I was wondering why my Remote-Touch-OSC did not work and noticed (again) that Cubse is tripling my MIDI-Devices for whatever reason.
I have to delete them in the Midi-Remote-Manager everytime but it happens frequently. Is this a bug ?
Interestingly, when I deactivate the SCRIPT and re-activate it, th edevices show up 3 times again on different MIDI-ports.
I’ll attach my Script
Hexler_TouchOSC.midiremote (17.7 KB)
Version: Cubase 13.0.50 and previous
Hi, I think this means that you had the issue before updating to 0.50, right?
How many files name like Hexler_TouchOSC with an ending _globalmappings.json do you see in the folder [your documents folder]\Steinberg\Cubase\MIDI Remote\User Settings ?
Same problem here but "only " doubles.
I tried deactivate/activate the script and the doubles where gone but only until restart of Cubase.
The issue still exists in 14.0.5
By the way, is there any way to rename the Model and Vendor Name?
Not a big deal, but I misspelled mine and can’t find a way to change it.
Edit: Perhaps using different usb ports triggers this? I might having both on different ports before.
@basicnoise
I think you could edit the .json file.
Then change the name there.
I am not on the PC right now soI am not sure if you look up the original file or if you have to export the script first. One of those files is encrypted, the other one editable.
@m.c
I can see that multiple instances are in that one JSON file.
I am not yet familiar withthe formatting though, else I would have edited it myself already and removed the trippled instances
Nope, port doesnt matter. I keep my Launchkey 49 plugged into the same port on my hub and just use the button next to the port to turn it on and off when I need to use it. Almost every time I open a project, I have a brand new instance of my Launchkey, next to the old disconnected one. Funny thing is, most of the time the lights dont light up on it either (although it does work). I have to delete all of them and re-add the Launchkey as a brand new controller and it works until I close Cubase and start over again.
Note sure I understand. JSON files should hold a) surface elements, when in the local folder and b) mapping elements when in the user settings one.
I am. Can you post the file you’re talking about?
I agree unfortunately. I’ve seen this behaviour in one of my recent script, where there were no other ports even temporarily involved. However, the duplication was happening only upon refreshing the scripts.
This is an interesting finding. Could you please point me to the script used?
Its the Launchkey 49 script that comes with Cubase. For the longest time it used to show my 25 inactive still too, but I finally got that to stop showing up once and for all.
Yeah, I’ve just had a look at this script. When it’s the time to send a color change, it checks some values which are supposed to have arrived previously. Interesting… I have to guess this has to do with the frequency of checks by the API. By the way, are you on Win or Mac?
Im on a Mac here, latest version of MacOS and Cubase and all that fun stuff hehe.
Go figure, last night I worked on a project that had the issue over the weekend, and it fired up just fine with only one instance of the MIDI Remote and all the pads were lit up as they should be. I really wish I could figure out what exactly triggers it! Now I’ll likely work on it over the holiday tomorrow and it will probably pop up again haha.
Hexler_TouchOSC.zip (9.0 KB)
find the file attached
This looks corrupted to me. It contains 3 DeviceDetectionUnits, while only the one is “tree”-id correctly. The other two are broken. Did you try manually altering the DeviceDetectionUnit or this has happened unexpectedly at some point?
Still, it loads correctly here, i.e. just one instance…
I was reconfiguring my MIDI ports - I guess it happened there.
So can it be “cleaned up” ? 
Go figure worked on the same project multiple times throughout the day yesterday, only had one instance this time every time I opened it. Maybe it was off for the holiday haha.
Can you post here the exact names of the MIDI In and Out ports you use? I could give it a try.
Perhaps you’ve been working on a fairly recent project, and the issue gets in when working with older ones?
i will use this new one here. I have to run TouchOSC through the BOME MIDI TRANSLATOR software. IN and OUT have the same naming “Bome MIDI Translator 2”
OK, here’s a file to test. Backup first your current json file, close Cubase and then replace it with this one, after decompressing it obviously:
Hexler_TouchOSC.zip (10.1 KB)
Here it works as expected, but you never know…
@m.c Dear anonymous new-year fairy.
You absoluteley solved it and I can now work again - what a great start in this new year. You were so much faster than the guys at Steinberg. I will drop them a link to this thread in my ticket.
I owe you big time - if I can make it up somehow, please let me know - just ask.
Big anonymous hugs.
For everyone who passes bye, I have to mention the trick on how to get the JSON Script in Cubase, since there is no way to import. (only encrypted .midiremote files).
So, first I looked up all my old “TouchOSC”-files I could find (using UltraSearch) and deleted/back-up them.
Then I created a new MIDI Remote set in Cubase, using the same vendor name and device name as described in the .JSON file.
After creating this “dummy”, cubase now saves a new .JSON file.
I closed cCubase and overwrote the .JSON file with your repaired one.
I now got all my button-layout back.
The only drawback is that the assigned functions are empty but they are most likely written in the other encrypted files of CUBASE.
Anyway, re-assigning takes 30 minutes and I am done.
Glad that it worked out for you!
