Posts by rif

    Thanks VOUK! :) I'll try it

    But I still haven't understood how the Vegas Pro data feed coming into Voukoder is handled.

    What is important in Vegas Pro project settings (File->Properties) for Voukoder rendering?

    I want to get 10bit, HLG (HDR) real rendering through Voukoder.


    Nr 2. has four options (8bit... video levels or full range and 32 bit floating points... video levels or full range)

    Nr 1. (HDR mode) HLG cannot be selected if Nr 2. (Pixel format) is not selected to 32bit floating point (full range)

    Nr 3. Will it send Rec. 2020, HLG, 1000nit to Voukoder for rendering?


    OK, IN CONCLUSION!
    Two weeks of testing to get faster rendering with GPU/AMD (I haven't tested GPU/NVIDIA)

    If you choose the project settings as shown in the picture and you want to customize the levels and colors in Vegas and you want to render the correct result (with or without Voukoder).
    ....
    Then ... in Vegas Pro, select on menu
    Options -> Preferences.
    Select
    "Video" tab and set "GPU acceleration of video processing" to OFF.
    Restart Vegas!

    If you don't make color corrections in Vegas, it seems that the final result will be rendered and displayed in Vegas with the correct levels and colors. Maybe don't have to change "GPU acceleration of video processing" to OFF.
    In voukoder, you could probably choose x256 (cpu) rendering.
    (good but slow)

    NB! I haven't yet tested what happens when AMD (GPU) is chosen for rendering instead in Voukoder.

    If someone has a similar case with Voukoder when rendering in Vegas Pro (as I have described before),
    selecting from Voukoder (AMD (GPU) -> HEVEC -> Format p010le- YUV 4:2:0(10-bit, 3 channel, Planar)
    and AMD encoder will insert the wrong flags in the metadata of the rendered file in the case of HLG (HDR, Hybrid log–gamma, ARIB STD-B67, BT.2020) !!

    Then: Try "Windows Commant Prompt" with this ffmpeg command line, for a file that has already been rendered (it will only change HEVEC Metadata without re-rendering the file). It worked for me, and Videoplayers will play the copied file correctly.
    NB! You have to set the input file and output file path yourself.

    Code
    C:\Windows\System32>
    ffmpeg -i "D:\0-AudioVideoProjects\VideoProj\TEST\vegas2026-1.mp4" -c: copy -bsf:v hevc_metadata=colour_primaries=9:transfer_characteristics=18:matrix_coefficients=9  "D:\0-AudioVideoProjects\VideoProj\TEST\vegas2026-HLG.mp4"

    ==================================================
    I will not leave my Estonian stubbornness ;)
    ==================================================

    I asked ChatGPT similar questions out of curiosity (especially regarding hevc_amf GPU rendering, HLG BT.2020... ARIB_STD_B67 format) :)
    Don't criticize me! :P
    I know that AI tends to mess everything up.
    But maybe there are things there that we haven't noticed ourselves.
    I don't know. Everything seems mixed up like potatoes and cabbage in a pot. :D

    ==================================================
    ChatGPT: Reply that can be posted in the Voukoder forum: :P

    He doesn't give any reference from which he puts together his answer. :D
    ==============================================================


    PS! I found a couple of interesting writings to get the (AMD/amf HEVC h.256) metadata right.
    But I haven't tried it yet.

    How to add colour space metadata to an HEVC/H265 file with ffmpeg


    and

    How to Change Video Color Matrix with FFmpeg - ffmpeg
    Adjusting color matrix coefficients in standard definition (SD) video is critical for avoiding washed-out colors or improper tinting during playback or…
    salivity.github.io

    Thank you very much for the tutorials!

    Is it possible to forcibly change the metadata of the final file after rendering the AMD/amf gpu?
    (Change Transfer characteristics: to HLG and add Matrix coefficients: BT.2020 non-constant, without re-rendering the video)

    PS! The bit rate is tuned to reach about 80-90Mbs. CQP or CBR/CQP and 10-bit is selected (source 3840x2160, FPS 29.970 (NTSC) 4:2:0, 10bit).
    Which is the better option ... libx265 (cpu - slow rendering) vs. AMD HEVC (gpu - fast rendering) to maintain the best quality for encoding later into other formats or reusing in a video editor.
    But I don't want larger files than the original material (Osma pocket 3: 10bit, 4k, Overall bit rate 83.2 Mb/s, HLG, (mp4 HEVEC))
    NB! it is not necessary that the final rendering is in the MP4 container (if that changes something, oh... OK, Vegas Pro doesn't like MKV files).

    AND MORE! There was also a question about what settings in the Vegas Pro project settings (or also in the Vegas rendering template settings) are important when rendering with Voukoder... for example: if I have 8bit set in the Vegas project settings, will the raw material output to 8bit or does it not matter to get a 10bit final render? Considering that Voukoder already has 10bit set to the encoder.

    Thank you in advance if anyone has any recommendations :)

    OK!

    Second attempt:
    libX265 CPU rendering. (Still for rendering Osmo Bocket 3 10bit HLG files out of Vegas without losing quality.)

    Just in case, I will also put here the metadata of the original file that has been imported to Vegas (Metainfo v26.05):

    NB! I don't know what data is being sent from Vegas to Voukoder.

    I set in Vegas as the project settings -->
    Pixel Format: 32bit floating point (full range),
    HDR Mode:HLG,
    Compositing gamma: 1,000 (linear),
    ACES: 1.2,
    ACES color: Default (ACES2065-1),
    View transform: Rec.2020 HLG 1000nits

    Just in case, I'm going to change the Vegas render profile (Project tab) -->
    Color space: Rec.2020 HLG 1000nits,
    Color range (YCbCr output): Limited (Default
    ) ... (I don't know what would happen if I selected "Full" from the drop-down menu.)

    In order to obtain the same metadata as the original file when rendering in Voukoder, I had to create the following lines:
    X265 params:
    colorprim=bt2020:colormatrix=bt2020nc:transfer=arib-std-b67
    And to get the rendered file into the metadata - Format profile: Main 10@L5@High (it turned out that it was Main 10@L5.1@High).
    I had to add:
    level=5.1:profile=main10:tier=high
    The rest of the parameters, if anyone is interested:
    "passes": 1,
    "rc": 0,
    "crf": 15,
    "g": 10,
    "bf": 0,
    "preset": "slow",
    "profile": "main10",

    PS! You can't really choose anything more from there, because there are no drop-down menus and descriptions, unlike Voukoder's old free versions :).

    But my question is:
    Is the rendered video ... Vegas-out -> Voukoder-in -> ffmpg-out -> Remux-> rendered fail(mp4, mov, .etc) as desired and close to the original?
    And well, a rendered video file is not really the kind that needs these metadata.

    Hello!

    Specifications:
    Vegas pro ver 22 - 2026
    Metainfo v26.05
    Voukoder pro (Experiments)
    PS! I have AMD Ryzen 7 7840U RAM 64GB / Radeon 780M Graphic 16GB, Windows11 Home 25H2, AMD drivers latest

    I use Osmo Bocket 3 10bit HLG (HVEC) video files in Vegas.
    Color range : Limited
    Color primaries : BT.2020
    Transfer characteristics : HLG
    Matrix coefficients : BT.2020 non-constant

    I want to render a video file from Vegas that would have the same metadata as the original. It would be nice if the final rendering was of the same quality as the original material. For archiving but also for viewing.

    At the moment I'm trying an AMD/amf (GPU) HEVC encoder.

    No matter how I try, "Transfer characteristics: HLG" is replaced by PQ.
    "Matrix coefficients: BT.2020 non-constant" is missing from the metadata at all.

    I tried to change the Scene - Video Input params ...
    Colors Range - limited,
    Color space: Matrix - BT.2020nc, Primaries - BT.2020, Trasfer - ARIB STD B67.

    But that didn't change anything. It still turns out that "Transfer characteristics:" are PQ and "Matrix coefficients:" are missing.
    In video players, the colors are therefore incorrect.

    If I select the same video file in Voukoder Pro Transcoder and render it with the same "Scene", then everything is in place as it should be.

    Here's my Scene profile ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::)