render time increased

smeagol wrote on 3/24/2004, 4:27 PM
I produce a daily television show using vegas video 3.0c that is 28 minutes long. Usually, this takes 2 hours and 10 minutes to render on my hp 2.53Ghz machine with 512mb ram (winxp). However, today, it is taking 7 hours to render and I don't know why. This computer's sole purpose is rendering this broadcast and I haven't changed any settings. It is not online or anything. Does anyone know what would cause the render time to increase? (mpgeg2) Thanks alot!

Comments

TheHappyFriar wrote on 3/24/2004, 5:48 PM
you cropping something somewhere by acident? Also, are you rendering to the same size/field order as the origional footage?
hugoharris wrote on 3/24/2004, 5:56 PM
If a velocity or opacity setting has been accidently changed (say, to 99%) you won't see the difference on the timeline but it has a significant effect on rendering times.

Kevin.
smeagol wrote on 3/24/2004, 6:22 PM
That may be it. I put an opacity envelope on my entire show for 1 part and may not have turned it to 100%. I will check this as soon as the render finished (2 more hours).
Thanks for the advice!!
Spot|DSE wrote on 3/24/2004, 9:10 PM
smeagol, i have a similar situation where I'm using opacity envelopes every 40-60 seconds on a (currently) 9 hour project. There is an Audit Envelope check script on the Sundance site that is wonderful for checking these.
http://www.sundancemediagroup.com/help/kb
johnmeyer wrote on 3/24/2004, 9:56 PM
Here's the direct link to my audit script:

Audit for event levels

This script finds all events where the opacity level has been set to a level only slightly less than 100%, or the audio level set to slightly less than 0dB. This usually is not intentional and results from accidentally moving the opacity or volume line while moving an event. Without this script, such an accident is very difficult to detect, and can result in long rendering times.

You can change the threshold at which the script detects an "error" by changing a variable at the start of the script.

The script detects changes on all events, both video and audio. However, there is no way, via scripts to check the track header levels. This is unfortunate, because I find that it is very easy to nudge these, especially if you use keyboard shortcuts. All you have to do is accidentally select the track header instead of an event, and then use the arrow keys, thinking that you are going to scrub on the timeline. Instead, you move the track header level. Since the script cannot detect or set these levels, it instead provides a reminder at the end of the script to check these levels.