nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Keyboard fails to transmit Midi to Cubase and shows Script Errors.

MeanGreen7

My keyboard fails to transmit Midi to Cubase after updating to latest firmware and Hardware Connection Service. It will send Midi for maybe 1 minute after initially loading an empty project, and then the Cubase Midi script service opens and shows a series of error messages. I have tried reinstalling the HCS and deleting the device from Audio Midi Setup as suggested. The Midi Studio Panel shows that the keyboard is sending out information.

Find more posts tagged with

Komplete Kontrol Keyboards

Accepted answers

PoorFellow

https://community.native-instruments.com/discussion/comment/261685#Comment_261685

I did not know that NI suggest not using MIDI 2 currently, as I have been using it before the update with no issues. Clearly something happened with the update, so for now I will go back to MIDI 1.

Thank you !

I do not know exactly how far Midi 2.0 implementation has progressed but I have this quote with reference for you (more info in post by timrae_NI quoted) :

Quote Timrae_NI , May 5 , 2026 :

So my previous advice still stands for now:

MIDI 2 mode is not recommended, you'll significantly increase the chance of instability and bugs and afaik there is currently zero benefit for end users of using midi 2.

Anyway then I agree that you should still follow up and pursue the issue with NI Support when they gets back to you, if for nothing else then to inform NI of the issue that you think introduced (remember to respond to NI AI email confirmations also !)

All comments

PoorFellow

https://community.native-instruments.com/discussion/50742/keyboard-fails-to-transmit-midi-to-cubase-and-shows-script-errors

Did you set the keyboard to Midi 1 before you deleted the device from Audio Midi ? : How to Switch a Kontrol S-Series MK3 Keyboard to MIDI 1.0

Also then have you given full disk access to all NI apps and DAW ? : How to Enable Full Disk Access on macOS and also added NI apps and DAW to the Local Network if prompted ? (Ref.: How to grant audio apps access to your local network on macOS 15 Sequoia)

MeanGreen7

Yes I have tried that and so far it hasn't helped. I have attached a picture of the error messages I get in Cubase. It seems to be an error with the Midi Device Script, and sometimes the field is populated with even more of the same error message and freezes Cubase.

PoorFellow

https://community.native-instruments.com/discussion/comment/261673#Comment_261673

I am far from being an expert in anything Cubase but these I/O settings looks wrong to me , especially if you claim to be using Midi 1.

@Uwe303 , you are very knowledgeable about Cubase , what do you think ?

MeanGreen7

No actually I am trying to use MIDI 2.0, and I have been before I updated. Since I have updated though, it seems to have broken the connection between the keyboard and Cubase. I tried with MIDI 1.0 and everything functions normally.

MeanGreen7

Thanks for your help btw. I have also contact NI, but figured I'd post here as well in case others have had the same issue.

PoorFellow

https://community.native-instruments.com/discussion/comment/261676#Comment_261676

I tried with MIDI 1.0 and everything functions normally.

Thank you for clearing that up.

Then I think that you should consider your attempt to use Midi 2 as the cause of your problem. (But I am a bit confused that you first reported above that setting Midi 1 did not help).

At the moment then as far as I know then NI still advice that you do not use Midi 2.0.

However you should clear up things with NI Support and remember to tell them that everything functions normal using Midi 1.0

MeanGreen7

My point about MIDI 1 was just that switching to it, then switching back to MIDI 2(after deleting the device) did not help fix the MIDI 2 issue. I thought a "reset" might help since it was suggested.

I did not know that NI suggest not using MIDI 2 currently, as I have been using it before the update with no issues. Clearly something happened with the update, so for now I will go back to MIDI 1.

As a side note, I tried to use MIDI 2 with a VST application outside of Cubase, and it worked fine. So the issue is a communication error with Cubase and not the MIDI output of the device itself.

I appreciate the help, and I'll follow up with NI when they get back to me.

Uwe303

Good to know cause I use maschine stand alone with the MK3 keyboard, there I need midi 2.0 and cubase. Hope native get it sorted soon.

PoorFellow

https://community.native-instruments.com/discussion/comment/261685#Comment_261685

I did not know that NI suggest not using MIDI 2 currently, as I have been using it before the update with no issues. Clearly something happened with the update, so for now I will go back to MIDI 1.

Thank you !

I do not know exactly how far Midi 2.0 implementation has progressed but I have this quote with reference for you (more info in post by timrae_NI quoted) :

Quote Timrae_NI , May 5 , 2026 :

So my previous advice still stands for now:

MIDI 2 mode is not recommended, you'll significantly increase the chance of instability and bugs and afaik there is currently zero benefit for end users of using midi 2.

Quick links

Unanswered questions