Comments

mbmjk wrote on 2/11/2002, 2:30 PM
Anyone have a fix for this? When I use too much reverb is when it happens most.
way2slo wrote on 2/11/2002, 2:47 PM
just let u know direct x reverb is a big cpu hog. how many reverb plugs r u running at the same time? more info please.
SHTUNOT wrote on 2/11/2002, 6:46 PM
Try raising your audio buffer settings...options/preferences/audio...try keep as low as possible without problems. Each time you get a noise just raise it untill it goes away. Remember that in doing so your response time will get slower. It won't respond as quick but thats a good thing because it will be able to do more. Also try printing your effect. Later.
mbmjk wrote on 2/12/2002, 9:42 AM
I'm running reverb on 3-5 tracks at once.
mbmjk wrote on 2/12/2002, 9:42 AM
What do you mean about printing my effect?
timoheil wrote on 2/12/2002, 10:14 AM
With your setup you should be able to run far more than 3-5 reverbs for individual tracks. As reverb-effects in general are very CPU-hungry you should consider running the reverb on an effect-bus instead of using it as a track-effect. But that shouldn't be the actual problem. Maybe the latency-setting for the Delta-driver is too lo low? How many samples/milliseconds is it?
JoeD wrote on 2/12/2002, 4:41 PM
- Seen this with cracked versions of plug-ins. You using any cracked versions (not to put you on the spot).

- Waves is notoriously cpu intensive (especially early versions - check for later versions)

- Make sure you're not clipping in the verb (or any other plugs in the chain). It's easy to forget about this.

- Are you putting separate verb plugs on each track or on a buss?
try the buss only and see what happens.

- then we come to Maudio and their drivers. Notorious for crackling audio. For XP use the .26 only but for win98 use 4.1.22.27 as you can adjust ASIO and MME buffers separately along with the best audio fidelity for Maudio cards.
But you say it only happens with the verb...in which case the prior items may be the culprit


JoeD