Originally Posted by
mostapha
Nosferatu, where'd you make that up?
OP, Ableton does something called "automatic plugin delay compensation" or something close to that…what you're hearing has nothing to do with audio buffers or any of the normal sources of latency. What you're hearing is that when the effect rack turns on, it suddenly takes more time to process the audio going through the device rack than it did to process the audio not going through the effect rack.
In order to keep everything exactly in time, Ableton figures out how long it takes to process that audio and delays everything else by that amount.
My suggestion is to stop being mad/frustrated at/with it for doing exactly what its supposed to do and use it right.
Either leave your racks on all the time or put the effects in a send. You can use google to figure out how to map a midi macro to turn a button or knob into a wet/dry control (i use the Send A and Send B knobs on my vcm, as well as the track mute buttons for a third) using dummy channels and utility plugins.
The track delays will always work out, and you won't get that pop unless it's caused by an abrupt change to your audio signal based on what something in your rack does, which I can't help you with unless I have a copy of your .als file.
Also, what are you doing to make the CPU work too hard? My old macbook performs just fine with what I do until I start using too many midi instrument racks in a DJ template…and then only when I try to make it send analog through multiple effects while other tracks are playing and a lot of other stuff is going on. I still wouldn't qualify it as really working too hard…it just gets a bit hotter than I feel safe running.
Bookmarks