MIDI Problem with Komplet kontrol

Since I turned on my Mk3 in the middle of a Cubase session, my DAW and the Komplete Kontrol software only partially detect the Mk3. Let me explain: when I launch Komplete Kontrol, I can browse for a sound and I can hear the different samples. I can also browse directly from the keyboard interface. However, as soon as I load a sound, the keyboard stops sending any signal — it doesn’t play.

So I checked the MIDI settings in the Komplete Kontrol software, and the keyboard does not appear there, which means I can’t select it.

I restarted my computer yesterday, and it worked again — it showed up in the MIDI device list. Today i can't… I don’t understand this issue.

If anyone can help me find a solution to this problem, thank you in advance.

Find more posts tagged with

Comments

PoorFellow

https://community.native-instruments.com/discussion/50169/midi-problem-with-komplet-kontrol

I checked the MIDI settings in the Komplete Kontrol software, and the keyboard does not appear there, which means I can’t select it.

Use the stand alone version of Komplete Kontrol software

Try checking if the keyboard is set to Midi 1.0 and set it to Midi 1.0 if it is not to see if that makes any difference : How to Switch a Kontrol S-Series MK3 Keyboard to MIDI 1.0

Else then try checking the Windows Device Manager which shows the MIDI device under "Sound, Video, and Game Controllers" to see if there are more entries for the keyboard , Else I am not entirely sure if one could remove the keyboard (while it is turned off/not connected) and then re-add it to see if that makes any difference. But I am not sure how this works so I advice you to make a backup of Windows prior to doing anything so that you can revert any changes

kal-el

Thank you for your advice. I followed the steps and I’m already on MIDI 1.0.
I’m going to check the Windows device now.

PoorFellow

https://community.native-instruments.com/discussion/comment/257417#Comment_257417

P.S.

There could maybe also be something else Midi that could be blocking the keyboard.

DunedinDragon

Depending on the DAW and your setup, if you were to launch the DAW or Komplete Kontrol at some point without the keyboard turned on or an external audio interface enabled it will modify your configuration so that the MIDI and audio aren't configured correctly.

For example, I use Ableton and my normal setup is to have my external audio interface powered up when I'm using it. If for some reason I go into Ableton without the external interface on it will reset my configuration to point to my internal audio interface which isn't connected to any speakers. The same happens if I launch into Ableton without my keyboard powered up so it defaults to the sound card's MIDI configuration.

Vocalpoint

Agree with others.

Over here - I power up everything up in a very specific order before ever starting Studio One. It is the last thing to get started.

Have never ever had any issue with device detection.

And I never start up any device mid-session when already inside Studio One.

VP

DunedinDragon

Just to add to VP's comment, I do exactly the same since I have multiple external devices connected both direct and on a USB hub. I've found everything plays most nicely when I turn on all my devices BEFORE I power on the computer AND I turn everything off AFTER I shut down the computer. Interestingly the PC shuts down slightly faster if I leave all external deviced powered up, then turn them off.

I don't know if it's the same on Windows 11, but after a bootup I typically need to give it a few moments to suss out and allocate the memory for all the external devices, but then everything works and responds nicely and quickly.

Vocalpoint

For me it's

4:00am - Machine wakes for imaging/backup

7:30am - I power on the Samsung TV (Monitor) and see the Win 10 logon screen. Next I power up the RME UCX-II, then the S61MKII, then my Presonus Monitor Station and then I logon.

7:40am - Then (and only then) - do I start Studio One/Studio Pro and get to work.

Have never ever encountered a missing device or any MIDI weirdness or any kind. I use no hubs either - all devices have their own MIDI port direct on the motherboard.

JesterMgee

Just switch on your MIDI device then load up your DAW, it's no more complicated than that.

kal-el

First of all, thank you to everyone who took the time to reply. 😉

I’ve been able to identify the problem a bit more precisely. When I turn on my KK MK3 MIDI device, it is detected and works perfectly.

However, when I turn it off — even if Cubase or any other software is already closed — it is no longer detected as a MIDI device afterwards. In other words, if I turn the keyboard back on, it is no longer recognized by any software, including Komplete Kontrol in standalone mode.

For it to work again, I have to restart my computer, and then everything works normally again.

So I’m wondering if this could be a Windows issue.
My MK3 driver is up to date, but I haven’t tried uninstalling and reinstalling the keyboard yet.

Do you think that could solve the problem?

Vocalpoint

https://community.native-instruments.com/discussion/comment/257960#Comment_257960

Can you check to see if the Hardware Connection Service (v2.07) is installed and running? For the MKIII - this service is critical to correct integration with any DAW software.

This service is installed separately via Native Access.

And it wouldn't hurt to open Device Manager (with your MKIII off) and then turn it on - and watch for nodes to appear on the Device Manager tree. Also check for any yellow (!) exclamation marks on the Device tree as well.

kal-el

"Can you check to see if the Hardware Connection Service (v2.07) is installed and running? For the MKIII - this service is critical to correct integration with any DAW software."

I checked and re-installed the hardware.

" open Device Manager (with your MKIII off) and then turn it on - and watch for nodes to appear on the Device Manager tree. Also check for any yellow (!) exclamation marks on the Device tree as well."

I checked , it's ok, no yellow "!"

Vocalpoint

https://community.native-instruments.com/discussion/comment/259013#Comment_259013

Should be good to go then.

Quick links

Unanswered questions