Yes, I am not interested in NVENC anymore, we have found the reason for it. I'd like to know why other encoders are failing now.
That's why I asked you to test any other encoder (i.e. x264). As it is failing with an error in the voukoder log there must be some FF low level log entries.
I can't help you if you don't want to send it to me.
Well, but in the other post you tried to do an NVENC encode, right?
Please do an x264 encode until the error appears and attach that windbg console output here.
The issue is that Premiere / Voukoder was not able to identify the framerate "23,932" fps. I guess this is some sort of a variable frame rate (VFR) and is most likely (24000/1001fps or 24fps) material.
Can you please post a MediaInfo of the source file?
The solution is to set an FPS value manually.
So what does windbg.exe say about x264?
I check that, yes that is correct. I made a note in the release notes.
So i guess that issue has been solved, right?
Okay, normally I set:
info->max_width = 8192;
info->max_height = 4320;But maybe that is a limitation from the encoder.
So what is not working in your case?
Rendering by Media Encoder? (prm file)
or
Rendering the Render queue? (aex file)
Released 2.3beta6
IMPORTANT: Please uninstall any old version of voukoder and its connectors first!
Fixes:
Changes:
Both updated components are available now. Please retest (and confirm that this is fixed now).
So, also strange one. According to the Premiere Developers Guide a key "CurrentVersion" should be present.
I have no clue why it can't start a software encoder. Maybe you can run it in a debugger (i.e. windgb.exe) so you get important additional logging information in the output console.
First, x264 is an encoder for the h264 codec. Just like there is an AMD h264 encoder, but not an AMD x264 encoder.
I would suggest you to test this with FFmpeg. Voukoder is always using the latest versions of all components from GIT master.
Existing for premiere but missing for VEGAS.
Requires additional UI elements.
On list for 2.4.
Should be possible.
I'll put it on the list for 2.4.
Can you post a voukoder log file? Then we can take a look at it.
What "bitrate=0" does is that it actually says "bitrate can be unlimited", which is what you want. This basically simulates a dynamic quantizer like CRF with x264.
So, yes i'll change it to allow bitrate=0.
Can't confirm.
If i run this ...
ffmpeg -i "z:\overvouk\2016-11-02-Dead by Daylight #001.mp4" -vcodec h264_nvenc -preset hp -profile:v main -rc:v vbr -qmin 0 -qmax 50 Out.mkv
... the quantizer value is frequently changing. Maybe the range between qmin and qmax in your case is just too small.
Gefunden und behoben. Benötigt allerdings für einen vollständigen Fix ein Update beider Komponenten.
can you start regedit.exe and make a screenshot of this key with all its entries first, please?
HKEY_LocalMachine\Software\Adobe\Premiere Pro\
Really strange. I have the impression that it is somehow related to your specific windows configuration.
Is it possible your user is a special restricted user? Maybe limited by various rules defined by a domain policy? Or in a citrix environment or similar?