Solo Button in Ableton Live

Question

Was "How can I map a button to a solo in Ableton 9  so the button light corresponds to the solo light."

When I press the button on the ipad the light flashes on then right off. The solo light stays on. I have this problem with all my controllers.
 

Comments

As far as we can tell from a little playing around, Ableton Live expects a momentary to control the solo/cue button, but does not give standard MIDI feedback as to whether it gets turned on or off. In fact, we're not seeing ANY midi being echoed back from Live regarding the solo/cue button.

This is an old topic:

https://forum.ableton.com/viewtopic.php?f=2&t=26701&view=previous

but we're not aware of any workarounds using a standard MIDI controller (like MIDI Designer) and Live. We'll be investigating in any case.

Thanks!
Dan

---

One really interesting thing to investigate is STC for Ableton Live.

http://stc.wiffbi.com

Thanks!

---

DAN,
IS THIS THE SAME CASE WITH THE MUTE BUTTON IN ABLETON? IF NOT, WHAT'S THE WORK AROUND?
THANKS,STEVEN

---

Hi Steven,

We haven't found a workaround yet, but I'd suggest that you work with supercontrols and subcontrols and map to the VOLUME (if you need to make another track, do) instead of the mute buttons, if they act weird... my understanding is that the mute buttons are fine but that the solo button doesn't feed back directly.

Let me know if these instructions help move you further ahead. If not, I could give some more concrete examples.

Thanks!
Dan

---

Actually, you can do this pretty easily by making your OWN solo buttons using button groups. Ableton doesn't allow you any other way with a generic MIDI controller.

---

check the answer below. Works for solo buttons, will work for others perhaps.

---

There is a work-around for this using a control surface scheme
I noticed I got feedback when using the MackieKontrol scheme for my KorgNanoKontrol2

You simply change the Midi Data of your Control surface to the corresponding AbletonLive Control surface scheme

Im not sure of all the mappings for MackieKontrol but for starters
Solo(1-8): G#-2 -> D#-1
Cue(1-8): C-2 -> G-2
Stop: A5
Play: A#5
Record: B5

Note: you most likely want momentary vs toggle,
also your control surface (Note) data may be transposed a little differently, off an octave or so, as mine was.

---

xvgem100: do you have a layout or page you want to share on this? Anything would be helpful, even if it's just a proof-of-concept. Thanks!

---

Sorry for such late reply, I opened the Consts file of the MackieKontrol scheme(found in the Ableton directory under remote scripts) and found a MidiCC-to-NoteValue sheet/chart, from there I was able to map stuff, mostsome of the setting names are straight forward, some notsomuch.

---

That's great. If you ever want to share anything concrete, the forum here (see mididesigner.com/share) is the place to do that. Thanks for responding!

---

No Prob, I also forgot, another way of doing this is just simply adding a ghost-track w/empty AudioEffects Rack and doing double mapping

---

Sorry, what problem are you solving with ghost-track and that? I  might need a bit more of a hint here, though I'm VERY familiar with racks and can guess what a Ghost Track is. Totally irrelevant, but have you seen this vid?

Answer 1

Change Toggle Button's MIDI Min-Max to 64-127 (instead of 0-127)

This is regarding Live not sending a remote signal to turn on a light when the button is pressed, yes?

It MAY BE the same issue that we see with the NanoKontrol for no lights indicating a Rec Arm is pressed: UNLESS one changes the (toggle button) values from default of 0 to 127, to 64 to 127, which fixes Ze Problem!

Comments

opening ableton and trying now ;)

---

Oh wonderful, thanks for sharing your knowledge!

Answer 2

Change Toggle Button's MIDI Min-Max to 64-127 (instead of 0-127)

This is regarding Live not sending a remote signal to turn on a light when the button is pressed, yes?

It MAY BE the same issue that we see with the NanoKontrol for no lights indicating a Rec Arm is pressed: UNLESS one changes the (toggle button) values from default of 0 to 127, to 64 to 127, which fixes Ze Problem!