I want to have visual feedback on my launchpad in user 2, that’s why i programmed the attached patch. It creates 8 visual rows in user 2 mode plus a visual metronome. That works quite well.
Question: Lets assume I use the attached patch in my Live set. As soon as I MIDI learn one of the Launchpad rows (let’s say full bottom row = press midi learn, then press bottom left, then bottom right, then let go both) to any knob in live, the lights functionality of the attached patch breaks. That is quite logical to me, because the midi info seems to be "absorbed/swallowed" by the Midi learn. But is there a way around it?
MAx4Live listens to the control surface, by it’s nature when you midi map a button it disables the control surface for the button….
You’ll need to look at creating the functionality of your midi mapping native within M4L….
I’m just creating a scene of faders for my Ocotp4d device that does exactly this, i’ve not got the launchpad with me to understand what you’re achieving but which buttons are lighting for the visual metronome??
The visual metronome can be put on any row of the launchpad, running from left to right.
It does not restore the existing light states of what was lighting up before.
Its best to test the patch with a launchpad…
Would you mind sharing your experience on the scene of faders functionality you created?