(Windows User) MIDI Remote scripts refuse to reconnect unless CUBASE is run as administrator

Cubase
, ,
1

Sharing my findings — might help someone with the same issue

I’ve been using a custom JavaScript script for the Allen & Heath XONE:K1, mainly to control the Control Room in Cubase and transport controls. Overall, it works great — with one annoying issue.

If any controller gets disconnected while Cubase is running, the A&H controller becomes greyed out in the MIDI Remote tab and none of its controls respond anymore.

After some investigation, I found that this seems to be a permissions issue.

When I run Cubase as Administrator, the problem disappears.

So, if any of your controllers stops responding after a controller disconnects, try running Cubase as admin — that solved it for me.

I think the best way to do this, is go to the Start menu on Windows.

Search for Cubase, right click on it and choose Open File Location.

Single click on Cubase and then press Alt + Enter on your keyboard to open properties.

Go to compatibily tab and check Run this program as an administrator.

This will always run Cubase as admin. Even the shortcut on your taskbar.

I hope this helps someone having a problem with his midi controllers on windows. Enjoy.

2

I’m curious to know if other folks are running into this. There’s nothing in MIDI that should require administrator permissions, so I’d like to understand if this is something in Windows or in Cubase.

Pete
Microsoft

1 Like
3

I wanted like to understand this too. Thats why I started investigating this.

Do you run cubase on windows or mac?

4

Pretty sure, on Windows.

2 Likes
5

I’m on the Windows team at Microsoft, working on, among some other things, MIDI.

I run all my DAWs on Windows 11 pre-releases.

Pete
Microsoft

6

Btw we spoke before, and I know you’re very knowledgeable in this. Did you have this issue before? Where your midi controller is working fine and then it randomly disconnects?

7

That’s really cool, so not just cubase. But everything midi on windows right?

1 Like
8

Under Windows, I’ve noticed such issues when the usb hub power management was turned on.

Other than that, both on Win and Mac, no. I know this is a long standing issue though, for some users. The way I see it, Cubase automatically reconnects upon such failures, while MIDI Remote doesn’t do that every time. This should be a matter of how MR queries the core, or expects changes, or tries to resolve port names, in cases where these change.

1 Like
9

Yes power management thats the first thing I looked at but didn’t solve it.

Which cubase version are you on Cubase 14.0.40? or Cubase 15.0.5?

10

Both. I don’t think there’s currently a distinction to the MR mechanism between these two, though can’t be 100% sure obviously.

11

I asked because I wanted to confirm that you’re not having this issue on cubase 14.0.40 and I only tried running as admin for cubase 15.0.5. and with 14.0.40 I was having this issue. So I’m gonna try tomorrow and post the result here.

12

Sorry for the late reply, Psychlist1972 was right and doesn’t have to do with running as administrator. I don’t know what happened and solved it that day when I ran cubase as administrator and made it reconnect automatically. Now I have the same issue if I disconnect my keyboard for example the midi remote script for this controller stops working. I’ll keep investigating to see if I can solve this.

1 Like