Impossible video rendering

Comments

thurefil wrote on 12/23/2018, 4:23 AM

Hello Nik Hope,

I upgrade my Vegas software, but it's the  352 build.

I can't download the 416 build with "vp16edit_dlm.exe" tool.

I will be attentive to the plugins for my next edit.

You have to know that!

A prior warning from Magix on the compatibility of third-party plugins would be welcome.

I completely agree with you on providing a complete list of defective plugins.

As they say here: prevention is better than cure!

thank you

NickHope wrote on 12/23/2018, 4:38 AM

Oops, I got my versions muddled up. 416 is the last build of VP15. 352 is the last build of VP16.

Do you know what build you were using before you updated?

Please let us know here if you do another render of a project with the VEGAS AutoLooks FX and if it is now works any better.

thurefil wrote on 12/23/2018, 12:20 PM

With the update, everything is ok.

I summarize the adjustments made:

1- Update Software

2 - I match my project to my video project using the wizard,
3 - In the options, I have set the dynamic preview to zero,
4 - I have reduced the playback thread to 1
5 - the GPU is enabled,
6 - I select the optimized codec with Nvidia NVENC
7 - AutoLook is enabled

Rendering is done without exceeding GPU memory and without exceeding RAM memory.

The GPU's RAM is used stably and consistently, as is RAM memory.

My ASUS P5Q3 Deluxe card, my Q9650 CPU and my Nvidia GTX 1060 graphics card still have a bright future ahead of them!

Thanks again to all of you, it's nice to have help to untangle this bag of knots.

Excellent forum

Happy holidays to all of you, and happy new year 2019!