VEGAS PRO 21 not rendering.

  • Vegas Pro 21 is not working with Voukoder. It will immediately jump to 100% and say "cancelled" in the bottom left corner of Vegas.

    I've reinstalled the software and restarted my computer several times looking for a fix.

    Einmal editiert, zuletzt von iamRA (22. September 2023 um 03:36)

  • Vouk 22. September 2023 um 07:49

    Hat das Thema freigeschaltet.
  • Lower the audio sample rate of your Vegas project and try again. AAC has a limit of 96 kHz.

  • Always stops on frame #102? That's odd. Do you have "Render Loop Regions Only" set in Vegas render options?

    Can you elaborate on what you mean by the render "freezing"? Do you have to force-close Vegas, or what?

    No errors that i can find in the logs. Maybe somebody else can see something. The fact that it's rendering at all is puzzling.

    The AAC codec in FFmpeg used to have a bug that would glitch on anything over 48 kHz sample rate, although i thought that was fixed years ago. Did you try 48 kHz?

    Also, maybe try changing video and audio formats, see if you can pin the error down to some specific setting or format.

    Does VoukoderPro give you the same problems?

    3 Mal editiert, zuletzt von Joe24 (23. September 2023 um 09:31)

  • Render loop regions only is OFF. I do have to force-close Vegas afterwards because the program freezes once the render stop itself. I am on 48kHz.

    I tried Voukoder pro but I don't think it works with Vegas 21 yet. I've tried different installations and it never shows up in the program.

    Einmal editiert, zuletzt von iamRA (24. September 2023 um 01:59)

  • Does it render without using Voukoder? Or using Voukoder but software rendering, like x264? Are your video drivers up to date?

    Yes VoukoderPro works fine in Vegas 21. On the other hand, Voukoder 13 predates Vegas 21, so possibly there are some issues there?

    When you install VoukoderPro, you have to manually select your NLE (Vegas 21, etc.) from the setup menu. This is not automatic. Seems to confuse a lot of people.

    3 Mal editiert, zuletzt von Joe24 (24. September 2023 um 04:18)

  • It does render without Voukoder. A software rendering did not work with Voukoder, and all my graphics drivers for my Nvidia 3080 are up to date (had to be to play starfield lol).

    I did install Voukoder Pro to the right NLE but there are multiple options.

    (Install to local hard drive, install entire feature to local hard drive etc.)

    I don't know which one of these was the correct one and that could be the reason Voukoder pro doesn't pop up when I open Vegas 21.

  • In the Vegas "Render As" menu, make sure you have "Show Favorites Only" de-selected.

    If neither Voukoder nor VoukoderPro works on your rig, there's something screwy with your system settings. Lots of successful users with Vegas 21.

    Your vRender times are 100x higher (slower) than mine.... and my system is not new. Some of your vRender times (the time Vegas takes to render the frame before it gets fed into Voukoder/VoPro) are over 1 second, which is bonkers. On a system like yours, I'd expect at least double-digit fps . . . not <1 fps.

    Code
    [20:02:18] Frame #49: vRender: 798341 us, vProcess: 0 us, vEncoding: 3036 us, aRenderEncode: 906 us, Latency: 802295 us
    [20:02:19] Frame #50: vRender: 1071685 us, vProcess: 0 us, vEncoding: 4496 us, aRenderEncode: 566 us, Latency: 1076763 us

    Are you trying to run any other programs at the same time (e.g., mining?), or is Vegas running out of RAM? To be clear, you're saying that all projects malfunction, without exception? Have you tried creating a simple new project and rendering that?

    14 Mal editiert, zuletzt von Joe24 (2. Oktober 2023 um 07:42)

  • Similar problem here, after updating both VEGAS and Voukoder to newest versions.... just rendered succesfully after changing project settings audio from 192000 (the original resolution of the WAV file I am using) to 48000... also 96000 would work.

    2 Mal editiert, zuletzt von richardpohl (13. November 2023 um 07:14)

  • I was having this issue also and found the fix for me was to go into Project Properties and make sure the "Field Order" was set to "None (progressive scan)"

    Immediately after this, my rendering worked flawlessly no issues.