Launchpad X custom modes led issues
Hey there,
this is more of a launchpad x issue and not necessarily drambo, but since I can't find any useful information regarding both, I'll ask here - maybe someone had a similar problem with this daw + controller setup.
I recently upgraded my launchpad mini mk2 working with drambo without issues to newer and sexier X sibling. I created 4 custom modes in components, that are blank midi notes without light on different channels per mode.
The mapping in drambo works fine and it does what I want, but I have to touch the pads to light up. whenever I change custom mode - they don't light up automatically which makes it a bit unusable since you have to trigger every note to light the led up and get a visual feedback. I also had issues with leds blinking and not providing steady light, but found out that it's a mode slot related thing (which I don't know how to change).
I could possibly use the mapping based on conditions with launchpad in legacy mode, but utilizing 8 custom modes was one of the reasons i decided to upgrade the controller. If anyone has the device and is willing to help me out with it, I'll be grateful. Other workarounds and known limitations of lpx with drambo will also be appreciated.
Cheers!
.
Comments
Custom modes are different from the programming mode Drambo uses. In this mode a specific mapping is invoked by sending a sysex message.
I have an LP mini and no X, but you might want to try Legacy Mode (check manual / Novation website about how to enable it. Legacy mode has the advantage that you can map the entire pad including the top and right button rows. And you can easily switch back to another (custom) mode. Programming mode in contrast can only be deactivated via SysEx or restarting the Launchpad.