Page 1 of 1
Latency in return tracks?
Posted: Fri Nov 18, 2016 4:21 am
by aspen1135
I know that return tracks will
not be latency compensated if it is bused out to an audio track. However, I really like busing return tracks for mixing stuff sometimes. I've heard you can disable the return sends on the rvb bus and it will start compensating again, but from my experience I'm not 100% sure about this as I usually try it but it'll sometimes will get re-enabled when I add or delete returns to try new reverbs or combinations. I was wondering if there's a way to manually calculate and compensate return tracks using the 'track delay' feature, or if the best workaround to is dedicate one of the 12 sends as a reverb/sfx 'mixbus'
this wouldn't really be a problem if it was a 12 send limit

damn you ableton. Love & Hate.
Re: Latency in return tracks?
Posted: Fri Nov 18, 2016 6:05 am
by fishmonkey
as you said, disable the associated sends on the audio tracks that you are routing the returns back to:
https://help.ableton.com/hc/en-us/artic ... ation-FAQs
if you don't disable them you potentially have an infinite loop, which is indeed hard to compensate for...
Re: Latency in return tracks?
Posted: Fri Nov 18, 2016 3:59 pm
by Stromkraft
aspen1135 wrote: I've heard you can disable the return sends on the rvb bus and it will start compensating again, but from my experience I'm not 100% sure about this as I usually try it but it'll sometimes will get re-enabled when I add or delete returns to try new reverbs or combinations. I was wondering if there's a way to manually calculate and compensate return tracks using the 'track delay' feature, or if the best workaround to is dedicate one of the 12 sends as a reverb/sfx 'mixbus'
Of course you need to disable any new sends. Do you actually think that's harder than manually calculating new latencies as you
add and remove plug-ins that I would think is quite common to do during working with
Live? If so, good for you, but I couldn't understand this preference myself.
And the track delay, if put ahead of the beat, only delays all other tracks by adding latency. Idiotic! I'd rather it actually shifted both MIDI and audio events earlier
without delaying all other tracks, though of course this is not possible for real time input.