Midi Remote control stops working when i plug in another midi device

[exoslime]

Hi

i have some weird behaviours with my midi remote controls…
Cubase Pro 12.0.70

The Remote Control works fine, until i plugin or enable a new midi device, that was not present at the start of cubase, it will make all my midi remote control units without function until i restart cubase.

example:
i start cubase and i have 2 midi devices powered on and running:

1. Behringer X-Touch Mini
2. Midi Fighter Twister

everything works fine, for hours.

BUT, if i turn on / plug-in another midi device , or a device that also has a midi2usb ports, (no matter if its a keyboard, the NI Maschine Mikro, or the FAS Axe FXII) suddenly the remote controls stop working, the GUIs are still in the remote control view and show as connected, but cubase does not react to the controls anymore.
When i restart cubase, all works fine again including the new turned on devices.

I dont think that was the case in previous cubase 12 pro builds, because usually when i´m recording a song, sometimes in between i turn on my Axe FX II to record some guitars, and once finished, i turn the axe fx off again. the remote control units always did work no matter how often i turned on/off some devices in between. but now it doesnt anymore.

As soon as i have a cubase project running and i want to record some guitar takes, and i power on ie, my Axe FXII, the remote controls are loosing their functionality. so i need to close and restart cubase entirely to make it work again, which is a bit annoying
it also happens when i turn off a midi device.

i did already lots of testing, it does not depend of which devices or in which order they are started, it happens to all of them, in all orders

any ideas what could that be?

kind regards
exo

[av_music]

I am pretty sure it happened with earlier Cubase 22 versions too

I think it’s a “known issue”

For me doesn’t happen with all the devices ,for example I have 2 native instruments Kontrols [different models], if I disconnect a device [iCon controller, or Novation] one of the 2 Kontrols stops working, the other one works. No other device is affected [and I have many usb…]

I think it also due to the USB port, so that’s probably due to Windows [10 for me] and Cubase together

Would be curious to know if this happens to Mac users too

[exoslime]

thank you very much for your reply,
i´m currently right in between a project, so i´m not very keen to downgrade to a previous version and test if the issue is existend there as well, but i might do this once i have finished that project

yeah, i can confirm, i noticed it that sometimes only one of my 2 controllers stop working, sometimes the behringer, sometimes the midifighter, and somethings both. i did already try different usb ports, etc.
also i noticed that sometimes the controllers still get midi signals from cubase, because their led indicators are still following what is happening in cubase, but cubase does not get any midi data back when i turn knobs or pushing buttons on the controllers.

i´m also on Win10

[Gunnar_Schuettler]

I have the same Issue here. Good to know that I am not the only one. When I plug in a new USB-Midi Device my USB-Cubase-Remotes stop workin. Sometimes my Maschine3 was not responding from the Cubase-start so I had to restart it in a running session which caused the Remotes not to work anymore. In a working environment its horrible for creativity.
I have Maschine3, Minilab3 and X-Touch (Mini and XTouch as Cubase Remotes via USB). Interesting is that the X-Touch still received Data from Cubase after I plugged in a new Device (Maschine3 restart), so the Faders were moving when I changed Volumes via Mouse.
As I mosty need the X-Touch controls I tried to run it over “Lan-Midi” instead of USB and that fixed the problem for the X-Touch as a Remote. Some Faders take some time to find values but thats better then not working.
Did anyone allready send a support request regardning this Topic? I guess I switch all my controllers to Midi now, just to not have the struggle with USB.

[exoslime]

@Gunnar_Schuettler

Did anyone allready send a support request regardning this Topic?

just to let you know, i did not supply a support request

sorry to hear you are having the same issue, , yes, i totally agree, its horrible for creativity.
for example, i´m in the middle of working on a song, think about recording some additional guitar overdubs, turn on my axe fx, and voila, all midi remots stop working because the axe fx also has an inbuilt midi device via its USB ( i cannot unplug the usb connection because i need to use the editor software at the same time)

the workaround via Lan-Midi sounds interesting, would you be so kind and share more details about how you do that?

i also noticed that my behringer x-touch midi still recieves midi data from cubase after this happens, thats same here as well.

[Gunnar_Schuettler]

So I would put a support request in place when I have the time regarding this topic. Will let you know what the support has to offer.

So you can use the X-Touch as a Lan-Midi Controller. The Protocol is called rtp-Midi. There are some tutorials on youtube how to setup this. But you maybe need a Ethernet-Switch so that you can root more ethernet connections into your PC / Mac if you want to use internet and the x-touch per cable at the same time.

For me it runs ok. Sometimes the X-Touch-Controller is not responding perfectly but better than just not working. I have to say, that all USB-Remotes still loose connnection when adding another USB-Midi-Device. I will check the issue with Cubase-Remotes via Midi, maybe its easier to just get a large Midi-interface. I also like the idea to switch Synths on/off to safe electricity.

So let me know, if it worked for you with the X-Touch

[Gunnar_Schuettler]

Ok, i checked if midi works better than usb when turning on and of a usbmidi- device. As expected a cubaseremote connected with midi doesnt have a big issue disconnecting and will work after turning on and of a usbdevice.
The Lan option of the xtouch works ok. I am using a control script from @bjoluc to have coloured displays. Some controls are a bit laggy but it works.
Hope that helped

