I’m also still very interested in a script. Custom mapping is nice but the lack of fluid control inhibits creative flow. Still seems odd the flagship controller was not mapped in favor of more limited models. Hopefully it will make it to the top of the to-do list soon! Thank you for your help!
1 Like
You said:
On 8 March was ASAP, today become quit long and so tomorrow will be NEVER?
I could understand you are so busy guys to recover all issues but I would appreciate if you give the highest priority to fix this issue.
I don’t want disturb you guys but I said issue because I tried to create a script for my MK3 and was a mess.
1 Like
I will be happy with this Novation SLMk3 script
For what it’s worth, I’m able to use the SLMKII (Even older than III obviously) with no problems. Although I did have to use the SLmkII template editor to upload essentially a blank template to my SLMKII first. I see the MKIII has a template editor programme too, so perhaps it will work the same?
Thank you Bunny for your suggestion which I did with a new template
However, I was able to create a script but just for some controls, however, many others is completely dark, working bad or not working. 
You’re welcome.
Sorry to hear it didn’t work.
It’s very important with scripts, that is 100% compatible with different midi keyboards.
I’ve been a Cubase user for ages, and has stopped upgrading with Cubase 11. The new Midi Remote stuff is great, and I did think of buying one of the Launchkey keyboard + Cubase 12. It it’s the only bigger full featured midi keyboard, that steiny has put out with Cubase 12.
More scripts that works 100%, is = more sold Cubase copies + more sold midi keyboards
1 Like
Hey there, I just wanted to check in and see if there has been any progress on this front yet. Thanks!
I have the knobs set to : Value Mode = Relative Twos Complement ( last option in that Box ) and it works great 
Is their one for the Arturia Keyland mk2 61 key? Thanks.
I´ve switched to Ableton live, the SL MK3 works without any hassle…try to do your work better Cubase…!
This post was flagged by the community and is temporarily hidden.
I got my new SL49MKIII, but still no chance to use it in Cubase 12. I tried to use it as Macki HUI, works terrible. When I set the MIDI-Input to the SLMKiii, not all functions work. But as soon as I use the MIDI-Output to the SL MK3, Cubase got cracy and some Softsynths begin to sound. Seems like there coming some crazy Midiinputs from the Controller. I can’t figure out, what’s wrong.
So I ordered the cheaper Launchkey 61 MK3. And I’m happy, but still confused.
For the cheaper Model Launchkey, there exist a perfekt Script for Cubase, and all Buttons, Faders and Knobs works perfekt in Cubase. But the Highend-Model SL MK3 (costs more than double the price) isn’t supported in the DAW, what a shame.
Does somebody has news about the work at Focusrite ? I think the programmers of the mothercompany takes the Job.
thx
I wrote Focusrite and Novation either Cubase about this issue
Fucusrite and Novation said the issue is Cubase
Cubase said high priority but is almost 6 months
What I would appreciate if Cubase say very clear that Novation SL MKIII DOESN’T WORKS WITH CUBASE and close this issue once at all
I’m actually thinking about adding this keyboard to my setup, so in case I finally do, I will surely create a script for it as I did for the Arturia Keylab MK2 and the Komplete Kontrol MK2.
I have two questions by the way:
- How does the keybed feel?
- What do usually the 8 displays I see, show? Volume/Pan and instrument parameters?
Note that,the way I see it, it would be much easier for them to create a script than Steinberg, because simply they know the correct midi implementation to follow. I’ve noticed that for Cubase they suggest using HUI, but that is nowhere near their tight implementation for Live.
I have had a poke at Novation about this via an email exchange with their “customer support” having given the SL Mkiii a zero star review and stating I could not in all good conscience recommend this to a friend or colleague.
They kicked into the long grass by saying they had passed it to their developers to look at. It won’t be.
It does not work in Cubase. It is that simple.
I am going to have to move back to Ableton to get any work done, and Cubase can whistle for my money because I won’t be buying it. The trial version will be deleted and that will be the end of it.
It is a pity because I prefer Cubase in many ways, but I need to make music, not learn Javascript!
I do wonder though, given it is around five years since the SL Mk3 was launched, whether there is some kind of time limited agreement between Novation and Ableton where Novation agree not to support other DAW manufacturers in return for a kickback of profits from Ableton.
I can’t think of any other reason why there is no support for other DAWs.