ticked off delete render

Sonisfear wrote on 10/7/2005, 5:25 AM
Okay guys...
I was rendering a crutial mpg for a cx leaving the country. it has been rendering for 11 hours so far. only 50 %completed. I desided to break the file in half so I press cancel.

Why....I don't understand why would Vegas delete the completed 50%. That is 11 hours donwn the drain and a cx that cannot get anything. Wow that ticks me.

Why not just close/finalize the file at it's current size. If Vegas is afraid of wasting space with uncompleted files simple have it ask.

"would you like to delete the process so far?" yes / no

And you need to put the render pause button in there.

Sorry to vent but these little things to vegas are big things to me especially in a world of HD render times in Vegas are way higher and we just don't have time to waste with such a simple button.

Comments

Liam_Vegas wrote on 10/7/2005, 8:10 AM
Sorry to hear of your problem.

The fact is... that is simply the way that MPEG rendering works. It is a non-triavial exercise to connect two pieces of MPEG together (there are extarnal tools that do it - but Vegas does not). Therefore... when you hit cancel... Vegas deletes the partially completed file.

If you were rendering to AVI - then it would not have deleted the file.

Making assumptions about how something should work is always a dangerous thing to do.
farss wrote on 10/7/2005, 8:11 AM
Vegas really cannot handle closing the mpeg file, how would you split this in half and then join it anyway. It can be done but it's not simple or goof proof.
If you need to fixed length GOP the I think you'd really be in trouble.
Bob.
Chienworks wrote on 10/7/2005, 8:38 AM
Also keep in mind that if you were doing a 2-pass render then at 50% Vegas hasn't started writing any of the output file yet!
johnmeyer wrote on 10/7/2005, 9:06 AM
Actually, none of the responses to the original poster's questions is correct. Vegas used to do exactly what Sonisfear wanted it to do. If you started a render -- of an MPEG-2 file -- and then stopped, the file would be closed at that point and you could use what you rendered up until that point. I have Vegas 4 on this computer and I just did a test to make sure my memory was correct.

Sony removed this feature in Vegas 6, for what reasons I have no idea. It was certainly technically feasible. Heck, even if the software didn't close the last GOP, the playback device wouldn't detect any error until it got to that point so, at worst, the only place you'd notice any problem is in the last one second of playback.

I used to rely on this feature all the time, and its removal has been a real pain.

Sonisfear wrote on 10/7/2005, 10:08 AM
Okay I am calmed down now...If you could only imagine the pressure from this client. and I would have been able to deliver if not for this issue.

But I am still a happy user. And this feature definately use to work.

I didn't need to join any files together the cx just need the ceremony to show his family .

Please put a pause render button. I know and use the task priorty function but there are times when I need the full power like playing back HDV files to a projector demonstrating High definition. Even one studder is enough to distract the cx from the story and ambience.

And even better if I could close Vegas and restart the machine.

Anyway as I said Vegas serves me well and I am happy with it.
Chienworks wrote on 10/7/2005, 10:16 AM
If studder-free playback is that important to you then you really need a dedicated computer just for playback. Dealing with clients that picky makes this a necessary business expense.

That being said, setting Vegas' priority to below normal has always allowed it to not interfere with playback on my systems.