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.
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.
The thing that is hilariously disappointing about this is that the SL 61 Mk3 is supposed to be novations flagship midi controller, yet its not supported properly in any DAW apart from ableton,
The steinberg MACKIEUI has so many bugs its unusable so you need to turn it off to avoid midi problems.
Lots of issues that could be solved if cubase and novation make a script for midi integration into cubase.
@m.c The SL 61 mk3 feels like a keyboard synth, the semi weighted keys are more synth like (but i’m used to fully weighted), the knobs and faders feel perfect, probably the best i’ve used, especially the infinite turning knobs. the pad buttons feel amazing as well.
The software that comes with it allows you to completely customize everything it does, banks and banks of different CCs to each fader or knob, its actually pretty amazing.
the displays show the knob location (as its an infinate knob you need to see where it is) it also shows what it is controlling, and also what CC it is assigned to,
On the main bank/template display it also shows what fader and knob is currently being moved, and you can customize what that fader is called and it will show up on the screen as you move it.
its one of the most complete midi keyboard controllers, and it is really a joke that it cant properly be integrated in cubase, I dont have much faith in cubase solving this issue, happy to be suprised though
Ahh, sorry. First I read “Launchkey mk3”, but you mean the big one. I got you!
At the moment I don’t see any resources for implementing it. I know I said something else a year ago, but we had to adapt our policies.
As there are sooo many MIDI controllers already on the market and being released every few weeks, it is impossible for us to address them all. Therefore we try to encourage the manufacturers to develop the scripts themselves. Like Arturia did lately.
Hey Jochen, any chance to get at least some specifications from the manufacturers? For example, I would happily create a script for the sl mk3 and in fact buy it, since I think it’s a pretty good controller, but I wouldn’t want to get into exploring all over the net for sysexes and so on, as I’ve done for the arturia keylab mk2.. It just takes enormous resources for no obvious reason.
thank you very much for your answer.
If I well understood, the solution would be to change keyboard and continue using Cubase unless we change and move to Ableton.
Being clear now we can close, once at all, this issue.
The solution now is on my hands.
Just placed an order for the SL MK3. Whenever @Jochen_Trappe kindly provides us with these essential info, I will surely create a script, which may be useful. At least it will surely be useful for my own workflow
Thank you @Jochen_Trappe! So far, so good, all leds and displays are working as expected, and I’m in the process of building the pages. However, since I know you’re willing to help, can you please have a look at the issue with mixerBankZones that I mentioned earlier?
Say we are on a certain page (I have one called Mixer for obvious reasons). We change bank and everything is OK. Then, say, we move to another page (for example instrument quick controls). When we return to the first page (Mixer) the bank resets to the top one.