Voukoder 10.2 won't render using NVENC and Voukoder 12.2 doesn't have a NVENC option (Vegas Pro 15)

  • The last time I used Voukoder (Fall 2021) I had no issues with version 10.2. Today I tried using it again because I wanted to render in a bigger resolution than magix mp4 could provide. However everytime I tried the rendering window popped up for a short period of time and then disappeared again.

    Afterwards I installed version 12.2 but in that version there are no NVENC options and I don't wanna render with my cpu since it would take hours.
    My specs are:
    Ryzen 5 3600

    MSI RTX3060
    32gb 3200mHz RAM

    I've seen the first problem quite often on this forum but none of the solutions written in the other reports worked for me. (I might have overseen some though)

  • Vouk 16. März 2023 um 20:49

    Hat das Thema freigeschaltet.
  • Now the newest voukoder version shows my graphics card in the encoders but the same problem occurs as with the older voukoder version where the render display disappears almost immiedately after clicking on "render" before being able to reach a singlular percent.
    Thank you so far for giving this easy solution for half of my problems though!

  • the res i'm trying to render in is 3200x2400 (3:4 format)
    i'm gonna try to render different resolutions/projects now to see if that's the problem!



    Is that true for all resolutions (HD, UHD) or just the one you are trying to render to? What is that resolution and does it work with hardware encoders?

    so I've tried some different projects with different resolutions and project settings than the one i originally wanted to render with voukoder but the same problem occurs. The render process starts but then stops and closes before going above 0% almost immediately.

  • Enable advanced logging in Voukoder, then try rendering again and check the log file.

    No point stumbling around in the dark trying to find the problem when you can ask the program itself what it's crabby about!

    Einmal editiert, zuletzt von Joe24 (22. März 2023 um 17:38)

  • Newer NVENC cards (starting with Turing) also can't encode interlaced video, which you have enabled in your first screenshot (the Field Order option). Try progressive video instead.

    4 Mal editiert, zuletzt von Joe24 (22. März 2023 um 18:37)

  • Newer NVENC cards (starting with Turing) also can't encode interlaced video, which you have enabled in your first screenshot (the Field Order option). Try progressive video instead.

    Didn't work, sorry. I should've mentioned that not all my projects have interlacing activated and since I've tried rendering multiple projects I should've listed the differences to my original project.
    Also I have messaged the log file but it wasn't permitted by a mod yet.


    Newer NVENC cards (starting with Turing) also can't encode interlaced video, which you have enabled in your first screenshot (the Field Order option). Try progressive video instead.

    [16:55:27] FFmpeg: No capable devices found

    [16:55:27] FFmpeg: Nvenc unloaded

    [16:55:27] Failed opening codec: h264_nvenc

    [16:55:27] Unable to open video encoder: h264_nvenc

    [16:55:27] Closing encoders ...

    [16:55:27] Opening encoder failed! Aborting ...

    [16:55:27] Unable to open encoder.

    (these are the last 7 lines of the log)

    Einmal editiert, zuletzt von Vouk (22. März 2023 um 19:10) aus folgendem Grund: Ein Beitrag von 8spin mit diesem Beitrag zusammengefügt.

  • It's something to do with your resolution. I tried a known working project on my rig (VP15, 3060Ti, Voukoder 13.0.2, Nvidia driver v531.29DCH patched with keylase), and I can make it choke by changing either of the resolution values (width or height) to your values. Tried 2400x3600, 1920x3600, 2400x1080. In all 3 cases, I get the following error in the log when ffmpeg is being initialized:

    FFmpeg: InitializeEncoder failed: invalid param (8): Invalid Level.

    When setting resolution back to 1920x1080, everything works again.

    According to the documentation, NVENC resolution limit for everything from Pascal to Lovelace is 8192x8192, so it shouldn't be an NVENC problem. Either FFmpeg doesn't like your resolution, or it's not receiving the correct syntax from Voukoder.

    You could test for an FFmpeg limitation by CPU-rendering a small test file in Vegas and then trying to re-encode the file using FFmpeg and the NVENC encoder directly from command line.

    3 Mal editiert, zuletzt von Joe24 (23. März 2023 um 05:43)

  • There might be more than one problem with your settings. Is this log from before or after you changed to progressive video?

    Is that what you meant with disabling interlacing? Because I tried that yesterday and it actually worked! The whole time the problem was right infront of me I just didn't notice it because I never change the field order since the default is "none (progressive scan)" but for whatever reason this was automatically set to "upper field first" in my recent projects which is why voukoder didn't work. I don't know why vegas did that but the problem is fixed now. Thank you so much to all of you!

  • Glad it works!

    Ignore what i said earlier about there being a problem with the resolution. I was exceeding the max resolution of my target output format. Duh!

    Einmal editiert, zuletzt von Joe24 (23. März 2023 um 16:42)

  • Vouk 23. März 2023 um 19:48

    Hat das Label Kein Bug hinzugefügt.
  • “Interlacing option automatically turns on” might have a connection with incorrect video editing software setting. I haven't used Vegas Pro so I could only guess. Maybe Voukoder should add something to alert user using NVENC encoders for Interlacing/TFF/BFF is on, before starting the encoding task