Rendering just stops ..

garo wrote on 10/23/2004, 12:16 AM

Hi All!
jo, rendering a 8 minute surfing project from Sweden - (yes we surf and have good waves in Sweden! - good wet suits too!) and twice now rendering has just stopped dead in it's tracks at (I think) about the same spot (no pun intended) i.e. 35%. There is lot's of space left on the Lacie firewire disk - the program just seems to stop "answering" --- WINXP Vegas 5.0

Any clues?

Thanks. Garo

Comments

B.Verlik wrote on 10/23/2004, 3:25 AM

More information. Rendering from what, to what? There are so many variables, you need to include exact information. Are you multi-tasking?

Liam_Vegas wrote on 10/23/2004, 6:55 AM

If it stops at a particular spot then that usually means something on the timeline at that very frame is causing this. Not that it has happened to me often (probably - once). As long as you are rendering to AVI you should end up with an AVI after that failed render (at least what it had rendered up to that point). Load that back into the same project and place it on tracks above the existing ones.

By doing this you will have two options available.

1) You will then be able to see the exact frame it failed on. Now look at the FX's and other things that may be applied at that point and see if by changing them (maybe removing some FX's) you can get the render to continue.

2) you can now easily select the portion of the time-line after the already rendered video (that 35%) and render that seperately. (note that if this does now work - then you can easily load the original AVI (the 35% complete one and this new one (containing the rest) into a Veg and render again to a single AVI file (which will do a a very rapid full bit-copy of the combined AVI).

Make sense?

garo wrote on 10/23/2004, 8:42 AM

hmm, I suspected a very short but plug-in intensiv event and sure'nuf follks removing the Convultion Kernal FX and one of the Brighteness/Contrast FX (you know how they sneak in there now and again) the rendering is puutting along just fine and the entire rendering time seems to have been reduced appreciably also - just by adjusting this single event!

//Garo