How to display Ableton track colors on MIDI controller pads?
Hi,
Great to see 2.6 out of beta, thanks for keeping up the development!
Now with the new reactions working, is it possible to send the color of the track in Ableton to a controller RGB pad? I mean, pick up the color from Ableton, not write down manually a matching velocity value.
What I want to do is lay out all the tracks on my controller pads with their colors and then hit the pad to select the track. It is MUCH easier to select the right track when I can see the color. Counting tracks to find the right one from a bunch of identically colored ones is not really useful.
If it is possible now, I’d really appreciate some direction on how to do it… I’ve tried finding the functionality myself, but failed :-/
Cheers!
Of course! here is a slightly updated version, I just segmented out the blues into 3 categories. (regular, light, and dark). This was helpful for me to keep my color mapping reactions organized for all the Launchpad Mini Mk3 LED colors (velocities) I am using in my script.
For what it’s worth in this thread, I also attached an example script that elaborates on the included script from John’s tutorial post above. The only difference in my attached script is that it will convert all 69 possible Ableton colors into 13 specific MIDI velocities (colors to send to the controller). This way, the controller LEDs will become the general color of the Ableton track color – no matter which of the 69 color options are selected in Ableton.
I know that this potential is mentioned in the tutorial but I just wanted to share the leg work for anyone who stumbles into this thread. Peace ya’ll!
I’m looking for some help if possible. I’ve been trying to make a Reaction for sending the track color to Pad 1 on my Launchpad Mini Mk3 whenever a clip exists and also remove the color from Pad 1 when the clip is deleted.
The problem is that the LED Feedback from the “Session Box” mapping is overriding my Reaction’s pad color assignment. My Reaction works fine without a “Session Box” mapping but I need it to coexist with a Session Box mapping for clip launching.
The LED Feedback settings in the Session Box have been turned OFF for “Clip Stopped” but it seems to still be breaking my Reaction regardless.
Any advice would be greatly appreciated! Thank you!
To clarify, the problem is that the Session Box is causing the pad color to dissapear from the first clip slot when I create another clip in a different clip slot. My Reaction works initially and will assign a color to the pad but as soon as I create another clip, the Session Box takes over the first clip and turns the color off.
Hey, thanks for the reply!
I have set the Clip Stopped feedback for the Session Box to “None” but it seems like “None” still sends a velocity to the pads, turning the LED off/black/velocity 0. It is in fact, set to “None” and not “0”.
I even tried turning all of the Session Box LED feedback drop-down options to “None” just in case something else was causing the issue but I think I might be out of luck due to the nature of how the Session Box mapping LED feedback acts unless there is an additional listener or condition I could use as a workaround.
Thanks for checking it out, trolo. I found that if I randomly remove this line of code from the python script file, my pad color doesn’t disappear as soon as I add another clip but if I play the clip and then stop it, the color goes away unfortunately. (I have no python skills at all but am desperately trying anything I can think of).
clip_slot.set_stopped_value(feedbackArr[“ClipStopped”])
Sign up
User registration is currently not allowed.