Beiträge von Joe24

  • B frames as references

    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).

  • Missing GOP setting?

    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.

  • Dynamic file naming

    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:

    Code
    2024-07-09 15:30:32 (error)    [OutputNode.cpp:210] Unable to open output: D:    empchannel 1\bike_5sec - GPU0 - BD v4.9.mp4


    So 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.

  • JavaScript errors from dynamic renaming in VoukoderPro

    Attempting to insert JavaScript variable in the filename, and all file/path-related variables seem to return a value of "#ERROR". VoukoderPro v1.2.5.


    This gives me the following error in the log:

    2024-07-08 15:56:29 (error)    [OutputNode.cpp:210] Unable to open output: #ERROR - GPU0 - BD v4.9.mp4


    PS, this was a fairly long filename, but shouldn't have exceeded 256 characters or anything. :/

    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:

    Code
    2024-07-09 15:30:32 (error)    [OutputNode.cpp:210] Unable to open output: D:    empchannel 1\bike_5sec - GPU0 - BD v4.9.mp4

    So 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.

    Something's not getting parsed right. Tried all the way back to VoukoderPro v1.0.0, and the same problem exists in all versions.

    It seems VoPro will return #ERROR if there is no path specified. A path must be provided, whether a static one such as d:\temp\, or a dynamic one such as ${OutputFile.Path}.

    Dynamic path ${OutputFile.Path} is currently not working (see above). Maybe others too, I've only tried ${OutputFile.Path} and ${OutputFile.Name}.

    However, as a workaround, if you manually specify a static path such as d:\temp\, you can still use dynamic file naming within that folder, because ${OutputFile.Name} appears to be working. (e.g., d:\temp\${OutputFile.Name}.mp4) The drawback is that your output files will always appear in the d:\temp\ folder with this method, regardless of what target folder you specified in your NLE. Which can be a bit disorienting! ;)

  • VEGAS Pro 15 support

    If I manually install to the \Program Files\VEGAS Pro 15.0 folder (using an unused Vegas 18/19/20 option in install menu, then manually entering the target folder), I get the following behavior in Vegas 15:

    • When clicking "Render As" in Vegas, instead of the Render As menu appearing, I get a simple popup box which says "VoukoderPro for VEGAS Pro, (C) 2023, Daniel Stankewitz" with an OK button.
    • If I hit OK, then the main Vegas Render As window appears.
    • VoukoderPro does not appear in the Render As list.
    • voukoderproplug-vegas18.dll (or 20, etc.) does appear in the Vegas 15 components list.


    Tried manually copying VoukoderPro files from a working Vegas 20 installation to Vegas 15 folders. Same behavior as above. Files copied:

    • \Vegas Pro 20.0\Voukoder-x64.fio2007-config
    • \Vegas Pro 20.0\FileIO Plug-Ins\voukoderproplug\

  • VoukoderPro 1.2

    If I manually install to the \Program Files\VEGAS Pro 15.0 folder (using an unused Vegas 18/19/20 option in install menu, then manually entering the target folder), I get the following behavior in Vegas 15:

    • When clicking "Render As" in Vegas, instead of the Render As menu appearing, I get a simple popup box which says "VoukoderPro for VEGAS Pro, (C) 2023, Daniel Stankewitz" with an OK button.
    • If I hit OK, then the main Vegas Render As window appears.
    • VoukoderPro does not appear in the Render As list.
    • voukoderproplug-vegas18.dll (or 20, etc.) does appear in the Vegas 15 components list.


    Tried manually copying VoukoderPro files from a working Vegas 20 installation to Vegas 15 folders. Same behavior as above. Files copied:

    • \Vegas Pro 20.0\Voukoder-x64.fio2007-config
    • \Vegas Pro 20.0\FileIO Plug-Ins\voukoderproplug\