Ableton Forum

Unless something changed with Live 11, Live tracks have never respected midi channel information in the way one might expect. Regardless of what channel the info arrives on to the track, what is passed to the devices is always on channel 1 (or omni, I forget). Look for threads like this: https://for...

is there a max device parameter that can receive string, text? that's the only thing that miss to my needs Receive string text from where? A basic message object can display any text you want, but I don't think that's what you're after. I don't have any of the control scripts you speak of, so we're...

It's possible, it's just that the only way I know to pull it off purely through M4L is inelegant under-the-hood... but I went ahead and brute-forced it for y'all anyway. Since this forum doesn't support attachments, I uploaded it on the other thread: https://cycling74.com/forums/searching-for-a-devi...

chapelier fou wrote: ↑

Sat Apr 24, 2021 5:59 am

Observe the path live_set selected_parameter

I tried that first, but parameters can be adjusted via control surface w/o being selected.

I looked through the LOM for Max 8 last night, and I don't see anything that would let you observe changes in parameter values across all devices, or ever within one device. You have to set a live.observer module to monitor an individual, specified parameter... meaning you'd need a bank of dozens of...

To me it absolutely makes sense that the [plugsync~] example works, as it basically buffers the not messages. It should be problematic with synchronous notes, though. yeah, I like the plugsync option even less than the micro-delay option for that very reason. I was surprised to see that a 0ms delay...

I had to deal with something similar about a year ago in a Live 10 M4L project. I'm afraid I don't have any great news for you in terms of what was discovered. I found no truly perfect/desirable methods for obtaining complete event order control over the MIDI activity live feeds to devices. In my ca...

Thanks for confirming. It seems that enabling the Scale button for a Clip sets the current/control surface scale to whatever the Clip setting is... so I can see a potential argument against being able to remotely enable Clip Scale... I mean, this button isn't MIDI-mappable either... there's got to b...

This is seriously impressive.

I may have to buy it just to bathe in the aqua & salmon splendor of its interface.

Keep making more devices!

Running some tests on the v11 API additions. Looks like I can change the Key and Scale that a MIDI Clip is set to via the API if (and only if) the Scale button for that clip is already active. ... but is there no way to enable or disable the Scale button for a MIDI Clip via the API? Thanks to anyone...