Ableton Forum

I think the behavior in your case is due to the way Ableton's delay compensation system works. To perform delay compensation, all tracks are delayed to the longest track latency time . The problem for you is that compensation is happening to OTHER tracks - not your track. So, when you tap the outpu...

No, that would only be the case IF Ableton implemented my suggestion. Currently, the tempos don't drift, but they are not latency compensated.

Converting beat-time values to samples under the hood seems like it would always be inaccurate at certain tempos due to floating point math and how certain numbers do not divide evenly. If I had to guess, then I would say that is why Ableton has not implemented this. As I wrote in this thread , I th...

Just to make sure we are talking about the same thing: the issue is the lack of delay compensation for beat-time devices like Beat Repeat and Arpeggiator? If that is the case, then I don't think any wrapping in Max for Live devices will help. IIRC, I have tried that for days. I have my own Max for L...

I'm testing this up and down and keep latency has nothing to do with tempo synced plugins running in sync. Correct. I just deleted my reply above, as I had replied to the wrong thread. Someone much earlier described why Ableton resolved to do this - because they want a Max for live device that has ...

Many of us are aware that built-in device modulation synced to the Live transport (i.e. synced to a specific beat-time position) is not compensated. E.g., Beat Repeat and Arpeggiator are not latency compensated when they are preceded by latency inducing devices in their signal path. As a proof-of-co...

Monsoon has been updated. The update is free for all existing users. The change log is below. I am really pleased with the update. I did not think it is possible to have Monsoon run on individual tracks, but after a month of research and coding, now it is. I think this brings Monsoon as close to a n...

This is very similar and possibly the same fundamental problem as what I posted about here:

viewtopic.php?t=248971

You're welcome. BTW, I looked back at my emails again, and I had also raised a ticket with Roland. The last communication I got from them was that they had forwarded the repro steps to their development team so they could take a look at it. Sad to hear it is apparently still an issue.

I just looked back through my emails with Ableton support, and at the time we both kind of agreed it was probably an issue on Roland’s end. That is where I left it.

I never resolved it, and I am no longer using that Roland plugin. Sorry.

Did you set a negative clock sync delay as I described earlier?

Yes. That does not work in my case. I am working on a Max For Live product which requires using the chain activators, and I do not want to go into the details right now.

Thanks for confirming. I already reported to support. I can't use Utility as a workaround, because my effect it is a MIDI effect. Also, I must use the chain activators in order to keep my MIDI effects processing regardless or whether they are muted or unmuted. I ended up coding a Max For Live device...

I now see what you meant when you said that "when turning an encoder you get some 'room' before reaching the actual value," HOWEVER that is NOT what is happening with my example. If what you described was actually what is happening in my example, then there would be no issue. In your examp...