Ableton Forum

I'm glad I helped. Have fun !

Sounds like midi feedback loop. Try to figure out what’s causing it by unchecking unnecessary routings in the midi prefs tab.

Also I made this some time ago
https://maxforlive.com/library/device/9163/cf-reservoir

Put the 3 notes on top of each other and use an arpeggiator in random mode.

I’ll definitely check this out !

I’ve always found help and helped people on this very forum !

I think it’s accessible via the Discord. But I can’t find them there…

I would narrow down your tests to get what the issue really is. I'll do some tests if I can, no promises.

Hello !

firstly, it's good advice to use live.thisdevice as it outputs a bang when the Max API is ready. I generally use a single instance and link it to something like [s ---init] although you need to be aware that the timing between different receive objects will not be (?) predictable. If ...

Oh nice, thnx !
Will test when I’m back home.

Hi,
I noticed that setting the tempo via M4L seems to have a higher latency than API usual latency.
It's quite noticeable, and I can definitely hear a weird groove if, for instance, I play a simple clip containing one note on each quarter note and changing the tempo from 120 to 60 on beat 3.

I ...

It's tricky because it depends on the tempo automation curve.
If you restrict it to linear segments, maybe it's simpler to calculate ?

You're not missing something. Max either ignores or is unaware of the Exclusive settings in Preferences.

In Max, it's possible to disarm all tracks first, then arm the desired one. But users who don't use the exclusive arm may not like this. Maybe the developer could offer an option in the device ...

+1000.
But more generally, let us define what the actual beat is.
So the tempo is actually the right tempo, so we can use tap tempo, and set the metronome in a usable way.

Nice use case for shaper, thanks for the advice !
(meanwhile I made my own trapezoid gain scanner in M4L).