9.0b Unusual lockup after render

PeterWright wrote on 9/8/2009, 9:13 PM
This has happened three or four times, but not every time ...

After rendering from Timeline to DVD format, the Render window says "Complete", but the render progress box at bottom left says "100% (1 of 7). There was only one item, not seven.

The main problem is that when this happens, Vegas is "frozen" and has to be shut down using Ctrl/Alt Delete.

I shall submit this to Support, but wondered if anyone else has experienced this.

edit: I've submitted to Support - but I do HATE having to repeat all my details, plus serial number, machine ID etc, when this information is already registered on this site. It's a deterrent to seeking support.

Comments

Grazie wrote on 9/8/2009, 11:55 PM
These hit n miss issues I hate.

Pete, have you done the usual stuff? Cleaned out the system drive of temps and stuff? If you have been getting crashes on rendering, make sure the UNDO buffer folder isn't constipated; I have render workspace that is stripped of anything CPU demanding; do you think that you could be getting "hot" - see what the dust levels are on the CPU fan and how clean the airways are around the innards of the pc.

Rendering is CPU intensive - maybe, just maybe there is a "brake" on the process: heat, temps AutoSave call-outs. Oh yeah, make sure you have saved the project in that latest form before you render.

Grazie
PeterWright wrote on 9/9/2009, 12:21 AM
Thanks for the suggestions Grazie.
The thing is, rendering is completing fine - it's just that once it's finished, the progress bar says 100% (1 of 7) and Vegas is frozen. On other occasions it's said (1 of 2) or (1 of 4), when there's only been one file involved, so that seems to be a "clue" as to what's gone wrong.
Grazie wrote on 9/9/2009, 12:43 AM
Maybe the render outcome is fine, but the process isn't. It should, as you want it to be, and that is STOP and come back to VEgas. There is something putting a brake ion the system, especially IF you have to do a Ctrl+ . . .to kill off VEgas. That's not right. It's the process that is not completing, and maybe THAT is 'cos you have an issue around CPU <> System activity - hence my suggestions.

Grazie