Posts by Vogelforscher

    Set up needed tools

    • Create a github account if you don't own one
    • Install git
    • Make sure git is in your system PATH variable
    • The first thing you should do when you install Git is to set your user name and email address. This is important because every Git commit uses this information, and it’s immutably baked into the commits you start creating. Type these commands in a command line with your username and email

    git config --global "John Doe"

    git config --global ""

    Fork Voukoder

    • To make changes in the translation files or other files we are forking voukoder (creating a clone in your own github account to make commits/changes)
    • Ensure you are signed in with your github account in your web browser
    • Navigate to the Voukoder project site
    • On the top right side click on "Fork"


    • Now you have your own forked repository of voukoder where you are able to make changes

    Cloning Voukoder

    • Open Visual Studio Code
    • Open a terminal in Visual Studio Code by clicking on "Terminal->New Terminal" on the top
    • On the bottom a new window has appeared where you can execute commands
    • Navigate to a folder where do you want to save the forked voukoder repository e. g. "cd C:\Users\test"
    • With the command "git clone <repository>" you can clone the repository to your filesystem e.g. "git clone" (don't forget to replace "testuser" with YOUR github username)
    • A recommended step but not needed is to add a upstream repository to sync your cloned fork with the original repository
    • Navigate to the voukoder folder in the terminal e. g. "cd C:\Users\test\voukoder"
    • Execute "git remote add upstream" in the terminal
    • Follow the next instructions explained here

    Make changes

    • After you have cloned your forked repository to filesystem, you can open the folder in Visual Studio Code
    • Click on "File" at the top left corner and "Open folder" or press CTRL+K+O
    • A new window has appeared and you can navigate and select the voukoder folder which you have cloned
    • Now you should see the explorer on the left side where you can open and edit files


    • The translation files are located in "Core/resources/translations"
    • If you want to edit a file, simply click on it in the explorer
    • When editing a translation file make sure you only edit the second part after the colon in the quotation marks


    Commit and push changes

    • When you are finished, you can commit and push your changes to the forked repository
    • Click on the "Source control icon" on the left


    • You should see the files you have changed now
    • In the box above type a small message which describes your changes you have done
    • Click on the hook to commit the changes (if a window appears which says "There are no staged changes to commit" just click "Yes")
    • Now you can push the changes to github by clicking on the three dots and Push


    • A window should appear where you have to login with your github account to push the changes

    Pull request

    NOTE: Before you send your pull request, make sure you only make changes that are necessary, don't change files like Visual Studio Project files, except it is needed.

    • Open github in your browser
    • Go to your forked voukoder repository
    • You should now see that your branch is commits ahead of voukoder:master
    • Click on "Pull request"


    • Select the voukoder base repository first with base:master and on the right side your repository with the branch you want to compare (default master)


    • Click on "Create pull request"
    • Type a title and description for your pull request
    • Click on "Create Pull Request" again

    It would be nice if Voukoder can update itself and you don't have to download copy the .prm file in the plugins folder.

    Moving the logging view there is a good idea in my eyes. I would like to have something like: Rightclick on the Icon->Export Logfile to textfile.


    audioRenderer is suddenly NULL and the Reset() is not called. But i'm not sure how this can happen

    Yes, in the pull request I have replaced if(audioRenderer) with if( then everything works fine.

    I have also made an if clause to avoid that audio is encoded twice when using 2pass.

    Eigentlich brauchst du den Haken generell nicht setzen.

    Quelle digitalrebellion:


    Maximum Render Quality

    This is a high-quality resize operation that should be used when outputting to a different frame size from your sequence. It can reduce aliasing (jagged edges) when resizing images but is of no use when outputting to the same frame size. This operation significantly increases render times so only use it when resizing.

    Here is an example: Video source is a 4k 60fps video with a color correction applied. I have set Mercury Playback Engine in Premiere to CUDA. In Voukoder I have set hevc_nvenc with preset slow.

    In the taskmanager you can see that the GPU Video Encode engine is used (voukoder nvenc encoding) and the Video Copy Engine (premiere acceleration for the color correction).

    Ok, i've got the GTX1660, installed the Nvidia drivers and, while I'm still doing the 1 hour video test encode, it looks like it's going to take about the same time as without the GTX

    Do you have set the Renderer Setting to Mecury Playback Engine CUDA? (you can find it in the Project Settings) If you haven't any effects applied on your video like color corrections the GPU will not accelerate frame delivery. As I can see in the screenshot, the GPU Copy usage is at 0% so it is not used by Premiere as acceleration.

    Das Level Flag ist eine limitierung. Manche Decoder wie z. B. alte Handys oder eine PS3 können nicht alle Videodateien dekodieren. Deshalb gibt es das Level Flag um die Voraussetzungen vom Encoder zu limitieren. Lass das Level Flag einfach weg, einfach den Haken bei Level rausnehmen ;)

    Currently it is not possible to select a pixel format for h264_nvenc.

    The ffmpeg help output says these are available:

    1. Supported pixel formats: yuv420p nv12 p010le yuv444p p016le yuv444p16le bgr0 rgb0 cuda d3d11

    If you choose hevc_nvenc it is only possible to select 8 or 10 Bit but no pixel format.

    These are available for hevc_nvenc:

    1. Supported pixel formats: yuv420p nv12 p010le yuv444p p016le yuv444p16le bgr0 rgb0 cuda d3d11