I have two MIDI controllers. They both appear multiple times in the lower zone, the duplicates kinda “greyed out/empty”. I can clean up with “Remove controller surface”, but the “ghost controllers” appear again.
In the Mapping Assistant there are correctly just two controllers visible.
Anyone ideas why?
As far as I know:
Windows creates a new device every time the USB cable is plugged in. This can cause problems. It’s better to always use the same USB port for a device and have it enabled at system startup (that’s how it was for me).
You can remove the unnecessary “devices” in Windows Device Manager. They should then also disappear in Cubase.
Thanks for your reply! Strangely the controllers are always on the same (direct, no hub) USB port on my PC and there are no duplicated devices in the device manager.
Hmm ok …
So it´s different to my problem …
To see the ghost versions, in Device Manager, go up to the top menu and choose View → Show Hidden Devices.
This happens because some USB devices do not have unique serial numbers. However, if you’re always leaving them plugged in and powered on, and don’t have multiples of each, this shouldn’t happen.
Pete
Microsoft
Hmm, I don’t see any ghost devices with this expanded view. My “Novation Launch Control" XL” and “AKAI LPD8” just appear one time.
Even more strangely I just opened an empty Cubase project and there are no MIDI controllers in the lower zone. Either my Win11 system has troubles managing MIDI devices (but Device Manager looks fine) or Cubase 15 Pro has.
It’s a bit complicated. 
It’s down to Steinberg, not Microsoft, and is a bug that has become more prevalent since Cubase 14.0.40.
In short, the problem is that MIDI Remote settings are also saved within projects.
When you open old projects, this can lead to issues such as duplicate entries or the MIDI Remote controllers not being recognised.
Often, the controller assignments in the global mapping file are reset.
Since Cubase 15.0.10, at least the assignments are no longer reset. However, problems such as duplicates can still occur when opening an old project.
I think the problem lies in the fact that the old project still contains code from the bug, causing the otherwise functioning MIDI Remote to crash.
You can find the full story with suggested solutions here.
It’s worth reading through the whole thing.
