Cubase 12 / 12.0.10 issue - losing Midi Remote

Hi,
I’m using a new buyed Novation Launchkey 37 on Windows 11 with Cubase 12 (today updated to 12.0.10).
Launchkey is conntected via USB directly to the Computer and recognized by the supported Cubase12 - Midi Remote Script.
Problem:
First recognized the Launchkey correctly then after a few minutes not using Launchkey 37, Cubase 12 is losing the connection to Launchkey, Midi Remote is greyed out and the Launchkey doesn’t work until i disconnect / reconnect it from USB. Then same procedure again.

Tried it out with Cubase 11 (always installed on the same system) and it works fine without Cubase11 losing the connection to Launchkey 37.
Therefore it seems like a bug in Cubase 12 and the new Midi-Remote-functionality :frowning:

Could this be your USB going to sleep? A long shot but a possible guess!

Thanks for your tip … but this could not be the reason …

  1. already disabled USB-Powersaving
  2. if Cubase12 looses the USB-Connection to the Launchkey37 and Cubase11 on the same system works fine, in my option this could not be the reason (btw. in Ableton11, also on the same system, there’s again no problem with loosing the USB-Connection to the Launchkey).

==> Problem only exists with Cubase12

Hi,
I’ve got exactly the same device (Novation Launchkey 37 MK3) with strange behaviour too.
I think there’s a problem with this script or the midi remote API.
See my post here :

Hi Xion,
my problem also exists in the first Cubase12-Version, yesterday I tried it again after I’ve updated to 12.0.10 and the problem was not solved in this update. Therefore I registered for this forum, posted the issue and opened an additional case for the Cubase support.

Hey guys,

Instaled the most recent version today (12.0.40)
and I have the same exact problem with my Launchkey 49 MK1 (the first model) after a few minutes I loose incontrol connection but the keyboard still works as a normal MIDI input, just cant use transport options and mixer shortcuts, I still have cubase 11 and can confirm that it works flawlessly over there.
Hopefully steinberg can explain us what are we doing wrong, or guide us somehow.

Hi [vbconceicao],
Steinberg-Support ist horrible … opened Ticket: #477142 for this case. They closed it without solution - original answer:


"Dear customer‍,

Thank you for contacting us!

Due to a high volume of incoming emails and unfortunate personnel absences, we were not able to reply all enquiries. Please excuse the inconvenience!

In case you are still in need of assistance, we kindly ask you to write us again, preferably via the support request form that you can access via your MySteinberg account in many countries: Sign in
Opening a new support request on your issue will help us work out and answer the unresolved enquiries.

Once again, we sincerely apologise for the inconvenience of the waiting time.

Best regards,

Your Steinberg Support Team"


I answered a little bit angry in Case #493993 as follow up to this case & answer … and now this case is also closed with NO answer.

In my opinion at Steinberg there’s nothing that deserves the name support.