Ableton Forum

I said the device that I posted earlier.

I haven't had a chance to look at jomtones's device yet.

Correction might be a stretch. Maybe an addendum is a better description ;) I found that setting multiple IDs with one action, as with the device I posted earlier in the thread, only writes one step in the history. I actually didn't know that. Functionally, the difference is one writing to the undo ...

Wow... well I cracked the bulk of it. Just need to RTFM a bit :D ... Question is now - live.remote vs a live.observer / live.object combo. Which is better for performance? Live.remote does NOT write to the undo history, live.object DOES. Generally you want to use live.remote to remote (get it?) con...

Observe the scenes, and if one (or a particular one) is launched, send the OSC data.
You're request is a bit wide open and I don't know how you're sending the OSC (UDP?), so I don't have any specific advice. But it's possible.

Oh that's Lives MIDI mapping being stupid with M4L stuff. You want to change the transition of the live.text to Both instead of zero to one. This will make the button double trigger when clicked with the mouse though. So maybe make two buttons, one for mapping, one for mousing.

is it possible to get the track name, and map the faders without actually focusing Live on a track? (so changing track away from the mapping plugin). Yeah that's possible. If I understand what you are asking. But I'm not really sure. Almost anything is possible with the API. You want this to be one...

Sweet! Good luck with the rest of the project.

Rad. It wouldn't be tough to do either of those things. Just copy the code that looks for the send control, and change the path to the volume/panning/etc. Instead of mixer_device sends 0, it would be mixer_device volume, or mixer_device panning. And the path would change to live_set tracks X, where ...

I'm away from the hardware until Monday, so I won't be much help until then with practical advice, but it looks like section 2.6.2 of that document you linked to earlier provides some insight into how colors are calculated. The MIDI values 0-127 are translated via a color palette. I do not recall if...

Sounds good - let me know if you have any questions, or just want to bounce some ideas around. I love nerding out about LED control schemes.

Woo! Glad I could help.

That sentence with the glasses was meant to read:

"can easily make it 8"

That patch should get you started on using and controlling just the matrix. I didn't start using js to do LED stuff until recently, but I've found it much easier to manage. Defining utility functions, and iterating through LED states/colors is way easier and cleaner in a text based environment. I ha...

Yep, I'd stay away from User mode. The convenient thing about the Push/2 is that you can selectively 'grab' and 'release' components of the control surface, and leave all other behavior intact. You're free to take a look at any of my devices to see how I've done it, but the older ones can be quite a...

Some questions: If you make a M4L Instrument, is there a way to override the default keyboard LED feedback? If so, is it possible to have an instrument that also takes audio input? Yes, there is, you'll be diving head first into the deep end of the control surface API, or using User mode. Only Audi...

Your welcome