Problem is only that free Voukoder classic is not available anymore.

So the alternative options are to purchase Voukoder Pro or Wayne's HOS?

I have been using Voukoder classic for several years now and it's still my favorite method of rendering. No experience with Voukoder Pro or Wayne's HOS. Unfortunately there's no way to implement Voukoder classic into VP23, as I'm aware of.

+1 FIX IT, PLEASE

It's worth remembering that the Voukoder Classic is a depreciated program with no further development and is different to the newer Voukoder Pro. Wayne's HOS is an alternative - albeit a paid version that can allow NVENC in all versions of Vegas (via Render+) and has many other tools included. I am getting fantastic results with the AV1 codec and NVENC.

@LUCAS-OLIVEIRA Whilst we appreciate your frustration please refrain from posting the same comment in several threads. CR#3 applies and your posts have been removed from the other threads.

Also we trust you are also harassing Nvidia to "FIX IT, PLEASE". After all they created the problem and it doesn't just affect Magix/VEGAS.

When i render with voukouder in vegas 22 the audio is out of sync by about 5 frames. Does anyone know how I can fix this? It also happens with Happy Otter.

Are you sure the rendered file is out of sync? (are you judging it in a player) Or is VEGAS decoding it wrong when brought back in?

If the render is off it might be fixable with a filter in Voukoder: https://www.voukoder.org/forum/thread/552-vegas-pro-audio-shift-in-rendered-video/
Others report no issue with VP 22 and 23: https://www.voukoder.org/forum/thread/1685-vegas-22-maybe-offset-problem/

Are you sure the rendered file is out of sync? (are you judging it in a player) Or is VEGAS decoding it wrong when brought back in?

If the render is off it might be fixable with a filter in Voukoder: https://www.voukoder.org/forum/thread/552-vegas-pro-audio-shift-in-rendered-video/
Others report no issue with VP 22 and 23: https://www.voukoder.org/forum/thread/1685-vegas-22-maybe-offset-problem/

Thanks Roger. I continue with the old nvidia drivers and after import the voukouder render version in vegas for check the audio have 2 ~ 3 frames out of sync comparated with the native vegas 22 render option. In happy ptter happend the same. I will check your link thanks a lot roger!!

the audio is out of sync by about 5 frames

Five frames with what framerate?

One way to fix it might be to render just the audio to a wav file. Then use the wav file on your timeline, muting the other original audio tracks. Then move the audio by five frames. If it needs to be advanced you will need to trim frames of the beginning in order to move it. Then render your project with Voukoder or HOS.

I did some testing of VP 22 before and also found audio alignment issues. I'm not sure VP 22 NVENC is correct though; it may be that Voukoder was correct.

Here C0008 is the source file so for me that's the reference. Mainconcept= MagixAVC with Mainconcept; NVENC= MagixAVC with NVENC.

In 21.208 all but the 22 NVENC render matched my source file.

Anyway the important thing is that the rendered file itself is correct so do a test or two for just that (something with a sharp sound where you can see if the audio lags or precedes the video).

If you render to then continue to edit then a workflow where it stays in sync upon reimportation into VEGAS becomes important and using audio delay in Voukoder may help.

I did some testing of VP 22 before and also found audio alignment issues. I'm not sure VP 22 NVENC is correct though; it may be that Voukoder was correct.

Here C0008 is the source file so for me that's the reference. Mainconcept= MagixAVC with Mainconcept; NVENC= MagixAVC with NVENC.

In 21.208 all but the 22 NVENC render matched my source file.

Anyway the important thing is that the rendered file itself is correct so do a test or two for just that (something with a sharp sound where you can see if the audio lags or precedes the video).

If you render to then continue to edit then a workflow where it stays in sync upon reimportation into VEGAS becomes important and using audio delay in Voukoder may help.

would you try to check it after switching on "enable legacy AVC decoding" in preferences > file i/o.?

Sure.

For anyone currently experiencing render failures after the latest NVIDIA driver update, there is a workaround. If you are on VEGAS Pro 22 or below, I highly recommend installing the standard version of Voukoder (and the corresponding connector) for the version of VEGAS you are using. Voukoder still remains fully compatible with the newest NVIDIA drivers. I tested it on both Vegas Pro 22/21 & It is often significantly faster than the built-in MainConcept renderers. This is currently the most reliable way to restore hardware-accelerated encoding without having to roll back your system drivers.

Until a permanent Fix by NVIDIA or Magix, this is the best solution.

The old free Voukoder doesn't work well with newer versions of Vegas because it applies an offset to the audio, as older versions of Vegas had an offset bug.

If you're using the old Voukoder (not Pro) and the new Vegas (probably >=20), then:
a) in Vegas, you render the video with Voukoder
b) export the audio to WAV using Vegas's built-in encoder
c) mux the video from a file with a) audio from a file with b) preferably ffmpeg

ffmpeg -hide_banner -i video.mp4 -i audio.wav -map 0:v -map 1:a -c:v copy -c:a aac -b:a 256k "output (muxed).mp4"

When i render with voukouder in vegas 22 the audio is out of sync by about 5 frames. Does anyone know how I can fix this? It also happens with Happy Otter.

Fix above. The offset error is ~0.044s

the audio is out of sync by about 5 frames

Five frames with what framerate?

One way to fix it might be to render just the audio to a wav file. Then use the wav file on your timeline, muting the other original audio tracks. Then move the audio by five frames. If it needs to be advanced you will need to trim frames of the beginning in order to move it. Then render your project with Voukoder or HOS.

It's a makeshift solution and won't work well. It'll cut off some of the audio at the beginning and insert silence at the end. (Or vice versa, I don't remember.)