How do I make Cubase forget an instance of a MIDI Remote device ever existed?

Cubase
1

I have a MIDI surface device. It can be plugged into the USB port or into a standard MIDI jack. I plugged it into the MIDI input jack of my UR44C and make a MIDI Remote device mapping for it (just trying it out really). I prefer to use the device in the USB port.

So, I have 2 “instances” of this MIDI Remote device in the MIDI Remote manager. One of them is using the “USB Port” and the other is using the “Steinberg UR44C MIDI In” port.

The main problem is that when I start up the project, Cubase always sees the “Steinberg UR44C MIDI In” port (of course, even if I don’t have the device plugged into it, because my audio interface is on), and activates that “instance” of the MIDI Remote device. If I have it plugged into a USB port, Cubase also creates that “instance” but it is “not connected”. So I have to remove that instance that is connected to the UR44C MIDI port (even though it is not actually connected) then, I have to actually remove the instance connected to the USB port and add it back in. It won’t even let me just “activate” or “connect” the USB instance.

Somewhere, Cubase has written that the MIDI Remote device is associated with the Steinberg UR44C MIDI In port and I need to remove that. I don’t want to trash all my preferences though. I did notice that the script is marked as a “Global” mapping, which means it should be available for all projects so Cubase must store that information somewhere.

Does anyone know where I can remove this so Cubase forgets that the MIDI Remote device was ever associated with my UR44C?

Sincerely,

JL

Edited…..

Well, I figured out that in the script, if I add the…

deviceDriver.makeDetectionUnit().detectPortPair(midiInput, midiOutput)
.expectInputNameEquals(‘USBport IN’)
.expectOutputNameEquals(‘USBport OUT’)

It will automatically load and activate the USB instance of the device. But, it still usually adds the instance that is connected to the UR44C midi port and shows it disconnected.

I plan to just rename the device and script (it is not finished yet) and then just completely trash the old “version” but it is still bothering me that I can’t get Cubase to “forget” it.

2 Likes
2

I think I figured this out. When you create an “instance” of a midi remote, using a specific midi port configuration, Cubase saves a .json file in the

C:\Users\\Documents\Steinberg\Cubase\MIDI Remote\User Settings\ folder.

I believe it only does this when the midi remote is “global” and not a “project” specific midi remote instance.

If you delete the .json file referring to the midi remote it seems to clear Cubase’s memory of the previously used instances of that midi remote. It doesn’t delete the script or, if you created a remote using the layout editor and mapping assistant. Those files are saved in…

C:\Users\\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\

I hope this helps someone…

JL