You can use fdk_aac with Voukoder R2 too. You need the libfdk-aac-2.dll.
I'm currently using Voukoder R2 2.2 and I also tried to reproduce this behavior. In my case I can confirm that, if I choose a bitrate higher than 256 kb/s with stereo sound MediaInfo says it is VBR. When using 5.1 Mediainfo says VBR no matter which bitrate I choose. But I think this is not a Voukoder problem because with ffmpeg commandline this is the same.
Teste mal bitte einen anderen Audio Codec, z.b. AAC. Ist die CPU übertaktet?
Premiere Pro 2017 uses all nvenc sessions for itself as I remember. So unfortunately you have to use Premiere Pro < 2017 or Premiere Pro > 2017.
Were in Version 1 some more compiler optimizations active?
Seems like ffmpeg can only decode bink 1 and bink 2 video files. Encoding is not implemented so far I think. Furthermore a licence is required if you want to implement Bink in your software.
But there is an exporter plugin for Adobe to export Bink made by the developers itself.
The only thing that is not set to default is that your source and export is interlaced. Maybe you could try export a non interlaced source file just to be sure it's not the interlacing.
Please try to copy the .prm file manually to your install location -> Adobe\Common\Plug-ins\7.0\MediaCore
Please try again without setting the level flag.
In the logfile you can see that the frame rate is set to -4.65. That can't work
If you have used the automatic source detection, set the framerate manually.
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 user.name "John Doe"
git config --global user.email "firstname.lastname@example.org"
- Install Visual Studio Code (for easy code editing and pushing changes to github)
- 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
- 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 https://github.com/testuser/voukoder.git" (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 https://github.com/Vouk/voukoder.git" in the terminal
- Follow the next instructions explained here
- 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
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.
I can reproduce that issue with zscale using hevc_qsv and h264_qsv.
When using 2pass the audio is encoded already in the first pass. When the second pass starts audioRenderer is NULL because it's already done in the first pass I think. With my added if clause that prevents encoding the audio twice, it is fixed.
That's strange audioRenderer isn't NULL while debugging, but why it doesn't work?
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(exportInfo.audio.enabled) then everything works fine.
I have also made an if clause to avoid that audio is encoded twice when using 2pass.
I have have used the mkv container.
I have fixed it. I will do a pull request later
Oh yes, that's an important point!