Controllers with LEDs that don't listen - workarounds?

[Geminiclub]

Hi Guys,

There are a million MIDI controllers out there and almost all of them have LEDs of some kind but unlike Novation's Launchpad or Launchcontrol most don't let you control the LEDs with MIDI.
I have a Novation Remote SL61 mkii and I just got the Korg Taktile 49. I love both of them but neither take midi signals from ableton to their LEDs.

I use a key range on the Taktile's buttons and pads for patch changing (buttons) and setting the key of all diatonic controllers (drum pads, set up like a one octave keyboard). So I'd like the buttons and pads to stay lit so I can see which sound I am currently on and which key I am currently in.

Are there any known work arounds for controlling LEDs on controllers that don't automatically support that?
I know nothing about sysex (except that ableton disallows it) but would sysex be how these controllers internally control their LEDs?
If so does any body use Bomes, Midipipe, or m4l to get around these limitations?

[Quenepas]

I use a key range on the Taktile's buttons and pads for patch changing (buttons) and setting the key of all diatonic controllers (drum pads, set up like a one octave keyboard). So I'd like the buttons and pads to stay lit so I can see which sound I am currently on and which key I am currently in.

The only lit feedback is that from armed tracks and pads when hit. Also, have you ever had an issue with Taktile where only 15 out of all 49 keys make sound? Everything is setup (Makie/ins n outs) as the instructions but seems only 1 octave work. Hitting the +/- on the Taktile would shift notes but still only a few keys work, the others either do thing or do some weird random like changing from session to arragement.

Any info is welcome!