...that I don't need: I have interlaced INPUT and need progressive output.
I need to deinterlace 50i content to 25p.
If your Vegas output is 25p, then why even mention interlacing? Why would Voukoder care what format your raw footage was? All it sees is the Vegas output.
NVENC options look the same. Which supports my point that the hardware features are fixed, regardless of software.
Define "better control of the hardware encoder". Which encoder options, in particular?
Sounds really like it's a VEGAS issue.
Agreed. Although it's interesting that it only crashes with Voukoder/VoukoderPro.
Ran into this problem with h.264 MP4 files recorded and remuxed in OBS (using current version 30.2.3). Vegas 20 will crash when trying to render the project through Voukoder or VoukoderPro. Even opening a single OBS-generated h.264 MP4 file and trying to render it causes the Vegas 20 crash. No helpful log files from Voukoder or VoukoderPro, seems like it is Vegas itself that is crashing. Crash does not occur when using non-Voukoder encoders in Vegas (e.g., Sony AVC/MVC). Crash also does not occur with h.265 MP4 files from OBS.
Tried turning on/off the Legacy AVC/HEVC decoding and MKV Reader in Vegas 20 (Options -> Preferences -> File I/O). None of these settings made a difference.
Searched the forums, and found this thread.
The solution, as noted by Joelson_Forte above, was to reassert the framerate in Vegas Project Properties (File -> Properties), even though it appeared to be set correctly to 23.976. I pulled down the Frame Rate menu, and selected the same 23.976 option that was already selected. Hit OK, and now the project will render.
Voukoder v13.4.1, connector v1.7.1, VoukoderPro v1.3.0
Most hardware encoders won't accept interlaced Vegas output.
Wow! That's good news indeed! ☺️
I dunno where to start with this one. 🙄
NVENC is a hardware feature, meaning it's part of your physical Nvidia graphics chip. You can't "update" NVENC unless you buy a newer graphics card. The same NVENC settings are available to all programs (FFmpeg, etc.).
Likewise, QSV and AMF are hardware features.
Voukoder and VoukoderPro also use FFmpeg libraries. So I don't see any advantage to your pet program.
Maybe try actually using VoukoderPro?
Did you figure out the answers to all your questions?
Voukoder uses FFmpeg, so you can refer to the documentation on the FFmpeg website in the meantime.
Spent some time chasing down an h.264 (NVENC) Blu-ray compatibility issue. Since earlier this year, TMPGEnc insists on re-rendering all files, even though I'm using the same exact working Voukoder/VoPro presets as a year ago.
It turns out that in newer versions of FFmpeg, the option to "use B frames as references" must have changed from default-off to default-on. (My presets did not manually change this value, just leaving it as default.) Blu-ray video needs to have this option disabled in order to be passed-through without re-encoding in TMPGEnc.
VoukoderPro menu option just says "Auto" for the default setting, so nothing misleading there.
However, Voukoder Classic incorrectly reports the default value of this option to be Disabled, when in fact the correct default value is now Enabled (or Auto).
It is indeed! I'm not accustomed to seeing it referred to by that name. Thanks.
If you pay attention...
There is existing WEBM support, you just couldn't be bothered to look. Pay attention.
This has been fixed. File and path variables are now working in VoukoderPro v1.3.0.0.
Filename and path variables confirmed working in VoukoderPro v1.3.0.0.
Thank you!
Still no "Max. GOP Size" settings that I can find.
VoukoderPro v1.3.0.0.
The vp22 connector is already in Voukoder Pro released 7/24/24. and is reported on the Vegas site to work.
Indeed. However, if you read carefully:
the original Voukoder classic
Log file? Are you trying to render interlaced video?
Where did the Max GOP setting go for the h264_nvenc encoder? There used to be one, but it seems to have disappeared. This needs to be set properly to achieve Blu-ray compatibility, etc.
I don't see it in the h265_nvenc options either.
VoukoderPro 1.2.5
Update: VoukoderPro 1.1.0 still works, but 1.2.0 and newer have the GOP setting broken/missing.
Yes, this is currently broken in all VoukoderPro release versions to date (v1.0.0 through v1.2.5). Seems to be a path-parsing error.
Using ${OutputFile.Path}\${OutputFile.Name} - GPU0 - BD v4.9.mp4 with the target D:\temp\channel 1\bike_5sec.voukoderpro gives me the following error:
2024-07-09 15:30:32 (error) [OutputNode.cpp:210] Unable to open output: D: empchannel 1\bike_5sec - GPU0 - BD v4.9.mp4So instead of D:\temp\channel 1\bike_5sec - GPU0 - BD v4.9.mp4, the program tries to create a file named D: empchannel 1\bike_5sec - GPU0 - BD v4.9.mp4.