[fotmos]

Hallo everyone!
I have the exactly the same problem as exoslime descibed.
I noticed that everty time I connect a new USB midi device, the midi remote (an lower zone) is blinking. It is like its restarts its engine and unfortunatelly never works again. I have to reboot Cubase in order to start working…
I also see that this problem is known from Cubase 12.
Is there an official ansuer about that?
Or did anyone have already find a solution?

[fotmos]

Hi again!
I just discover something interesting!
When I open cubase having all my midi remote controllers already connected, in the midi port setup window I see this:

BUT,
If I connect a new midi device or disconnect a midi device, the midi port setup window change to this:

It seems that every midi port change making all the midi inputs getting lost!!

[exoslime]

@fotmos

It seems that every midi port change making all the midi inputs getting lost!!

thats a good observation!

i ddint find a solution yet to this case, its very annyoing indeed, i cannot plug & play my various usb midi controllers and input devises on the go, i always have to close cubase and restart and opening my projects so that remote control keeps working

[exoslime]

@Gunnar_Schuettler

So I would put a support request in place when I have the time regarding this topic. Will let you know what the support has to offer.

Hi Gunnar

did you get a response from support on this topic?
if yes, what did they say?

happy easter
cheers
Chris

[exoslime]

i have added a support ticket on this topic on 29.03.2024, but no feedback from support sofar… is this typical for steinberg support these days to not answer requests timely?

[raino]

@exoslime

When i restart cubase, all works fine again including the new turned on devices.

Try just closing and reopening the Project rather than restarting Cubase. This fixes it for me.

[exoslime]

Hi @raino
thanks for your reply, i have tried that with multiple projects, on cubase 12.0.7 as well as cubase 13.0.3, but i still have to completely close and reopen cubase to make them work again, just simple close the project and reopen the project doesnt fix it

[m.c]

@exoslime

just simple close the project and reopen the project doesnt fix it

Have you tried disabling and re-enabling your midi remotes?

You can do this in Studio→MIDI Remote Manager→Scripts Tab→Select your remote file→Click on Disable Controller Script and then again Enable Controller Script.

As a side note, WinRT MIDI is superior when it comes to auto re-connecting, though it has some other issues, but you can always give it a try.

Another thing that’s worth mentioning (Win OS), you have to make sure (by going to Device Manager) that the usb root hub power management is not enabled.

[exoslime]

thanks for your reply and very detailed help @m.c

@m.c

Have you tried disabling and re-enabling your midi remotes?

yes, i tried that many times too, but that did not have an effect

i can unplug the not working rendeered midi remote control device and plug it in again, then it will work again, but then the other devices will not anymore as remote controller anymore.

i also have my usb hubs/controller power management disabled

i havnt looked into WinRT Midi yet, but i will, thanks for the suggestion

[exoslime]

@m.c

As a side note, WinRT MIDI is superior when it comes to auto re-connecting, though it has some other issues, but you can always give it a try.

i cannot believe, i think using WinRT Midi did the trick

i have enabled Win T Midi, then i had the redo all my remote control setups and now suddenly, i can add or remove midi controllers as much as i want, and the remote controls all stays fully functional!! that is AWESOME

thank so you much @m.c for this little “sidenote”, i would have never thought about to try WinRT Midi

[raino]

@m.c

WinRT MIDI is superior when it comes to auto re-connecting, though it has some other issues, but you can always give it a try.

Well I tried enabling WinRT MIDI and that took me down a weird rabbit hole. Initially it seemed like playing the keyboard wasn’t triggering the VSTi, but MIDI Monitor showed it was receiving what I was playing. Then I tried playing a previously recorded MIDI Part - no sound. Next I noticed that a regular Audio Track wasn’t producing sound at all. Tried restarting Cubase, the PC, with WinRT MIDI on & off in various combinations. Whenever WinRT was on Cubase’s Audio was hosed, turn it off and the Audio works.

It’s all fine now but I’m puzzled why a MIDI setting would impact the Audio at all?

And then…

Making all those changes above had left a bunch of MIDI Missing Ports messages. Most were easy enough to remap just from their names. However 3 of them had very peculiar names, as you can see in this screenshot. The names kind of looked like entries in the Windows Registry so I tried doing a search there & bingo. That helped sort out what they actually were.

[exoslime]

i also had some weird things with WinRT on the 2nd days of using it.

i´m using 3 devices as remote controls, everythings powerd up, started fine, looks good, but suddenly Cubase did not recieve Midi Data from Device 2, the controller itself recieved the Data from Cubase, i saw the LED colors changing and reflecting the values from cubase, but controller changes from the controller was not sent back to the DAW, so i removed it, and set it up again, made sure the Midi In and Out were matched correctly, but still the same behaviour, the controller was able to receive midi data, but cubase did not pick up the midi sends from the controller, weird.
so i closed cubase and restarted and then suddenly it was all working again.

[thomas_martin]

This is a common behavior on my side.
My controller randomly disconnects this way.
I’m not using WinRT.

Thomas