Light up buttons on launch control XL.
So I read somewhere on the internet of things that pads/buttons on launch control XL can be lit up if they are sent a note that they are assigned to in the editor.
I’ve just quickly tried it with midi out pointed at XL but had no luck making it work.
Anyone’s had any success with this? Is it actually possible? It would be grand to have a visual feedback with mutes.
You simply have to follow this protocol:
Ok, so I got it to work by sending the note back to the controller. The problem now is that as soon as that note is learned to a mixer/sequencer function it is excluded and seems no longer to be sent to the track and the pad doesn’t get the message anymore. The same goes for CC messages.
Could there be a way around this hive mind?
I’ve just tried to do this on the master track but still, as soon as I midi learn the CC it is no longer allowed through.
Is this a bug or is it done to stop function messages from interfering with the track? If so perhaps this should be exclusive to notes but not to Cc messages? @giku
However when midi learn is removed the midi message is still disabled which I guess is a bug 🐛
@giku This seems to be in line with the cleanup issue after deleting a module. Also, what's the blocking logic with MIDI learn?
It's 2 separate issues (btw. the bug is fixed)
So, yes, when midi message is used to control a knob (mapped) it's blocked for further processing. (a natural logic ;)
@supadom I wonder what exactly you're trying to achieve because sending note data to toggle LEDs wouldn't interfere with incoming CC or notes.
Theoretically you may map a knob and then connect it's output to MIDI CC generator with the same CC number
I’m trying to map a toggle button sending cc to mute tracks and forward the same message back to the controller to turn the led on and off. As soon as the cc is mapped the message no longer reaches the controller.
I’ll try that instead of trying to map mutes in mixer.
Hard to know what you're doing without seeing it. What you describe doesn't work without external loopback.
Here's what I consider necessary without native controller suport:
The zip contains the animated gif, display is broken on the forum here.
Cool, thanks @rs2000 this is working!
I’ve updated to the latest beta and the buttons on my launch control XL aren’t illuminating anymore! @giku
Scrap that. Restarted the device, it is working now.
Encouraged by the success of lighting the pads for mutes i today proceeded to make the button I use as record button to light red. I eventually managed it by sending a CC85message of a value 15 which stands for red.
So it does work when transport is stopped but when transport starts it stays lit and want turn off at all until I stop the transport.
Any ideas what could be the cause? I’ve tried to change the channel and the CC thinking maybe it is receiving some conflicting message from somewhere else but the problem persists. @rs2000 @giku
@supadom Like said, supporting LED feedback before Drambo supports it natively can easily become a dirty, inconvenient, limited and laborious hack. D doesn't even know about what you send to the controller so every status change has to be done by yourself and since D has no status monitor modules either, it will always be some kind of "blind trip" until D supports it out of the box.
Fair enough, I thought that once a workaround works it is reliable. No biggie
Just found it strange that it works with mutes but not with transport. It’s the same cc message, the only thing that’s different is velocity.
Does it? If you hit a mute button on screen, will the status be reflected on the Launchpad?
Like with the mutes, you'd have to maintain your own transport state in your remote controlled project and hope that it won't go out of sync under any condition.
What you could do of course is to have constant status colors on the pads, simply indicating the button functionality and watch the iPad screen for actual transport status. It's easier to watch small symbols than to hit them precisely with your finger.
Sorry guys I’m out of town but will check this when I’m back. Cheers
No it doesn’t light up if I tap mute on the screen.
It all seems to be synced up alright in terms of stuff lighting up and if the state is off sync when I open the project the bits that are out of sync ‘wait’ one more press until it is. No complaints there. :)
There’s nothing coming out other than the midi from my rec mapped button and it operates on its own exclusive midi channel that’s why I’m puzzled why this works when the transport is not running but just lights up but won’t turn off when it is. @giku ?
I’ve just tried this in standalone with no other midi routings/mappings and behaviour is the same so that’s something do do with Drambo itself.