vegas 5b chokes when track 1 muted

DouglasClark wrote on 8/9/2004, 2:15 AM
My 8 track/3 bus 24/44 mix has been running fine with several Waves Renaissance plugins on each track/bus. But now when I mute track 1, the tempo slows (pitch stays same) with lots of hash (clicks, pops...) Same happens if I solo another track (so track 1 is effectively muted). I can solo other tracks as long as I also solo track 1 (with fader down but not -inf).

If cpu/memory were a problem, it would show when I ADD the track to the mix, not when I take it out, right? So this seems very strange. I tried moving the track to another position...same problem.

Track 1 is mono. The plugins on track 1 are: Waves REQ4 mono, Waves RComp mono, Waves RVerb (stereo?). Could combining stereo and mono plugins on a mono track be a problem? (there is no mono RVerb, but there is a mono->stereo version). The mix runs fine as long as track 1 is not muted.

Anybody else experience anything similar?

Douglas Clark
Denmark

Comments

DouglasClark wrote on 8/9/2004, 2:29 AM
Well...the problems goes away when I disable the the RVerb on track 1. But I need the verb! I don't want to have to disable the RVerb every time I need to solo other tracks. Any ideas?
Douglas
drbam wrote on 8/9/2004, 6:31 AM
>>(there is no mono RVerb, but there is a mono->stereo version). The mix runs fine as long as track 1 is not muted.<<

Your problem seems indeed strange. I don't have any suggestions other than to say experimenting with mono>stereo version is certainly a good idea. What about inserting the verb as an assignable efx? I'd try some different routing to see if some solution or cause can be found.

drbam
SonyEPM wrote on 8/9/2004, 7:35 AM
Please send the .veg file (no media needed) to Dr.dropout<AT>Sonypictures.com and we'll take a look. Please include the Waves version #s also (we have all Waves plugs here and work closely with their developers).
SonyEPM wrote on 8/11/2004, 8:53 AM
Looked at your project- you do have 18 separate Waves plugs running on both tracks and busses so I'd expect that to be a heavy load, on my rig the CPU is running close to 100% at all times (~30% with Waves disabled), yes I repro the gapping playback with Waves enabled.

I upped my playback buffering (Options>Prefs>Audio Device) to .7, all is well, no gapping. Please give that a try-
PipelineAudio wrote on 8/11/2004, 11:48 AM
so this is unrelated to the problem some of us are seeing where, if you solo a track the CPU spikes and playback becomes choppy?
DouglasClark wrote on 8/12/2004, 2:48 AM
My sound card is an Echo Mia using ASIO Echo WDM v.1 (v6.08) driver. Buffer size [Options, Preferences, Audio Device, Advanced, Configure] was 512 samples (11 ms) (default value). My 8 track/3 bus 24/44.1 mix with 18 Waves plugins plays back fine when all tracks are enabled, but clicks and pops ONLY when track 1 is MUTED.

I increased buffer size to 1024 samples, and had the same problem.
I increased buffer size to 2048 samples, and only got clicks when I moved the mouse while track 1 was muted.
I increased buffer size to 4048 samples (46 ms), and the problem dissappears. I even added an Ozone plugin (cpu hog) on the Master with no problem....but a second and third Ozone added to busses cause the MUTE-gapping/clicking problem again. (the third Ozone really made Vegas stutter!)

And then Vegas crashed when I removed the third Ozone plugin during playback :-( That must be a no-no!

Well, many thanks for the help, SonyEPM! It's the first time CPU load and buffer size has been an issue for me. But I still don't understand why the problem originally appeared only when a track was muted.

I'm running Win XP SP1 with lots of other software and resident processes installed. I think it's time to implement my second "audio-only" partition, to increase CPU available for the heavy-duty plugins.

Douglas
Denmark