Full stop working Metagrid with Cubase 15 integration

[ivan_jochner]

MetaGrid Pro / MetaServer 6.0.1 Beta 2 – Multiple Issues with Cubase Integration

Hello, Windows 10, Metaserver 6.0.1, Metagrid 1.7.1. ( Ipads 6/7/8/)/ Cubase 15.0.30

I would like to report several problems I am experiencing after installing MetaServer 6.0.1 Beta 2.

1. Installation Warnings (Red Flags)

After installing MetaServer 6.0.1 Beta 2, I received the same warnings that I had with the previous MetaServer 6 version.

MetaServer reported that some required files were missing, specifically related to:

• Project Logical Editor

• Logical Editor

I reinstalled these components, and the warnings appeared to disappear, but I am not sure whether everything was installed correctly.

---

2. MIDI Configuration Warning

In the MIDI section, MetaServer displays a yellow warning indicating that the required MIDI ports are not selected or configured correctly.

However, I have already created the necessary LoopMIDI ports:

• Cubase Sync In

• Cubase Sync Out

These synchronization ports are visible and available in the system.

I am not sure why MetaServer still reports a MIDI port configuration problem.

---

3. Cubase Detects MIDI Activity, but MetaGrid Commands Do Not Work

Inside Cubase, I configured all required MIDI ports and enabled them where necessary.

I also disabled needed ports under "All “Visible Ports” as required.

When I move a fader or trigger controls from MetaGrid, Cubase shows incoming MIDI activity, so MIDI data is clearly reaching Cubase.

However, none of the new MetaGrid 1.7.1 commands actually work.

Cubase receives MIDI activity, but there is no response from any MetaGrid functions.

---

4. Cubase Grid Loads on iPads, but No Control Is Working

When Cubase starts or closes, all three of my iPads correctly react to the Cubase connection status.

The Cubase Grid loads automatically on all devices, which suggests that communication between MetaGrid and Cubase is partially working.

However:

• Cubase does not respond to commands.

• Transport controls do not work.

• Channel controls do not work.

• General MetaGrid commands do not work.

So the connection appears to be detected, but actual control functionality is missing.

---

5. MIDI Remote Devices Disappear After Restart

Another serious issue concerns Cubase MIDI Remote.

I create and configure MIDI Remote devices for:

• Selected Channel controls

• Cubase commands

Everything appears correctly after configuration.

However, after restarting Cubase, these MIDI Remote configurations disappear and are no longer available.

As a result, I have to recreate them repeatedly.

Script activated

---

Then after Cubase restart - scripts are no longer available.

6. Previous Fader Freezing Issue

Previously, I demonstrated an issue where changing MIDI channels on a MetaGrid fader caused MetaGrid to freeze.

At the moment, this specific freezing issue appears to be gone.

However, although the freezing no longer occurs, almost nothing is functioning correctly.

---

7. Folder Structure and Installation Questions

I am also confused about the required file locations.

The Logical Editor and Project Logical Editor files now exist in multiple locations, including:

• Steinberg Documents User folders

• Application Data folders

I do not know whether I am expected to manually copy files to specific locations.

Could someone please clarify:

1. Which folders should contain the Logical Editor and Project Logical Editor files?

2. Does MetaServer automatically install them, or is manual copying required?

3. Why is MetaServer still reporting configuration problems even though the files and MIDI ports appear to be present?

At the moment, MetaGrid is essentially unusable because Cubase does not respond to any commands despite MIDI activity being detected.

8.Additional Question About Generic Remote Configuration

When I open Studio Setup in Cubase, the new MetaGrid PDF manual states that there should only be:

• Generic Remote

• Generic Remote 2

These are the two Generic Remote devices to which the new MetaGrid macro files are assigned.

However, I am confused because in some of the documentation and tutorial videos I see references to additional Generic Remote configurations from previous MetaGrid/MetaServer versions.

For example, I still have entries related to:

• MetaSystem 1

• MetaSystem 2 and 3

• Other older MetaGrid Generic Remote configurations

My question is:

1. Should these older Generic Remote devices remain in Cubase?

2. Should Generic Remote 3, Generic Remote 4, Generic Remote 5, etc., still be present?

3. Should I keep the old MetaSystem configurations from previous MetaServer/MetaGrid installations, or should they be completely removed?

4. Is the new MetaGrid 1.7.1 workflow supposed to use only Generic Remote and Generic Remote 2?

At the moment, the documentation, videos, and my Cubase setup seem to show different configurations, so I am unsure which setup is actually correct.

Could someone clarify exactly which Generic Remote entries should exist in a clean and properly configured MetaGrid 1.7.1 installation?

Any help would be greatly appreciated.

[greggybud]

I have similar issues here.

I believe I read that the Metagrid update continues to use the Cubase Generic Remotes. And fwiw, I don’t think the “depreciated” generic remotes are going anywhere…at least for a while.

IMO this is pure beta testing. I suppose the argument is that due to the nature of Metagrid, they really need hundreds of testers which I doubt they have. I have a support ticket that says a 6.0.2 hotfix should be out today.

[ivan_jochner]

The only workaround when all things work is when i uninstalled new metaserver and went back with version 5 , re- assigned metasystem 1,2,3 and macros with old fashioned way. So New metagrid 1.7.1 works well with old metaserver.