Forever Render

bigrock wrote on 11/7/2011, 3:11 PM
I've got a large project of about 2 hours length that uses a nested project. The nested project uses Boris Red 5 extensively, especially the noise processing filter. I can start it rendering but after about 7% it seems to hand up and keeps on rendering forever. The rendered file has a zero size. Any ideas of what could be causing this. I am using Vegas 10.0e and it happens on both 32 and 64 Vegas. I am rendering to standard DVD output.


gwailo wrote on 11/7/2011, 5:33 PM
I usually get around this type of rendering problem by rendering the file to an uncompressed *.avi first -> then convert to a mpg2 file for DVD from the newly created *.avi
Steve Mann wrote on 11/7/2011, 10:49 PM
Make sure the nested veg file will encode ("Render As") properly.
bigrock wrote on 11/8/2011, 1:31 AM
I've been working to get the first 10 minutes to render as a test. It failed all 4 tests on the two different machines with Red 5 and Vegas 10.0e 32 and 64 bit. So I decided on a lark to upgrade the one with Vegas 11 version that was sitting patiently on the desktop to be installed. The first run that same 10 minutes passed, it did take about 2 hours (there is ton of RED 5 work in the effects stack).

So I have started the whole two hours again under Vegas 11 64 bit. It will prolly take 24 hours or more for the render on my 6 core machine. However it should be obvious by morning whether it has failed or not as the frame counter always stops updating. I will update the thread with the results. If Vegas 11 fixes the issue then great, most likey was caused by an unknown bug in OpenFX API in 10.

Dominated wrote on 11/8/2011, 8:57 AM
If it is happening at the same place each time try deleting the files in the problem area and then recapture them and replace. I had the same problem with V9e and it cleared it up.
good luck

Here is a link for some other tips with render hangs.
bigrock wrote on 11/8/2011, 11:02 PM
Good news everybody, after 16 hours the render complete. It never hung at all, you can the frame counter incrementing throughout the process unlike before where it always stopped at some random spot.

And the solution is Vegas Pro Version 11 (latest version). There are clearly some fixes to OFX plugin API that have corrected the problem I had on every render try in 10.0e. So this is a good reason to upgrade to 11.
bigrock wrote on 11/11/2011, 5:30 PM
I have noticed on Version 11 if you have Red 5 work in embedded veg, and put more Red 5 work on the clip in which it is embedded it seems to also get lost in limbo land. I am going to avoid putting Red 5 on clip that has a embedded veg that has Red 5 on the same section.