Stable VEGAS 18 Pro (482), but without NVENC encoding

Fiola wrote on 3/28/2021, 10:34 AM

Hello everyone,

I have one very specific question regarding newest update VEGAS 18 Pro - 482. I don't know exactly what changed, except I have no more NVENC option when using MAGIX AVC in rendering window.

Basically, it has been almost one year ago, when we finally find a great internal setting which actually helps to avoid crashes.

We just needed to do this:

Internal: Hardware Decoder for So4 Compund Reader - 0 from 1
Internal: Enable OpenCL/GL interop - FALSE from TRUE
File I/O: Enable legacy AVC decoding - Checked
File I/O: Enable legacy HEVC decoding - Checked

With that I had no more crashes of software, 100% fluid preview window (no stuterring even in 4K!) - and it was still using some oif the GPU for acceleration it seems. So all was great, smooth and amazing. When Vegas crashed, it was due to probably some minor caching problem. When I say, almost no crashes, what I mean is: crash of vegas every 10 minutes of editing scaled down to 1 or 2 crashes in a whole week. I know, what?!

But main thing: we were able to get our production done. And it worked. And we enjoyed editing time. And also rendering - which was supported with NVENC.

But latest patch, which introduced the great setting of disabling "double click on the edge of video to enable A/B tracks", (which is great by the way), also introduced, that I can't render with NVENC - which means, it takes like 50% more time to render videos than in previous version.

If I tick off the Legacy AVC and Legacy HEVC decoding... I have the NVENC available again in my render presets. So I think, there is a chance, that you force us to not use Legacy to actually use the NVENC. Which I absolutely understand in theory. But in that case I would do that only at time, I am 100% sure that you have no more problems with crashing the VEGAS. Which is unfortunately not the case. Not using Legacy AVC and Legacy HEVC will introduce crashes every 10 minutes, timeline hangling, long loading times and video stutterring.

I would like to ask you, if there is any new internal variable or some settings I can force to enable NVENC even with Legacy AVC and Legacy HEVC turned on, please share that with us!

If there is no way how to enable NVENC back even though ...

I guess we will roll one version od VEGAS back, hopefully that will be possible. I would recommend that to everyone who has similar issues like in my studio.

Please, don't take this as a random rant. I want to ask, if someone already figure that out or not ...

Thank you very much for any help,

Comments

j-v wrote on 3/28/2021, 11:12 AM

No problem with me on laptop and desktop, but one of the most important changes in the latest build is, that most of your "needed" changes are not needed anymore, because the program makes itself the best settings for you.
Try it out yourself by resetting the program and after that don not cange something at Internal, Options/Preferences/Video and Options/Preferences/File I/O.

RogerS wrote on 3/28/2021, 12:30 PM

A few users have reported the same thing with NVENC render options disappearing. I also see that when I enabled legacy decoding to test.

My recommendation to you is the same as what j-v said- put all the settings you changed for VP 17 or earlier versions back to the default and give 18 a try as it is intended to be used- with GPU and hardware decoding. If you still have problems then you can revert to the way it its now.

If you have to do that, one workaround to allow NVENC to be used with these legacy settings is to render through Voukoder. I just tried it and task manager shows encoding active.

Fiola wrote on 3/28/2021, 4:34 PM

Yeah. Thank you guys very much for help. I did reset the settings using the j-v steps as recommended. 5 minutes into editing, and I've got unresponsive timeline again.

So, yeah. In order to have no-crashing editing I need to turn off the So4, Interop and enable Legacy AVC. Then I am editing smoothly and without any problem.

I did start stopwatch actually, so it was 5 minutes and 43 seconds in editing when crash happen during playback. Preview freezes and dots were adding as processing "....." next to frame number. This is so frustrating. 3 years and this basic problem is still presented.

I will try to go with Voukoder way.

Fiola wrote on 3/28/2021, 8:12 PM

I did finished my project without any problem after these steps and using the VOUKODER I was able to render project with NVENC. Thanks! This is solution.

RogerS wrote on 3/28/2021, 9:36 PM

Glad it worked for you.

For your NVIDIA card, are you using the Studio driver? It helps with stability.

walter-i. wrote on 3/29/2021, 3:39 AM

@Fiola
It would be more honest to mark RogerS's thread as a solution - because he actually put you on the track.

Fiola wrote on 3/30/2021, 11:20 AM

@Fiola
It would be more honest to mark RogerS's thread as a solution - because he actually put you on the track.

Yeah, but actually it missing the information that in order to really work, it needs to set internals to these:

Internal: Hardware Decoder for So4 Compund Reader - 0 from 1
Internal: Enable OpenCL/GL interop - FALSE from TRUE
File I/O: Enable legacy AVC decoding - Checked
File I/O: Enable legacy HEVC decoding - Checked

So in fact, VOUKODER is only thing what is actually not solution, more like workaround at the moment. But of course, thanks ...

walter-i. wrote on 3/30/2021, 1:59 PM

@Fiola

Thank you for the feedback and clarification!