Controller Scripts duplications - Why?

Hello there

After loading an empty project this is what I see in the MIDI Remote section:

Of course, I do not have 3 Akais and 3 NI Kontrols, these inactive units show up as duplications.

Why are they there, and how can I banish them?

Cubase Artis 14.0.40, Mac OS 15.6.1.

THX.

1 Like

I don’t know why they appear, but if you click on that down-arrow and “Disable Controller Script” for each affected controller-type then re-enable them again in the Midi Remote Manager, the duplicates should disappear.

Nice but they will come back upon the next launch of Cubase.

Yes, this is the problem.

Same Problem on my installation .. contacted the supprot but since a week no reaction

It’s not that simple. I was able to restart Cubase multiple times without seeing the issue. After a bunch of opening, closing, creating, and saving projects–I broke my MIDI remotes config again, but I made some helpful observations:

  • If you save a project or template while there are duplicate MIDI remotes, they will be there next time the project is opened.

  • If you manually resolve the duplicates in a project and then save it, it will be OK the next time that project is opened.

  • If you open a project with no duplicates, then open and activate another project in the background, the MIDI remote config from that project–good, or bad–will become the global MIDI remote configuration.

  • If you create an empty project (using the empty template) there should be no MIDI remote duplicates.

  • SideshowFX controller not affected–no duplicates. It uses Mackie Control.

I read through the API documentation and first tried to resolve the issue by deleting the “DetectionUnits” entry for my user-created MIDI remote–but it was reinserted.

image

Since that didn’t work, I replaced the empty “Name” fields in “DeviceMidiInput” and “DeviceMidiOutput” with the exact port names for the MIDI device my controller is attached to, and tested again.

I don’t think that helped either, since I still got duplicates when opening existing projects and when creating new projects using my user-created templates.

Here’s how I resolved the issue on my system:

  1. Open Cubase and created a new project using the empty template
  2. Confirm that there were no MIDI remote duplicates
  3. Save the project as “dummy.cpr”
  4. Close Cubase
  5. Open “dummy.cpr”
  6. With “dummy.cpr” open and active–to fix any affected templates–go to New Project and create a new project using a template that’s broken–but DO NOT activate the project when prompted with *Do you want to activate the project?*Choose “No”
  7. Go to the inactive project (make it in focus) and go to File→Save As Template
  8. Overwrite the existing template, or create a new one and delete the old one after confirming that the new one is fixed
  9. To update existing projects do basically the same steps. Keep “dummy.cpr” open and active, open a project but don’t activate it, and use File->Save As. You can just choose the existing project name and overwrite it
  10. Close and re-open Cubase. Confirm that your projects and templates don’t have duplicate MIDI remotes

It’s likely that the steps could be simplified. Steps 1 - 5 could probably be replaced with just opening an empty project from the template.

The auto-detection behavior in projects, when working with ports used by MIDI remotes, seems to be the root cause. I’m not sure it can be fixed permanently without some changes from Steinberg.

2 Likes

Wow, that was some extensive search and a solution that seems to be working at my end as well. Thank you.

1 Like