Beiträge von Vouk

  • Implementing SVT-VP9/AV1 in Voukoder

    Implemented AV1:

    Code
    [21:27:01] Frame #439: vRender: 31 us, vProcess: 16 us, vEncoding: 63649 us, aRender: 61 us, aEncoding: 265 us, Latency: 64077 us
[21:27:01] Frame #440: vRender: 23 us, vProcess: 11 us, vEncoding: 27684 us, aRender: 54 us, aEncoding: 254 us, Latency: 28058 us
[21:27:05] Frame #441: vRender: 27 us, vProcess: 15 us, vEncoding: 3904113 us, aRender: 61 us, aEncoding: 509 us, Latency: 3904768 us
[21:27:06] Frame #442: vRender: 48 us, vProcess: 16 us, vEncoding: 565042 us, aRender: 64 us, aEncoding: 355 us, Latency: 565568 us
...
[21:27:06] Exported 445 frames in 170 seconds. (avg. 2.62 fps)

    I guess I need a better CPU... my 8700K is too slow.

  • Need RGB+ Alpha In Mov Format

    You don't want the smallest file size here. Smallest file size means highest compression. And as you want to put this clip as source media in a premiere project I guess you'd even like to have no compression (-artifacts) to get highest quality and fast timeline scrubbing.

    Don't care about 17MB files. :)

    Alpha channel makes only sense with intermediate codecs (like ProRes). You need these in the editing process. When you're exporting a finished project you don't need it anymore. h.264 does not support it.

  • Need RGB+ Alpha In Mov Format

    Good news! I tested it and it was already working with 2.2.

    It is important to use a codec / encoder that supports alpha channels (like ProRes) and a pixel format that contains an alpha channel (YUVA - A=Alpha).

    Works for me as you can see.

  • HDR color space irregularities

    Lets look at the whole processing chain:

    • You'd like to export with yuv420 10bit and hevc_nvenc => using "p010le"
    • Version 2.2 requested the frame data in either:
      • Format: PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_PLANAR_8u_709 (bt709 selected)
        Input: bt709
        Output: bt709 or bt2020
      • Format: PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_PLANAR_8u_601 (all other selections)
        Input: smpte170m
        Output: smpte170m
        • 1. Issue: It requested 8bit and converted it up to 10bit
        • 2. Issue: It used bt601 and converted it to bt2020
    • Version 2.3 changed this behaviour to:
      • Format: PrPixelFormat_VUYX_4444_32f (BT601 selected)
        Input: bt601
        Output: unspecified (or set by setparams / colorspace)
      • Format: PrPixelFormat_VUYX_4444_32f_709 (all other selections)
        Input: bt709
        Output: unspecified (or set by setparams / colorspace)
    • Premiere will render in 32bit float
    • Connector converts it to yuv444 (16 bit)
    • FFmpeg converts it to p010le

    So it's more or less clear why this is not working:

    1. Using 32bit float is a good (but slower) decision because we are downscaling, not upscaling.
    2. I somehow need to get the information what PrPixelFormat_VUYX_4444_32f means. Is it bt601? Or does it depend on the source? How to identify this? And what is the color range?

    I have to admit the 10bit (and higher) modes really need improvement.

    But all changes need to be done in the connector, not in the voukoder itself. It is about how to get the right information from Premiere.

  • HDR color space irregularities

    Did you do a MediaInfo (https://mediaarea.net/en/MediaInfo) of both files to compare them with each other?

    In my case:

    As Voukoder is using FFmpeg internally, maybe it would be a good idea to create an FFmpeg command line that creates a perfect video from your point of view.

  • Voukoder 2.3

    Release Notes

    IMPORTANT - PLEASE READ

    Voukoder has been split up into two components starting with this release:

    • The Voukoder Core component (this part)
    • An application specific Connector module (i.e. for Premiere/MediaEncoder, After Effects or VEGAS)

    Instructions

    1. Uninstall all previously installed Voukoder related components from the control panel (esp. when upgrading)
    2. Install Voukoder 2.3
    3. Install an appropiate connector module

    We are working on it to make this easier in the next versions. The separation was necessary for legal reasons but also offers new future possibilities.

    Changes

    • Introduced VEGAS Pro support
    • Moved log and update information to the systray
    • Logging path changed to %LOCALAPPDATA%\Voukoder\Logs
    • Added video filters: Equalizer, SetParams and Colorspace
    • Added FFmpeg logging to STDOUT (for troubleshooting)
    • Added qmin and qmax encoder options for NVENC encoders
    • Added 10bit export for hevc_qsv
    • Removed lower bitrate limitation

    Fixes

    • Fixed audio isses when using 2-pass encoding
    • Colors with ZScale filters were messed up (when using packed pixel formats)
    • Advanced settings did not get loaded from stored x264/x265 settings
    • The codec options did not get saved and loaded correctly
    • Audio and video format changes did not get set correctly when changed (i.e. issues with FLAC)
    • Fixed and improved working with various color ranges and color spaces
    • Fixed handling unicode filenames

    Notes

    For using NVENC encoders driver version 436.15 or newer is required.

  • HDR color space irregularities

    The thing is I need to specify these values when creating the muxer / format instance:

    - matrix

    - primaries

    - transfer

    They are "unspecified" by default. Which seems to be okay for all non-2020 color spaces.

    Currently they will be only set when using the color space filter and this seems to be the issue. I need to think about a smart way to set these values even when not using any filter. But if a filter is used the filter settings will overwrite these values.