SL MkIII keyboard controller from Novation

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.

1 Like

How would you expect that to work?

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!

Wow, would expect MIDI feedback to work really.

It works well on LCXL, LKminiMK3, LPminiMK3 and LP-X.

It’s well worth emailing them with a feature request. Maybe it’ll get added eventually!

2 Likes

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.

It can be done. It’s more or less the same on any mk3 device. And it’s “simple to code”……

And when I mean simple to code, you just need to:

  1. Remember the initial value
  2. Store it
  3. Log any changes
  4. Store it
  5. If you leave the “page” on the novation, know what page you are on
  6. Restore the previous page when you go back to it from the above stored values
  7. Read that stored value so if the value is sending is below or above and doesn’t “jump” to the new value sent
  8. And then figure out how to make the lights work (cause you have to do some midi channel translations just for the lights alone)
  9. ……
  10. ……
  11. Harumph……

Edit: also none of this is performed on the LP I am using….its a script running elsewhere

Ita all in the programmers manual :upside_down_face:
You’ll prolly wanna brush up on your Sysex :wink:

I’ve been discussing with them about this feature for several years, and it’s probably not going to happen.
But yeah, contact them, who knows ?

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.

1 Like

Upgrading the firmware to include some of the new chord and arpeggio features in the new LaunchKey Mk4 controllers pads sure would be nice.

Or are they planning for an SLM4 controller ?

2 Likes

I would bet that both SW and HW in SL and Launchkey are quite different and therfore LK updates are not easily transferable to SL.

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.

1 Like

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.

1 Like

Hey! i know this is an old thread. But i have a Mk3 along with an Octatrack, A4 and DT. Could you walk me through your controller set up? Thanks

Has anybody created a midi keyboard with the snap-to-scale keys of the SK MKIII? I was just getting excited before I learned about the 16 step limit.

Although a bit cumbersome, you can chain patterns to create longer sequences than 16 steps.

2 Likes

… and set a sync rate for each pattern, so it can last 4 (maybe 8) bars. Each of the 16 steps can be subdivided into 6 micro-steps.

2 Likes

Oh interesting. I am not interested in chaining patterns for my use case, but maybe a subdivision would work

Guess what I’ve found out the other day

My 150 EUR M-AUDIO Keystation does have release / note off velocity, while SL doesn’t!

Now I don’t want any keyboard without note off velocity anymore, it’s such a useful expression / mod source.

1 Like

I feel your pain.