Comments

TheHappyFriar wrote on 5/11/2008, 5:00 PM
yes. normally when it thinks it should be done but a filter starts REALLY lagging. But no one said a first communion was a fast affair, right? :)
baysidebas wrote on 5/11/2008, 5:03 PM
By the time it's finished it'll be a second communion.
jrazz wrote on 5/11/2008, 5:13 PM
:)

It did finally complete. It started lagging when I had a velvet matter plugin applied to a track that had an event with the opacity down to 65% so that another track would show through. It craaaaawwwwwwlllllleeeeddd. I opened up task manager and saw that during opacity modified events, only 1 core is utilized.

j razz
Steve Mann wrote on 5/12/2008, 3:26 PM
John Meyer did a comparison chart of the different effects in Vegas and their affect on the render time. Opacity, if I recall, was the slowest of all. Presumably because every pixel in every frame has to be rendered.

Others have noted that you can apply the opacity filter to only one short event, and the entire timeline crawls.

The workaround is to render the event that requires an opacity change into a new AVI file, then bring that AVI file to your longer timeline. Or, put that event into another project by itself and bring that projects VEG file into the main project timeline.
jrazz wrote on 5/12/2008, 4:35 PM
Thanks for the tip. It did take a lot longer than I expected it to, even with no recompression selected (and 90% of it required no recompression). Hopefully I will remember to do that next time as I did not realize it could affect the entire render process.

j razz
johnmeyer wrote on 5/12/2008, 6:05 PM
Here's a link to that old post about fx times:

Results of render times for ALL Vegas fX

As noted in some of the other posts in that thread, some fX will get faster or slower, depending on the settings, although others will not. I didn't attempt to determine speed vs. settings, but just came up with my estimate of a "representative" setting for each fX.