Fixed in 5.0d: Titles made Chroma Blur horrendously slow

acappella wrote on 2/14/2005, 4:27 AM
If you've noticed the Chroma Blur filter making your renders amazingly slow, you should install the 5.0d release. In 5.0b, it appears that a media generator (e.g. text) on any track will affect the Chroma Blur filter on any other track, making your render take 75x longer. I did a search here and didn't see anyone describing this behavior, and it isn't mentioned in the readme for the latest update.

In Vegas 5.0b, when my video track just has a color curves filter, it renders about 40 frames per second. When I added a "Chroma Blur" filter, it slows down to about 15 frames per second. Not too bad.

But it only keeps up that speed until it hits the first Media Generator, which can be on any other track. (In my case, it's the opening credits using a Text generator.) Once it hits the media generator, the Chroma Blur takes about 5 seconds PER FRAME.

I just installed the 5.0d release, and the problem is fixed. Preview is still really slow with the chroma blur enabled, but rendering speed is restored. So my render will be done in a couple hours rather than a couple weeks. :-)

Comments

farss wrote on 2/14/2005, 4:53 AM
Yeah,
I'd read of other odd things in 5.0, not broken things but things like adding an extra video track with 3D composits in it made the whole render slow down. Probably the whole code module was run on every frame for the track even when there was nothing there.
Good to see minor annoyance being fixed, would be MUCH nicer if they told us what was happening.
Bob.
ken c wrote on 2/14/2005, 10:48 AM
I'm glad to still be sticking with Vegas 4. The more I hear about V5, the more I don't trust it.

Just like Windows XP SP2. Not a move forward. I still use Windows 2000 pro on my main pc, it's so much faster and better than XP, that's on my laptop and wife's pc.


ken