Why is my Kontrol S49 MK3 Silent in my DAW?

PJ Hoffman · 2024-10-28T20:27:07+00:00

There was an error rendering this rich post.

This problem has arisen in the past week. Previously everything was working well.

After booting up my Windows 11 computer, the KONTROL S49 MK3 input setting is unchecked in Komplete Kontrol's settings. I can't change that setting unless I unplug and then plug in again the keyboard's USB cable.

After I've done that, in my DAW, the new Cakewalk Sonar, I can set the Kontrol keyboard as an input and output device, but the unit doesn't transmit to the DAW. I can't play or record using the keyboard within the DAW. Occasionally an error message will appear that says Windows reports I don't have enough memory. (I have 64 GB RAM installed!)

At the same time, not in the DAW, the keyboard works fine with stand-alone instruments.

In "Device Manager" > "Sound video and game controllers", the device/driver KONTROL S49 MK3 is reported to be working properly but information below "Events" says "Device USB\VID_17CC&PID_2100&MI_00\8&236da33&0&0000 requires further installation"

I have spent three days updating, uninstalling and reinstalling, and checking settings. Any help would be greatly appreciated.

Find more posts tagged with

Windows 11

Komplete Kontrol Keyboards

Accepted answers

Jeremy_NI

https://community.native-instruments.com/discussion/comment/186973#Comment_186973

I've contacted you by email, my colleagues will need to have a deeper look into your issue.

All comments

DunedinDragon

It's been a very long time since I messed with Cakewalk, but I would assume it needs all the same configuration info any other DAW needs. When you say you've configured the S49 as an input and output device in your DAW, that's not typical. Your DAW needs to know what input channel to listen to for MIDI input from the S49, but typically you only need to configure that input and an appropriate audio output from your DAW.

In most DAWs the Device Manager entries aren't really relevant other than allowing Windows to have access to it. Generally you configure your DAW so that it receives MIDI input from the S49 keyboard device and has an appropriate audio device (typically the same one used for audio tracks) and that's all that's needed. You must have it configured correctly if it works standalone, so your DAW needs to emulate that same configuration.

On my old Sonar Platinum it looks like this on my Preferences:

PJ Hoffman

Thank you, Dunedin Dragon. You've clarified that Cakewalk doesn't need any MIDI outputs. However, this has not solved the problem.

I think the issue likely has roots in the NI drivers, especially suspect is "KONTROL S49 MKS", which Device Manager reports its installation may have not been successful. This is the driver that in Komplete Kontrol can be enabled only after I disconnect and reconnect the keyboard's USB cable. I also presume this is the driver Cakewalk Sonar by Bandlab (a new product based on the old Sonar) is unable to use to receive input from the Kontrol keyboard.

Again, up until about six days ago, everything was working. I recall that about then I updated the Kontrol's firmware but don't remember any other changes I may have made. Is this a bug in NI's firmware/software?

A little further information that may or may not be pertinent: my audio interface is a Universal Audio Apollo Twin USB.

Thanks again!

Jeremy_NI

https://community.native-instruments.com/discussion/comment/186783#Comment_186783

Make sure to have the latest version of the Hardware Connection Service as well as the latest version of Kontakt and Komplete Kontrol.

Maybe switch the keyboard to MIDI 1.0: How to Switch a Kontrol S-Series MK3 Keyboard to MIDI 1.0

Does that make a difference?

PJ Hoffman

Thanks. I've been working with the latest versions of the NI software and my keyboard has been set to MIDI 1.0.

After more work with the issue, it seems to boil down to this: I have to turn my Kontrol keyboard off and then on again in order for me to activate by check-marking the "KONTROL S49 MK3" as an input in any of my software. This happens no matter whether my keyboard is on or off when I restart my computer. Interestingly, I have no problem selecting the MIDIIN2 (KONTROL S49 MK3) and MIDIIN3 (KONTROL S49 MK3) inputs.

In my DAW, Bandlab's Cakewalk Sonar, I'm able to select all the Kontrol MIDI devices but continue to get no communication/sound. Until last week, it worked. As an experiment I installed Cubase. No problem there - the keyboard and DAW communicate.

I'd like NI to help me with what appears to be a KONTROL S49 MK3 driver issue. I'll bug the Cakewalk people about using their product with Kontrol.

DunedinDragon

That's certainly unusual behavior. Normally I don't power up my keyboard and my audio interface until I'm ready to use it and BEFORE I run my plugins or my DAW. I also don't shutdown my keyboard or my audio interface until AFTER I shut down the apps I'm using it with. That's just and old school way of making sure the configurations stay stable from session to session. The only other difference is you're on Windows 11 and I'm on 10, but I'm not sure if that makes a difference. As far as Cakewalk Sonar Platinum, I haven't tried it in this configuration because it's a very old Gibson version before it was owned by Bandlab, so I can't imagine it would representative of what happens now in Cakewalk. But in Ableton Live 11 everything works as expected as far as devices and configuration settings. Since everything seems to work appropriately in Cubase that draws my suspicions to whether the Bandlab people got things right with the newer devices under the new versions of Kontakt and KK. If I were you I'd still check the Connection Services since a new one (1.8.6) just came out earlier this week.

Jeremy_NI

https://community.native-instruments.com/discussion/comment/186973#Comment_186973

I've contacted you by email, my colleagues will need to have a deeper look into your issue.

PJ Hoffman

Thank you for your responses, DunedinDragon and Jeremy. DD, I normally turn on and load and exit my music production set-up much as you do. But I've been experimenting since this problem arose. I suspect you're right that the latest Cakewalk Sonar is not handling things well. But I still have a apparent problem with with the Kontrol driver(s) regardless, Thanks, Jeremy, for connecting me with your colleagues.

Quick links

Unanswered questions