cubase will now lose at least one of my midi controler setups at the start of a fresh project… not allways but at least 80% of the time, ?
sometimes the Port list is empty and i have to switch off the device and restart it so cubase can then populate the device list again, or the device is there and looks to be routed but no response untill i click on the dece name and delete it and then reconect it… bingo it is back
just another frustrating thing…
this has no relevance to the update because it has been a problem for years in my totally unqualified opinion could it be that cubase does not accept the “handshake” or something like that ?
Cheers
T
Hi There Martin , hope you are well
yes sorry , windows 11
and yes its midi remote.
this is not a new problem i have had it for years, several cubase versions, and several different midi (+mmc) controllers.
actual setup Yamaha Dm2000+ icon-Q.con pro G2.
i cant remeber for certain but as long ago as “SX” i read somwhere that we have to start the controller first then cubase.. if this is still the same then its my bad for forgetting but i am thinking if so why has this not been addressed.. so … it must be me .. i must be doing something wrong every setup .. same old mistake kind of thing .. what do you think ?
kind regards
T
This is still very very broken…
Can we get this fixed soon - I have to reprogram my midi remotes every time I open the program…
I also get a bunch of ghosted remotes that I have to delete but then they just keep coming back.
This is now a four year-old problem…
Are you on Mac or Windows? How did you create the MIDI Remote device (the built-in Manager or Scripting)? How is the MIDI Port defined (especially if it’s a script)? What kind of hardware device is it? Does it provide only 1 MIDI Port or multiple? Is it real MIDI Port or a virtual one?
Hi Martin - ok - I finally did enough research to see that program also saves Midi Remote data in the project as well.
So I removed the script (X-Touch plus 2 extenders), and saved that project and quit the program.
Opened same project again and all ghosts are gone.
Set up the remote again.
Now (on this project only) the remote comes up as expected, with no ghosts.
So I think I am suffering from a legacy project that has previous iterations of the remote…
I will research further, but it would be extremely useful to be able to change those ports once the media remote has been added, which seems to be not available currently.
Ok - I spoke too soon - ghosts are back and blocking the actual one I want…
Once again, I remove all iterations, then deactivate script, save project and restart cubase - this time open a new empty project.
Save as test and restart CB and open project.
No ghost issues anymore.
So maybe no way to fix existing projects?
So I did the same thing and saved as a new project and it seems to have cleared the problem.
Sheesh!
Ok - I will see if it reproduces - going to do the same to my templates…
So - seems like a legacy project problem…
i noticed the same, on new projects it works fine, but as soon as i open up an older project previous cubase versions, things can get weird, not only i get the ghost controllers, but also sometimes it wrecks my exisiting controlls to an unusable state with all global mappings lost (project mappings however are still working), but at this point, the damage is alreay done, as soon as i quit cubase the remote controller files get replaced with the wrong unusable ones → to solve this, i made backups of the good controller files with their mappings, i copy them into the controller directory and at the next start of cubase, the controllers are back in working condition with all their global mappings, its annoying but way less annoying if i would need to remamp all of my controllers all over again
I also noticed that loading more than one project screws everything up!
Pity, as I use that to shorten load times…
So - still problems with how this is handled.
A couple of older projects that I had fixed a few saves ago, broke again.
Perhaps the devs could check what happens when more than one project is loaded?
The problem is that Cubase also saves the MIDI remote assignments within the project. If you open an old project containing greyed-out duplicates, it overwrites a working project. If you delete the greyed-out duplicates, as is often suggested here in the forum, you end up deleting the MIDI ports in the JSON file.
I already wrote to German support about this back in April, including screenshots and JSON files. However, this information does not appear to have been passed on to the programmers.
Here are two workarounds that might work. However, they are just workarounds.
Workaround 1:
Make a backup of the working MIDI Remote and use the backup if Cubase corrupts the assignments or the script. This will always happen when a corrupted project is loaded or when you delete the greyed-out duplicates.
This behaviour in old projects has not been resolved, not even in the new versions, because Steinberg does not understand this bug, even though it could be fixed. This bug has existed for years and has been confirmed by a great many users. However, Steinberg does not seem to be reading these posts, even though they say they do. They probably don’t test with old projects either, but always use the latest versions. As a result, however, they cannot understand this bug.
Workaround 2:
The ‘Save as’ method.
I’ve given up by now and use these workarounds. It’s very time-consuming, especially if you still have older projects.
It could be resolved if Steinberg were to include a function to gently delete duplicates without corrupting the MIDI ports.
Furthermore, the assignments shouldn’t be changed on the fly in the Globalmappings file. This causes errors that then affect other projects as well.
I think it was a mistake to allow the MIDI Remote to be used both globally and on a project-by-project basis, and for the MIDI Remote settings to be saved within the project file as well.
I think settings should be either saved in the project OR the program - certainly not both!
This issue still killing my workflow every day!
Guys - please!
Or just give us the choice somehow…
