MIDI Chase Event For Ableton

Max For Livebeginner
uPlay's icon

uPlay

Hi Team,

Just arrived here looking for some tutorials how to create devices, but I have no idea how much difficult or easy to make my device...
I am a newbie to the Max For Live world while I have been using M4L packs/devices in my Ableton projects.

I would like to use MIDI Chase Event function in Ableton Live 9.5 which is famous in Logic Pro. This function triggers the last MIDI event when you start your song from half position.
https://support.apple.com/kb/PH13442?viewlocale=en_US&locale=ja_JP

Anyone please help me where I should start from?

Thanks,
Toshi

Evan's icon

Evan

Not easy if you want it to be set-wide (still not easy if you want it to be just on one track). It would have to scan through every track, look for MIDI events, build a database, and then reference that database to see if there is a MIDI note that should already be playing when you start the playhead.
I would spend my time making something a bit more creatively useful in M4L, personally.

EDIT: It might be possible to just ask about currently playing clips when the transport goes from off to on. That seems like an easier approach.

uPlay's icon

uPlay

Hi EVAN,

Thanks for your reply.
If it can find the "one earlier" MIDI note for example, it will be possible to send it. The problem is, how can it search the "one earlier" MIDI info, how can I implement the repeat method in the Max device? For example, it might be possible to use "for" loop method to repeat the detection task until it finds the "one earlier" MIDI note.

Evan's icon

Evan

There's no such thing as a 'for loop' in Max (at least not in those terms). What I suggest is look at the currently playing clip when the transport starts, and get the current position of each clip. If there should be a note playing at that time, send out a note.

I usually try to help out with implementing this type of stuff, but this feature doesn't get me excited enough unfortunately. ;)

Good luck!

Tom Swirly's icon

Tom Swirly

I first reported this bug to Ableton four or five years ago. It's sad to see that people are still struggling with it years later but Ableton has always very much prioritized new features over bug fixes.

Unfortunately, using M4L to get around this is going to be much too hard.

What I'm doing myself is to bypass Ableton as much as possible, running as much stuff as I can from Max. But that's a huge amount of work too...