The Mkii versions can be found sometimes for cheap. Highly recommended that one. The best midi controller I’ve ever had. Still integrates automatically with ableton 12, no drivers needed - which is good since those are nonexistent now.
Also the fatar keybed is the best. They didn’t put that in the mk3.
Well I have say a knob set to CC74 on Channel 1 of the SLmk3.
Then I have my deluge sending CC74 to Channel 1 of the midi in of the SLmk3.
It does not reflect changes (visual feedback) on the SLmk3’s CC74 knob on the screen on the keyboard.
I am working on sending a CC through a new function on deluge which is supposed to have the opposite gear reflecting the change. But it seems that the CC is not affected whatsoever. I have done searches and it appears that the CC changes are only affected when you manually turn the knob (or automation of course) on the actual SLmk3, and that it does not have a function to accept external CC in the way I would have expected.
If I am wrong and you have a solution please let us know. Thanks!
From my google search on the topic it looks like they are aware of it, but its been years since a firmware update, I am guessing it’s maybe not sold enough to keep updating? That’s a wild guess.
Ah, interesting to know it works on SL MK3 as well. I did think it was a strange omission since it works on nearly all their other (newer) gear.
I used Drambo to take control of mine. Never looked at the manual! No sysex required at all, and no coding (well I guess Drambo is a form of visual coding really).
I will say (this may help someone), there’s a key difference when getting lights to work on the LCXL than the MK3 devices. The MK3 devices share identical values across pages. The LCXL doesn’t.
So, for example, if you’re using the LCXL bottom row of pads as mutes, and you change to a different uesr page, the lights may be out of sync with the actual state of the mutes.
To get round that, you simply use CV Sequencers to store the on/off states in Drambo, then set a little repeating timer to ping those values to the LCXL every half second or so. The lights will flicker a tiny bit.
Then when you change pages on the LCXL the lights update automatically.
The LPminiMK3 and the LPX don’t have this issue. They seem to share values across pages and you don’t need to muck around. You can let the Launchpad store it’s own values etc.
Honestly, I’m no genius and this stuff wasn’t hard to get working even for me. A bit of MIDI processing is all that’s required. I encourage everyone who owns these devices to dig in and try stuff. It really helped my overall knowledge of MIDI as well.
I would love if they added polyphonic aftertouch and gave us more than 16 steps in the sequencer. I almost returned mine when I figured out that was the limit. Learned my lesson on not reading the manual before buying. I think I thought I was getting an upgrade on the KeyStep Pro.
That’s what i think too. At least as far as the new arp, chord and sequencer features in the Launchkey Mk4s.
The user interface parts are there already on the SLM3. And the new features are now running on a lowly $120 USD Launchkey Mini 25. The new features aren’t processor hogs, so they ought to run fine on the SLM3. The only limiting possibility, could be storage memory, and that’s probably not an issue.
As far as “easily”, they’ve got the source code already, and people experienced with its development. But i only judge things as a software developer who would do this sort of thing daily.