Waiting for Steinberg, is basically dying waiting.
As I understand it, I can request a refund within 14 days. Cubase 15 is clearly broken in several different, albeit perhaps minor, ways. No dying for me.
Yeah, better use that refund option. I took me 1-2 years to understand, that what Steinberg announces and what they deliver are two totally different worlds.
Only plug out your USB Controllers when Window is shutted down.
And take care das that all you controllers you wanna use or even you use normally are powered on
Good news, my nanoKontrol2 is working again - thanks to Pete Brown (@Psychlist1972) for his help in narrowing down what was going on.
The SysEx message I saw was actually coming from the nanokontrol2 (not to it, my bad for misreading Pocket MIDI), which means it was indeed responding to the Steinberg script - but something else was going wrong after that.
What got it working again was writing a clean (new) scene to it in the Korg editor. Worked fine after that.
Only fly in the ointment is that Cubase sets the nanokontrol2 to CC mode, so if you use it in a different mode outside of Cubase, you’ll need to set it back to that mode every time after quitting Cubase.
Next job is to look into whether Cubase can run an ‘on exit’ script to change the nanokontrol2 mode back to how it was. But at least it’s working now 
Yes. You have to implement it in a dedicated event for when the device driver gets deactivated.
deviceDriver.mOnDeactivate=function(activeDevice){
//Place the sysex you want here
}
1 Like
Thanks that looks good - can I simply add this into the KORG_nanoKONTROL2.js script in Public? Actually scratch that it gets overwritten - I can copy it over to Local and use it there I think.
I’m afraid I don’t have much JS scripting skill. I do have the nk2 MIDI implementation which shows the SysEx commands and have been able to send SysEx to my unit via Pocket MIDI, so I think I’ll be able to add in the correct SysEx into your example.
Yes, this is the suggested way. Don’t forget to disable the original script.
Yes. You need the command midiOutput.sendMidi(activeDevice,[array of bytes]) .
Say that your sysex is something like F0 12 00 32 00 15 F7. You can write:
midiOutput.sendMidi(activeDevice,[F0, 12, 00, 32, 00, 15, F7])
1 Like
Fantastic - will give it a try shortly.
At the moment I have it working okay with the Mackie Control legacy device, and the Public script disabled.
With an altered script I will perhaps be able to build on the nk2 MIDI Remote surface for other functions, while not having to hard-mode-change the nk2 before using other DAWs.