You can share the code with me, and I’ll try to fix it.
Judging from my script it would be straight forward to have it automatically connected, unless of course you’re changing midi ports from time to time.
That would be amazing if you could help me out with it. I would appreciate it so much. Beer on me!!!
I am attached the whole MIDI Remote package that came with my controller.
Please let me know what you think.
Thank you so much again!!!
Local.zip (12.8 KB)
Just checked the folder, there’s no detection unit anywhere. This means that we have to insert it, in order for the script to automatically detect our ports.
Can you please provide the name of the MIDI In and Out ports that you use for this script? A screenshot would be of help too.
EDIT: Just saw a previous post of yours where it seems that your ports are “loopMIDI Port 1” and “loopMIDI Port 2”. So, if this is correct, here’s what you can do:
-
Close Cubase.
-
Open the file mp-midi_mp-controller.js and then right under the line “const outputPort = driver.mPorts.makeMidiOutput();” place the following:
var detectionUnit=driver.makeDetectionUnit()
detectionUnit.detectPortPair(inputPort,outputPort)
.expectInputNameEquals("loopMIDI Port 1")
.expectOutputNameEquals("loopMIDI Port 2")
This file should now look like this:
- Save it, and start Cubase. If everything went OK, you should now see the MIDI Remote surface active.
Hi everybody,
I have the same issue than many of you.
When re opening cubade, the xtouch/midi remote controlers disappeared…but :
At home, windows 10/cubase 14.0.10, if I completely QUIT cubase, the issue is here and when reopen cubase, I have to setup newly my midi remote…
If I only CLOSE cubase project and cubase let the selection projects windows opened. When I select a project in the list, at opening, all devices on midi remote are properly recalled .!!!
There is something that cubase dump some temp files ( I could imagine ) related to midi remote when completely closed, but cubase keep some temp files if you just shut down “project” .
Hope Steinberg could listen it quick, in fact when you close computer for upgrade or any other case. Cubase lost midi remote controlers set up before!
Kind regards from France.
2 Likes
Try using an old version of Cubase like 12 to create the script and to use when you need to use the control surface. Also, try to log in to the Cubase Index forum with Greg Ondo and express the issue with him so it could possibly move up the chain and get to the employees that could help. Hope this helps
Only one of my 6 surfaces load with my project in Nuendo 13. Any fix to this issue on the horizon?
Cubase 14 still not keep in memory old remote script ( xtouch with bjoluc script )…the new upgrade is still messing… does anyone has a solution from steinberg ? cubase 13 recall correctly the devices but not cubase 14… what did they changed ? at each restart of cubase 14, I have to resetup the devices in remote tab…unfair !
Hi m.c
After upgrading from 12 to 14, can you please point me in the right direction for editing your custom script so it loads up with the midi remote every time when loading Cubase etc. It seems that Cubase support aren’t very helpful to everyone having this issue of having to set up the custom midi remote every time etc.
Having just read the posts above, I can’t seem to locate the file above: mp-midi_mp-controller.js in order to edit it and add in the extra lines of script shown above. Is it called another name?
Everyone with this script issue will have different parameters, because using different hardware devices. So look for the js files within your setup.
I had this issue with my Arturia MiniLab and made a post about which got lots of people talking. I finally resolved it, people shared tricks worth having a look at, good luck !
1 Like
Hi, please tag the user name with a @ in order for the user to see the message. I accidentally saw it now.
Post in the dedicated thread Arturia Keylab MK2 Custom Midi Remote Script ( MKII )
your Studio→Studio Setup→MIDI Port Setup screenshot.
1 Like