Beiträge von Joe24

  • NVENC resolution scaling (scale_cuda)

    The 'Scale' filter that is currently available does seem to use the GPU, but it's shuffling data back and forth to the CPU, very inefficient. Running 1 dual-output render in VoPro 0.7 is currently slower than running 2 simultaneous renders with Voukoder 13.

    'ZScale' is even worse, as it doesn't seem to use the GPU at all.

    On the other hand, the speed advantage of 'scale_cuda' should be substantial when it becomes available.

    For reference, here are some FFmpeg command lines I've used for scale_cuda with AVI/h.264/h.265 file sources:

    FFmpeg.zip

    Properly fed, all 3 variants will max out the GPU encoder with minimal CPU usage.

    An even more powerful feature of FFmpeg is the ability to use multiple graphics cards. Hopefully both GPU filtering (e.g., scale_cuda) and the ability to assign a job to a particular GPU will be added in the future.

  • NVENC bitrate

    NVENC VBR bitrate now confirmed working in v0.7.1.7, both with h.264 and h.265. Thanks.

    Clearing the error can also be achieved by deleting the broken h.264 encoder node in Scene Designer and creating a replacement node.

  • NVENC bitrate

    Deleted scene.json. Realized this action had just wiped all my saved scenes. Downloaded and imported the file from my previous post. Will rebuild the other lost scenes from memory at a future time.

    Scene Designer behavior unchanged, even in a fresh layout with a new encoder node. Render behavior also unchanged.


    Update: This info is from the most recent VoPro log file.

    (from C:\Users\[username]\AppData\Local\VoukoderPro\logs\)

    Code
    2023-08-05 15:08:30 (info)    [EncoderNode.cpp:200] Opening video encoder plugin: h264_nvenc
