The "cumulative bog effect"

PipelineAudio wrote on 4/22/2003, 12:20 AM

I notice in vegas that after there are a lot of takes whether or NOT they are in use in a project, vegas gets really sticky and boggy. Also a lot of fades, splits and etc, even if they are at the very END of a project make the whole project boggy. Doesnt seem to matter how many tracks are playing

A 5 minute 64 track project seems to run much better than a 24 track project of 30 minutes, no matter how many tracks are actually in use at the time

anyone else seeing this? Are there related things Im missing ?

Comments

stakeoutstudios wrote on 4/22/2003, 3:48 AM

It's true, the more splits there are the worse it gets.

I have a project where the vocals are really cut up and it's a nightmare!

wazer wrote on 4/22/2003, 6:45 AM

I've tried to get a whole MIX-CD done in the V4.0. (74 min., 14 tracks - each 8-10 min. long)
After an hour of editing i went back to the V3.0...
I have to wait approx 5-8 seconds, before the V4.0 starts to play the session..
This is frustrating.

After all in the V3.0 i can use the AUTOFADE algorithm ... :)

w!

Ben wrote on 4/22/2003, 7:46 AM

> It's true, the more splits there are the worse it gets.

I have a project where the vocals are really cut up and it's a nightmare! <

Yep, I've noticed this too. Very annoying - never happened in Vegas 3. I do a lot of stuff where there can be a load of edits and cuts in an extremely short space of time (Aphex Twin stylee) and Vegas 4 does really struggle with this for some reason.

I do find it strange we're having all these problems with V4; what have SF changed that's caused it all? If it's bloody ASIO, I for one could really do without it...

Ben

drbam wrote on 4/22/2003, 9:13 AM

<<I have a project where the vocals are really cut up and it's a nightmare! >>

I'm curious if you were to render the "really cut up" tracks whether this problem still occurs? Are you all saying it seems clearly related to the degree of edits in a session? I'm disappointed to keep reading about the bugs with 4.0b. I'm continuing to use Vegas 3 and have yet to install ver. 4 because of all this. I do a ton of editing in Vegas (splitting tracks, comping, creating loops, envelopes, etc), so this report is especially troubling. :-(

drbam

decrink wrote on 4/22/2003, 9:55 AM

I agree here. I've had several projects that I worked on in 4 and had to take them back to 3 to get them done. It really stinks because I don't want to be trading apps back and forth plus any edits I do in 4 can't be brought over to 3 for stability. It must have to do with asio because I can record but not play in asio and play but not record in Windows Classic. If I do one or the other, it gives me the stutters, buzzes and clicks. And I've got a deadline on a major film edit and it looks like I won't be able to use 4.0. And if I install 4.0b it all gets worse...

stakeoutstudios wrote on 4/23/2003, 9:31 AM

to be fair, this isn't happening on projects I started in Vegas 4, only the ones I started in Vegas 3 and imported to Vegas 4...

coincidence?

incidentally, it renders OK.

drbam wrote on 4/23/2003, 10:08 AM

<<to be fair, this isn't happening on projects I started in Vegas 4, only the ones I started in Vegas 3 and imported to Vegas 4... coincidence?>>

This is interesting. . .Can anyone else confirm that the "bog" bug only happens on imported sessions?

Thanks,

drbam

decrink wrote on 4/23/2003, 10:09 AM

Webpuppy (or others) is it possible to 'clean up' projects that were started in V3 so they will play properly in V4 or is it just necessary to start any new ones in V4? I'm leary about starting bigger projects and putting in the work and having later tracks start getting buggy...
Would you have to import all the wav files again? And place them, and...sounds like a lot of work for something that should 'work'.

SonyMLogan wrote on 4/23/2003, 10:44 AM

I have found some bottlenecks in the code involving projects with large numbers of events, but I am curious if anyone has noticed if a project with a large number of takes is also causing problems, or if the root cause is the number of events. Anyone?

PipelineAudio wrote on 4/23/2003, 12:32 PM

Takes as well,cause it, even lots of takes on muted tracks

For me this happened in vegas 2 and vegas 3 as well

CDM wrote on 4/23/2003, 4:38 PM

there is a way to "unbog" the project when you have a lot of events on a track. Create a new track and spread out the events on more tracks. This absolutely helps and is verified by the Vegas team.

PipelineAudio wrote on 4/23/2003, 10:46 PM

I'll try that, but then wont the CPU bog down due to needing multiples of the same fx plugins?

If you could send busses to other busses this would be OK, but...

hey,

how about we ask SF to let us send busses to other busses?
and busses to assignable fx?

oh boy!!!

stakeoutstudios wrote on 4/24/2003, 5:24 PM

I've been asking for the busses to busses routing since vegas2! would be so useful! mmm submixes of submixes!

The code to Vegas must be mind boggling... crikey.

My solution to the unbogging is to render all the split events without FX to a new track and then run the now single event through the same FX.

As this was mostly vocals it worked very well. Still a bit of a pain however.