Brothers we don't need such a pluggin because there is a button in track options near delay of the track that allows completely remove this latency. When you turn on monitoring on the track you just have to turn off "keep latency" button. Hope I help somebody)
Yes since Live 12. When I released these devices it wasn't the case. If you visit the product page you'll find this: - In Live 12 these two devices will become obsolete! Here's what the release note says: A Keep Monitoring Latency in Recorded Audio option has been added to the [right-click](Win) / [CTRL-click](Mac) context menu of the Monitor radio buttons for each track. This option is enabled by default, but when unchecked, recordings will have the same latency as if recorded with monitoring set to Off, regardless of which monitoring mode is selected. If you plan to grab Live 12 in the near future I would advise you to skip these devices! : ) (Of course if you plan to stay in Live 11 for a while it can still help you! )
@@homelandelisabeth7090 yes, this is really button from live 12, but before I didn't want to record something and I didn't know about it, when I tried to find something it seemed to me that nobody knows about this function but it is really useful. Thank you for your devices from all ableton live 10-11 users)
Mainly because If I record multitracks, things can shift from each other. If the RLWM option is enabled Live will process every track's latency separately, only applying the latency to the take that the actual track has ( Plus it's group track, and the Master) If I have two different tracks that I record at the same time, and one of them has latency while the other doesn't they'll wont be in sync with each other. My device can fix this, but I got used to simply not using this option. : )
That wouldn't help. 1: You would have to manually calculate the latency. 2: It would introduce more latency into your project which means: Now you would have to go though all your tracks again and redo the first step... :D
It's only a valuable option if you already done all the recording... but you would have to keep track on how much latency your project had when you recorded specific clips, plus for example if you recorded two clips into the same track in two different times when your project had different lateny (because you added a plugin since the first record) then you could only compensate for one of the clips.
It turns the monitoring ON after you start recording. (First it deactivates it if it was enabled so live recognise it as disabled, then start the recording, and then it turns the monitoring back ON, so the latency doesn't get baked into the take.)
Ableton should do it on its own. For my live performance I turned all the internal compensation of and did it manually. Sad, real sad. Also Ableton has no plugin crash protection, still massive gui latency. And the worst thing is seeing all in all its still the best solution.
Hi, did you test Bitwig 5 with its global modulation abilities? Not that i m suggesting it's better than Ableton overall - but at least it's more stable, with sandboxed plugins , and can partially replace some m4l devices on its own.
Really good! It's incredible Ableton doesn't have this natively. Question: is there any chance to upgrade this device to have automatic nudging for Session View Clip recordings, live, on the fly? Would be insane!😊
I don't think so... but honestly I don't think you should record with DelayC off at any time. I can't really think about a valid scenario where you should turn it off.
@@homelandelisabeth7090 I've been doing it for a long time for recording with good sounding results. It's not compensating plugin latency across tracks I'm pretty sure, but since I'm refraining from heavy latent fx, it sounds ok. I find this to have less latency than having it on with "reduced latency while monitoring". I'm totally open to hearing why this is not good if you'd be kind enough to explain 🙂. I've watched some vids on this recently.
@@rocknrory So Having Delay compensation turned off will result in.a really chaotic result. All the tracks that have plugins on them that adds latency will play back later than they should be related to the ones that has nothing on them. So for example: You have three tracks, two that has nothing, and one with soothe on it. so the first two tracks will play back as they should, but the third will be late with 40ms compared to them. Somewhy you decide that you want to add two soothe to the secound track, now the following happens: the first track will play back as it should, the second will be delayed by 80ms and the third with 40ms. As you grow your project the problem get's even worse when you add latency heavy plugins to your project. However if you have delay compensation enabled in this case all the three tracks will be delayed by 80ms (because that's the largest amount off latency that one of your track needs) so they'll be in sync with each other. So I would advise you to always have this option enabled! The "Reduce latency when monitoring" option works differently: When you enable it every track that you record enabled become it's own entity and doesn't get any other tracks Latency added to it, only it's own. So for example if you have a track with a plugin on it that adds 100ms latency to your project, and one that has 10ms and one that has 0, if you record/monitor each of them you'll hear the first one 100ms off, the second one 10ms off, and the third one 0 ms off. And the recorded takes will get that amount of latency added to them ( Plus your sound-card's roundtrip latency and if your Master track has anything on it.) Like in this Pic: drive.google.com/file/d/1xRssmlEqkZahMzHn0q7QY-83UWcKE-Gp/view?usp=sharing I recorded a clap at the same time with monitoring, with the Reduce Latency While Monitoring option enabled. I personally don't like to use it, but it could be a valid option for anyone, and doesn't mess up anything.
@@homelandelisabeth7090 Thank you for your detailed response, I appreciate it. You've made me understand how "reduced latency while monitoring" works. I'm still rather perplexed because recording guitar or MIDI with delay comp on in a project with plenty of vsts on all tracks has tremendous latency when monitoring. It's unplayable. The rest of the tracks sound in sync of course, due to the delay comp. Now if I turn off Delay Comp, my armed MIDI track / guitar track has basically no latency and is totally usable. If I play back my project, all the other tracks are usable. If soothe2 or something with high latency is enabled on a track (usually drums or synth bus for me), that instrument will be noticeably delayed, so I just switch off the most latent plugins and accept the small latency of everything else. Not ideal, but better than having Delay Comp on and not being able to record. I just turn on Delay Comp after recording my takes. Reduced latency while monitoring makes no meaningful difference to me here as well. My r/t latency is 6ms so that's not the issue. I guess I'm just curious how people are even having usable monitoring with delay comp on to even justify using your plugin to correct it after recording.
Even when opening my project template with no recorded tracks and all latent plugins disabled, delay comp on still gives noticeable latency when monitoring a simple ableton piano. Delay comp off has no latency at all.
Oh this is excellent! It's crazy that Ableton doesn't do this automatically.
Awesome plug in, crazy that we still need it in 2023.
Brothers we don't need such a pluggin because there is a button in track options near delay of the track that allows completely remove this latency. When you turn on monitoring on the track you just have to turn off "keep latency" button. Hope I help somebody)
Yes since Live 12.
When I released these devices it wasn't the case.
If you visit the product page you'll find this:
- In Live 12 these two devices will become obsolete!
Here's what the release note says:
A Keep Monitoring Latency in Recorded Audio option has been added to the [right-click](Win) /
[CTRL-click](Mac) context menu of the Monitor radio buttons for each track. This option is enabled by
default, but when unchecked, recordings will have the same latency as
if recorded with monitoring set
to Off, regardless of which monitoring mode is selected.
If you plan to grab Live 12 in the near future I would advise you to skip these devices! : )
(Of course if you plan to stay in Live 11 for a while it can still help you! )
@@homelandelisabeth7090 yes, this is really button from live 12, but before I didn't want to record something and I didn't know about it, when I tried to find something it seemed to me that nobody knows about this function but it is really useful. Thank you for your devices from all ableton live 10-11 users)
Another banger
Game changer thank God.
Bouta cop that immediately 😂😂😂😂💯💯💯💯💯💯
aaaaah love it it will save me a lot of time
This is pure gold
You mentioned that you don't like to use the Reduced Latency When Monitoring option - why is that? Thanks for great devices as always!
Mainly because If I record multitracks, things can shift from each other.
If the RLWM option is enabled Live will process every track's latency separately, only applying the latency to the take that the actual track has ( Plus it's group track, and the Master)
If I have two different tracks that I record at the same time, and one of them has latency while the other doesn't they'll wont be in sync with each other.
My device can fix this, but I got used to simply not using this option. : )
@@homelandelisabeth7090 Thank you for the clear explanation! All the best to you
What about setting the same latency value in track delay? It is basically doing the same
That wouldn't help.
1: You would have to manually calculate the latency.
2: It would introduce more latency into your project which means: Now you would have to go though all your tracks again and redo the first step... :D
It's only a valuable option if you already done all the recording... but you would have to keep track on how much latency your project had when you recorded specific clips, plus for example if you recorded two clips into the same track in two different times when your project had different lateny (because you added a plugin since the first record) then you could only compensate for one of the clips.
Works for fix the TR8s Latency problems?
I never used one, but I would say no. It only fixes internal latency, not anything hardware related.
@@homelandelisabeth7090 Thnks!
Does this not work for headphone mixes then, as it turns monitoring off while recording?
It turns the monitoring ON after you start recording.
(First it deactivates it if it was enabled so live recognise it as disabled, then start the recording, and then it turns the monitoring back ON, so the latency doesn't get baked into the take.)
Ableton should do it on its own. For my live performance I turned all the internal compensation of and did it manually. Sad, real sad. Also Ableton has no plugin crash protection, still massive gui latency. And the worst thing is seeing all in all its still the best solution.
Hi, did you test Bitwig 5 with its global modulation abilities? Not that i m suggesting it's better than Ableton overall - but at least it's more stable, with sandboxed plugins , and can partially replace some m4l devices on its own.
Really good! It's incredible Ableton doesn't have this natively. Question: is there any chance to upgrade this device to have automatic nudging for Session View Clip recordings, live, on the fly? Would be insane!😊
It's a bit tricky but I think it's possible, so maybe I'll include this feature for a future release : )
Apparently programs like Gig Performer are better for live latency
Does this still help if I record with Delay Compensation off? Would I set it up differently if so?
I don't think so... but honestly I don't think you should record with DelayC off at any time.
I can't really think about a valid scenario where you should turn it off.
@@homelandelisabeth7090 I've been doing it for a long time for recording with good sounding results. It's not compensating plugin latency across tracks I'm pretty sure, but since I'm refraining from heavy latent fx, it sounds ok. I find this to have less latency than having it on with "reduced latency while monitoring". I'm totally open to hearing why this is not good if you'd be kind enough to explain 🙂. I've watched some vids on this recently.
@@rocknrory So Having Delay compensation turned off will result in.a really chaotic result.
All the tracks that have plugins on them that adds latency will play back later than they should be related to the ones that has nothing on them.
So for example:
You have three tracks, two that has nothing, and one with soothe on it.
so the first two tracks will play back as they should, but the third will be late with 40ms compared to them.
Somewhy you decide that you want to add two soothe to the secound track, now the following happens:
the first track will play back as it should, the second will be delayed by 80ms and the third with 40ms.
As you grow your project the problem get's even worse when you add latency heavy plugins to your project.
However if you have delay compensation enabled in this case all the three tracks will be delayed by 80ms (because that's the largest amount off latency that one of your track needs) so they'll be in sync with each other.
So I would advise you to always have this option enabled!
The "Reduce latency when monitoring" option works differently:
When you enable it every track that you record enabled become it's own entity and doesn't get any other tracks Latency added to it, only it's own.
So for example if you have a track with a plugin on it that adds 100ms latency to your project, and one that has 10ms and one that has 0, if you record/monitor each of them you'll hear the first one 100ms off, the second one 10ms off, and the third one 0 ms off.
And the recorded takes will get that amount of latency added to them ( Plus your sound-card's roundtrip latency and if your Master track has anything on it.)
Like in this Pic:
drive.google.com/file/d/1xRssmlEqkZahMzHn0q7QY-83UWcKE-Gp/view?usp=sharing
I recorded a clap at the same time with monitoring, with the Reduce Latency While Monitoring option enabled.
I personally don't like to use it, but it could be a valid option for anyone, and doesn't mess up anything.
@@homelandelisabeth7090 Thank you for your detailed response, I appreciate it. You've made me understand how "reduced latency while monitoring" works.
I'm still rather perplexed because recording guitar or MIDI with delay comp on in a project with plenty of vsts on all tracks has tremendous latency when monitoring. It's unplayable. The rest of the tracks sound in sync of course, due to the delay comp. Now if I turn off Delay Comp, my armed MIDI track / guitar track has basically no latency and is totally usable. If I play back my project, all the other tracks are usable. If soothe2 or something with high latency is enabled on a track (usually drums or synth bus for me), that instrument will be noticeably delayed, so I just switch off the most latent plugins and accept the small latency of everything else. Not ideal, but better than having Delay Comp on and not being able to record. I just turn on Delay Comp after recording my takes.
Reduced latency while monitoring makes no meaningful difference to me here as well.
My r/t latency is 6ms so that's not the issue.
I guess I'm just curious how people are even having usable monitoring with delay comp on to even justify using your plugin to correct it after recording.
Even when opening my project template with no recorded tracks and all latent plugins disabled, delay comp on still gives noticeable latency when monitoring a simple ableton piano. Delay comp off has no latency at all.
thanks mang
Got It
I bet this can’t help when you have to comp the takes
Works with individual takes too! (just make sure you correct right after recording - before you add any new plugin to your project )
Narration by RatGPT….???