Cubase doesn't keep MIDI port assignments after restart

Support & Troubleshooting Cubase
1

Hello MetaGrid Team, Windows 10, Metaserver 6, Ipads 6,7,8.

I am attaching a video that demonstrates several serious issues I am experiencing.

  1. Cubase 15 does not keep in memory Metagrid midi controller ssurfaces after restart its completely BLANK !

  2. When I installed MetaServer 6, the software would not start correctly. I immediately received red warning messages indicating that MIDI ports were configured incorrectly or could not be detected properly. Because of this, I had to revert back to MetaServer 5.

  3. After updating to the latest version of MetaGrid, I discovered another major problem. When trying to edit the MIDI channels of my faders, the editor does not work correctly. I attempt to change the MIDI channel numbers, but the values simply remain unchanged. The software ignores the edits, making it impossible to configure the faders properly.

I have attached a video showing these problems in detail.

I would also like to make a sincere request. Please focus on stability before adding new features. At this point, the issue is not a matter of months—it has been years. The original versions of MetaGrid had their own problems, particularly with Connect/Reconnect behavior, but they were at least usable for real work.

Currently, I feel stuck between old versions that crash and newer versions that are still too unstable for professional daily use. As a long-time user, I would much rather have one solid, reliable version than additional features that introduce new problems.

Please, I am asking you to prioritize stability, reliability, MIDI functionality, and compatibility over new features. MetaGrid is an excellent concept and an extremely powerful tool, but right now the instability makes it very difficult to depend on in a professional environment.

Thank you for your time, and I hope these issues can be resolved.

Best regards,
Ivan

2

Ivan - please have a look at this:

For the faders - export the problematic fader for investigation.

I understand your frustration - the situation on the Windows front is frustrating for us as well - all our test systems are working correctly on the new MIDI Services. Please upgrade to MIDI Services per the post above.

I love your keyboard :-).

1 Like
3

I think he said all his faders were broken.

1 Like
4

Yes, the major problem its EDIT function and faders , no chance to edit and save Midi channels.

( I have looked in Services on my Windows 10, i dont think i have such service on Windows 10 ((

5

I’m with you. I’ve been waiting 3 years for them to sort out the connectivity and incoming MIDI issues. And now were moving over to a whole new system with Win MIDI services. It looks like another three years of waiting for bug fixes.

1 Like
6

please send us the fader grid for investigation - can’t replicate it on any of our test systems.

7

Can you check if you remove the fader and add it again and see whether the values stay? And can you try on different grids? Can you also check if you have this fader assigned to internal Cubase functions next to the text label?

8

What i did right now was:

I re-installed Metagrid 1.5.7 , i did not import any my custom older Cubase Grids, just downloaded new Cubase prerset on to Metagrid 1.5.7.

Without my older Dropbox grid it seems Faders WORK and assignable.

But if i Restore from older backups or download any older CUSTOM versions of grids of Cubase faders the are stuck at editing .

I presume older CUSTOM grids somehow are not compatible with some new updated Metagrid things(???)

9

please send me your old custom grid for investigation.

10

I am away from my computer right now but definitely do asap!

11

Here is my full backup

12

Cubase Grid Selected channel

13

Hi everyone, there a new Cubase update download it and see if it fixes anything, the release note says there is some improvements in MIDI Remote API

1 Like