Hello I’m getting silence on Native Instruments help Forum. I hope someone can help here?
I have recently purchased the above secondhand and have transferrd the licence arranged with the original owner. Everything works fine and have followed all the setup instructions. But it is hit and miss if I can navigate my DAW using the midi controls to move around cubase. If I restart windows maybe several times it will work.
Please can you suggest a solution as annoying to keep restarting windows. Already reinstalled Komplete software but still getting same issue. (all the settings are correct)
Not sure if this will help but in my experience these simple uninstall - reinstall procedures work in 90% of cases. If it does not (or you are that original poster and this was your question) that will at least remove the biggest possibility and help narrow the solution.
No - please ignore the above as I have now opened another project which shows the first midi remote picture with the created midi mappings but I can still navigate. But would be helpful if someone much more knowledgeable than me if anyone has had this issue before. If the issue reoccur’s I’ll let you know. (does it makes any difference if midi remote shows any mappings if you are trying to navigate Cubase with Komplete Kontrol Keyboard?))
Based upon the screenshots you posted I see you do have the Keyboard (S88) and a Machine.
The Keyboard (S88) transports should work because it is recognized and installed in Cubase as ‘Remote Device (Legacy)’.
Why is there a MIDI Remote entry (for that Machine?).
I suggest to first delete the MIDI remote device and see if the S88 behaves as expected.
same thing - a reboot fixes it for a while. Then after closing Cubase and Opening same circle where remote midi to control Cubase breaks again. Its driving me nuts. So don’t know if it is something to do with Cubase or NI. Probably NI.
I had a similar issue with my recently acquired S88 mkII. I did the reinstall thing a couple times, making sure to use device manager >View Devices by Connection and deleted all NI entries before reinstalling (not sure if that is needed or not). I still had issues, but so far, if I make sure to always start the keyboard before starting Cubase, it has not had any issues. Fingers are still crossed…
For me, if Cubase does not see my gear, it seems to “forget about it” to some degree, so I take steps to always start my studio gear before Cubase. I built a small batch file that I use to launch Cubase, that prompts me to turn everything on and then hit a key before it will launch Cubase.
Hello LarstradamusH - thanks for your helpful reply.
Yes you are right it does make a difference to start the keyboard first for better reliability. Unfortunately when you turn the keyboard off (because you want to take a break and save power) then turn back on you lose connection again to use keyboard to control Cubase.
I would be very interested to learn about your batch file as there may me some things I’m still not checking correctly. Yes I can see the drivers are always live but even when this happens the drivers are still open in the back ground and have not disconnected.
But why is this happening. If I reboot my computer with keyboard on, sometimes all the correct lights on the keyboard show and sometimes they don’t which will mean I won’t be able to use correctly on Cubase. On all occasions drivers are open in the background.
Here is the batch file (text file with a .bat file extension) I use (Windows 10). It simply prompts me with a text message and pauses until I press a key. Then it launches Cubase. I replaced my Cubase shortcut with this because I kept forgetting to turn things on first.
echo Put your message here
cd "C:\Program Files\Steinberg\Cubase 12"