Hi folks. I’m having some issues with my MIDI Remote devices in Cubase 15 on a Mac. The first issue is that some of the devices are constantly disconnecting. In particular, the Metagrid Pro Commands device is dropping off multiple times a day. I can get it to reconnect by reloading the script, but it doesn’t seem to last.
Secondly, I’m having problems with my Softube Console 1 mk3 Fader and Channel, where the Direct DAW control isn’t working on most of my projects, they’ll only connect if I have the Console 1 plugin inserted. What leads me to believe that it’s MIDI Remote related is that when I open the MIDI Remote manager, it shows me several instances of each device (I have one of each), and the number changes from project to project, or if I quit and reopen Cubase. I’ve tried uninstalling and reinstalling the Console 1 software, which initially shows one instance of each in the MIDI Remote Manager, but then more pop up. I’ve been in touch with Softube support, and so far they haven’t been able to figure it out.
And finally after doing the Cubase 15 update, all of my custom mappings for my controllers are gone. I’ve also seen that elsewhere on the forum with others having the same problem.
This has been bothering me since versions 13 and 14.
Here’s what I’ve found out so far.
Cubase sometimes deletes assignments when saving a project.
It also seems to have an effect when you open a ‘corrupt’ project and then close it again. This makes it totally unpredictable, of course.
What you can try is to save a working mapping as a backup and restore it when needed.
The assignments are stored in the User Settings folder as globalmappings.
My screenshot shows my M-Audio file with 10KB, which still contains the mappings.
The Korg file is only 1KB and the assignments were deleted again when Cubase was closed.
There was tremendous support/engagement from a Steinberg developer called Jochen Trappe in the very early days of MIDI Remote… Not sure if he’s still attached to the project… And I’m not sure why but after a year or so he just stopped participating in the user/dev dialogue all together - which was a big shame.
I also experiencing same issue with metagrid + cubase 15 pro, and some of my custom mapping setting. Looking forward for the solution. Thanks in advance
Softube Faders MkIII has just stopped working with C15 Pro on Mac. I’m not sure what changed, but I’m on latest of everything. It’s detected, but unless I use the VST3 it doesn’t work properly – it’s as if Direct DAW control has just stopped working entirely, one of the reasons I originally purchased it. Anyone else run into this?
Yeah, I’ve been having the same thing with the Fader and Channel both, although in my case, I think it started a couple of weeks before the C15 update. And oddly enough, it varies depending on the Cubase project. Anything made from my master template file (the big kitchen sink one) seems to have trouble, but others work totally fine. I’ve been in contact with Softube to try and figure it out, but no luck yet.
I’ve been having other issues unrelated to the MIDI Remote (macros, preferences, that sort of thing) I think might be some corrupted preference files, and so I wouldn’t be surprised if my Softube issues are related to that.
Not much help to offer, unfortunately, but you’re not alone with that problem.
MIDI Remote has been incredibly frustrating for me. Is there a document that lists exactly what files need to be deleted to get all vestiges of a MIDI remote off my system? My streamdeck works intermittently. I’ve removed the surface, deleted the scripts, whatever else I could find Documents (on my Mac), exited Cubase, reboot.
When I import the script, it immediately finds the device and the OLD MIDI port names, not the correct ones in the IAC driver. This seems to indicate that Cubase is caching MIDI remote information somewhere that’s been corrupted. This seems to be an issue only with user scripts for me, not public ones, although my NI S88mk3 has intermittent connection issues itself, but I believe that’s an NI issue.
Cubase generally stores all MIDI Remote related user data in the folder %USERPROFILE%\Documents\Steinberg\Cubase\MIDI Remoteon PC or ~/Documents/Steinberg/Cubase/MIDI Remote/ on Mac. If you rename this folder, Cubase will recreate it with the factory settings at the next start.
However, since this folder also contains factory scripts that still might interfere with your setup, you’ll have to rename their source folder too, which is %ProgramFiles%\Steinberg\Cubase [Version]\midiremote_factory_scripts on PC or /Applications/Cubase [Version]/Cubase [Version].app/Contents/MIDI Remote Factory Scripts/ on Mac.
With these two measures, you completely remove MIDI Remote from Cubase; it will also no longer be displayed as a tab in the lower zone. Note however, that the folders are restored with every Cubase update, i.e. MIDI Remote will “resurrect”.
