This is a known issue, generally of the MIDI Remote.
Out of curiosity, could you please post here what ports do these remotes use?
If you open Studio→MIDI Remote Manager, and then clicking to each of these remotes, you can see in the low section of the window the MIDI ports occupied. I’m asking so that I can make some suggestions.
Hi, thank you for this script. I’m not super adept at this stuff as I’m just learning. However, I employed the full script and installed and connected the Keylab MkII (apparently called a MIDI Controller Surface). I was able to raise and lower audio levels/control panning on the MixConsole and Transport Controls were working from the Keylab. Didn’t get too much farther than that yet. I opened Cubase 14 back up today and the MIDI Controller Surface was not connected, so I had to re-add it. After I added it and got it working, I saved everything and shut down. I re-opened Cubase and it was gone again. How do I get it to save to Cubase and not discard it everytime I shut down?
Hi, this sounds like a port name changed in the middle, either due to a win update (are you on win?) or a physical usb port change. Could you please post a screenshot of Studio→Studio Setup→MIDI Port Setup window so that I can have a look?
But… Where are the ports of the Keylab?
OK, here’s what you can try. Go this post and download the installation file (midiRemote) from there:
Basically in your case, after the installation, just grab the file customMIDIPorts.js from the folder MyPersonalSettings and move it one level up, i.e. at the core folder of the script.
Restart Cubase and the remote should now be automatically detected. There is still a chance that this fails, since there’s a known issue with loopMIDI ports in Win11 after its latest updates. See more here (if needed): Loop Midi hidden in Windows 11 25H2 fix
Thank you! I’ll give this a shot and let you know how it goes.
Chris
Just to be clear, did you download the file I suggested, and the customMIDIPorts.js is missing?
EDIT: I see the midiRemote file in your folder. Didn’t you install it instead of putting it there?
Yes, I downloaded the updated version of the file and imported it in the MIDI Remote Manager. I placed it in that particular folder for the moment so I wouldn’t forget and delete it from my downloads folder as I occasionally go through it and throw away files.
OK, but I’m puzzled since I see that the date signature of the files in your folder are older.
Looks like most are from the 25th, which I think is about right. The midiremote file is today though.
That’s what I’m talking about. I would expect your files to be signed today since the midiremote file was installed today. Could you please make one more try to install the script?
Sure will. When I install, it overwrites the old one. Would that by any chance affect it?
Yes, it would affect the setting for the StrippedDown mode. You should set it again to 0. Nevertheless, it’s always a good idea to keep a backup of the whole folder.
Looks like the dates in the folder did not update. I imported the script and added the new MIDI surface and activated it. No change. There is something I am not doing correctly but I can’t figure out where.
Did you find the customMIDIPorts.js file?
I ran a search for it inside the Steinberg folder (thus all the subfolders) and nothing came up. Maybe I should search under the Program Files app folders.
hI Many thanks for creating this script, It looks very comprehensive, I am only using in basic mode, easy to install.