Ableton Forum

Sick! Congratulations on the release!

Combine with Javelina to get Octatrack-style delay control and beat juggling.

https://sonoranmusicdevices.gumroad.com/l/javelina

Are you sure your graphics drivers are up to date? I had similar issues with M4L a long time ago, and updating my graphics drivers resolved it.

In my experience, sending data too quickly (but no faster than MIDI events) through live.remote~ causes it to "choke" i.e. not send all the data that was sent. My live.remote~ has Normalize set to "off" and Smoothing set to 0. In this thread , there is some discussion about the choke point possibly ...

As I wrote above, this is a complete non-issue in Live 12, and Ableton finally properly addressed the issue.

Live 12 introduces the "Keep Latency" feature on each track. If you disable that for tracks on which you are monitoring and recording synced hardware, then the recorded audio will line up ...

Finally. As of 12.1:
Swap the Sample Inside of a Simpler: Select a Simpler device and press the swap button. In the bottom left of the browser there is a toggle switch that allows you to change where you want to hot-swap the device you’ve selected, or the sample inside of it. Swapping the sample ...

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 ...

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 ...

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 ...

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 ...

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 ...

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 ...

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.