2023-08-05 15:08:30 (trace)    [FFmpeg:0] Unable to parse option value "-2013260544" as boolean
2023-08-05 15:08:30 (trace)    [FFmpeg:0] Error setting option bluray-compat to value -2013260544.
2023-08-05 15:08:30 (error)    [EncoderNode.cpp:207] Opening the encoder plugin failed with error code: -22
2023-08-05 15:08:30 (error)    [Router.cpp:274] Open phase failed: -22
2023-08-05 15:08:30 (info)    [VoukoderPro.cpp:589] Unable to start VoukoderPro: Undefined error!

  • NVENC bitrate

    Now it won't render at all (v0.7.1.6). When trying to render, immediately throws an error window that says "Unable to start VoukoderPro: Undefined error!"

    Also, in Scene Designer, double-clicking on the top NVENC h.264 node (the VBR one, see preset below) will now cause Designer to crash. If you delete the node and create a new one, it will initially allow you to set the parameters, but if you try to access the node properties for a second time, it will crash Designer.

    temp scene.zip

    One other (unrelated) minor issue is that in the installer options, the Vegas Pro 20 plugin is deselected by default.

  • NVENC bitrate

    • 96kbps AAC confirmed working.
    • Duplicate filename behavior confirmed working.
    • I can't reproduce the different-folder bug now, even doing what I did before (Vegas destination was default Documents folder on C: drive, VoukoderPro destination was set to D:\temp). Not sure what the difference is now. Free win, I guess?


    NVENC bitrate

    • The 2 attached files are encoded using supposedly identical settings, one using Voukouder v13.0.2, and one using VoukoderPro v0.7.1.5. Both videos are 1080p and have a target bitrate of 2.5 Mbps. Screenshots of the settings used are included.
    • Water videos.zip
    • I'm not aware of any user-defined minimum bitrate setting for NVENC VBR in either Voukoder or VoPro. There are only target (average), max, and buffer bitrates. As mentioned, the max rate is being observed, but the actual output bitrate is much lower than the commanded target rate.

  • NVENC bitrate

    A few issues noticed while experimenting with Vegas Pro 20.0 and VoukoderPro v0.7.1.4:

    • NVENC VBR target video bitrate is not being observed, although the max bitrate seems to be working. This affects both HEVC and h.264. Didn't try AV1. Tried to set a target video bitrate of anywhere from 2500-512000 kbps etc., but actual output is 200-400 kbps. If 2-pass is enabled, things get even worse (< 200 kbps).
    • AAC encoding setting of 96 kb/s CBR gives 128 kb/s. Other bitrate settings seem correct. This could possibly be an issue with the MediaInfo app.
    • If Vegas' output file name and VoukoderPro's output file name are not in the same folder/drive, the render hangs.
    • If you are creating multiple output files without specifying a unique name for each file, VoukoderPro will write both streams to the same file, resulting in a corrupt file.

  • VoukoderPro - Public Beta

    No.

    voukoderproplug.dll appears in Vegas' Component list. Cleared cache and preferences using Ctrl+Shift. No change.

    File size of voukoderproplug.dll is 175 KB, is this the expected size and version (0.1.0.0)?

    Is there a way to log what's (not) going on?

  • VoukoderPro - Public Beta

    Yes, voukoderproplug.dll is listed in Components (see screenshot).

    Uninstalled and reinstalled Vegas. Flushed the plugin cache with Ctrl+Shift, deleted all preference data.

    Still nothing showing in Render As menus.

  • VoukoderPro - Public Beta

    Zitat von Vouk

    Regarding the installer: Can you test if this fixes the issue?

    • VoukoderPro is still not available in the Vegas 20 render list. Tried uninstalling, reinstalling, rebooting, etc. Tried with the default installation settings, and also tried the options to install everything.
    • VoukoderPro.aex no longer appears in the root folder.
    • VoukoderPro.prm still appears in the root folder of a bulk storage drive (drive I:) which has no role in my operating system. There are multiple bulk drives available in the system, but it prefers Drive I:. If I remove drive I: from the system, VoukoderPro.prm instead appears in the root folder of my boot drive C:.

  • VoukoderPro - Public Beta

    Zitat von Vouk

    I've added first VEGAS Pro 20.0 support to 0.7.

    Hmmm . . . Voukoder Pro isn't shown in the renderer list (see screenshot). I'm using Vegas Pro 20.0 build 411.

    Uninstalled, reinstalled. No change.

    Also found VoukoderPro.aex and VoukoderPro.prm files in the root folder of one of my bulk storage drives (I:) which was odd. They were placed there today when I installed VoukoderPro v0.7, judging from the timestamps.

    And all audio and video streams in the output test files from Scene Designer are flagged as Swedish. Even when you manually enable the language flag for each stream and set it to English etc.

  • NVENC resolution scaling (scale_cuda)

    Test function reports success with this layout. Will see how that translates to the real world when the time comes.

    Video and audio streams in output files are by default flagged as.... Swedish??? Even after manually enabling language metadata in each stream node and setting all 4 streams to English.

  • NVENC resolution scaling (scale_cuda)

    Not really a bug, more of a question . . . Am I just missing something here?

    I've been playing around with the Scene Designer a bit, while waiting for Vegas Pro functionality to arrive. Love the interface. From downloading to having more-or-less what I wanted on the screen took less than 15 minutes. Of course I'm not able to actually test the results yet . . .

    One thing I notice is that the scale_cuda video filter doesn't appear in the list of available filters. (scale_cuda is the hardware scaler function on Nvidia graphics cards.) This would be fairly important for my use-case, as I'm trying to have the GPU accept a single video stream, split this into two streams, scale one of them down to 720p resolution, then use NVENC to encode them to different formats (h.264 and h.265).

    If this chain has to send a video stream back to the CPU for software scaling, and then back to the card, there will be a huge performance penalty.

    You can see my desired scenario below, except the Scale video filter would use scale_cuda and thereby keep all the computation on the graphics card.

    PS, wildcard file naming would be helpful, especially in a case like this where both output files will be MP4 file formats with the same name from the NLE. It would be nice to be able to add a suffix to the name from the NLE, for instance "* - Blu-ray version.mp4" and "* - download version.mp4".