[Fixed] MetaGrid receives Cubase plugin list after MetaServer update

Support & Troubleshooting Cubase
1

Hi, I just updated Metagrid to 1.7.2 and the corresponding new metaserver versions and while on my Mac I can use the insert plugin action on the PC Metagrid cannot get the plugin list list from the server.

If I create a button to insert a specific plugin on my Mac and then copy the macro to the Windows section I can then use this button to insert a plugin on the PC, so the side that doesn’t work is the receiving one in Metagrid.
On the PC I have not upgraded to the latest Windows 11 and corresponding MIDI services, so I’m still using loop MIDI for the MIDI ports, and the installed metagrid scripts, both the commands and the selected channel ones, vanished every time I closed Cubase. So I realized that I had to edit the scripts to change the MIDI ports name to the one that I currently using. Now the the scripts are permanently installed in Cubase, but I’m wondering if these MIDI port changing is the things that is blocking Metagrid from receiving the plugin list from Cubase.
On which port is Cubase sending Metagrid the plugin list? Is this port written in the script itself?

2

it is Metasystem - Cubase Sync

3

So, given that I changed the ports name to Metasystem - Cubase Sync - In and Metasystem - Cubase Sync - Out (with Loop MIDI you have to create 2 different ports, one for in and one for out) in the script and that I’m able to insert plugins, with the buttons created on the Mac, it should work, right?
What else can be blocking Metagrid from receiving the Cubase plugin list?
I’m connected with Wi-Fi and my Networks is set to public; Metaserver is stating that the network should be set to private, but if I set it to private my Mac is not connecting anymore to the shared folders on the PC.
Metaserver says also that my Wi-Fi is off but the Wi-Fi is actually on and my iPad can connect to the PC with Wi-Fi

4

@Project Send us the logs from MetaServer on Win and MetaGrid Pro - we need to see what’s blocking the pipeline.

5

Thanks, here are the logs

Logs.zip (371.3 KB)

6

Windows 10 here.

@metagrid_admin, Thank you for directing me to the pertinent information how to set this up. I too am experiencing scripts that vanish when restarting Cubase.

I think I need to use Loop Midi? I have been using Metagrid for years using the Cubase Generic Remotes, and I certainly don’t want to loose that. But I think they won’t work without Loop Midi correct? And of course I want to use the Generic Remote too.

Currently, once I activate Selected Channel Surface, or Commands Surface, the Cubase Transport Bar (midi in /out) shows what I believe is midi feedback and once I press Play in Cubase, I can’t stop it. I’m forced to close Cubase.

“Uncheck the In All MIDI Inputs column for all Metasystem ports except Metasystem - MIDI - In (keep that checked if you want to record MIDI from MetaGrid Pro on tracks).”

I’ll double check again to make sure on the Cubase Midi ports IN column, that All Midi Inputs except metasystem midi in is unchecked.

Prior to these instructions, I believe there was just 1 port that you had to uncheck? That was mentioned in the old manual. Has this changed?

"Step 3: Assign Ports

Set both input and output ports to Metasystem - Cubase Sync - In/Out (Mac) or the corresponding LoopMIDI ports (Windows)"

Since I’m on Windows 10, I don’t understand what you mean by “corresponding loop midi ports.” I have 4-5 Loop Midi ports to select from. Which one do I choose?

Are there any video tutorials for Windows 10 and users that desire using both all Cubase generic remotes as well as the Midi Remote?

Maybe a better way is to simply delete all my created ports in Loop Midi and start over? If that’s the situation, is there a guide to follow here that maybe I missed? Again, like Cubase Midi Remote, this stuff is set it and forget it. I have forgotten Loop Midi over the years, and now I’m struggling.

7

@MetaGrid_Admin where you able to take a look at the logs? Another strange thing happened in the meantime. While connected to Metaserver on PC MGP switched connection and connected to the Mac but it still continue to send to the PC the commands going thru the MIDI Remote, it just stopped sending commands going thru the Generic Remote.

8

A gentle bump, since it’s been 8 days that I asked the original question dnd shared the log

9

@MetaGrid_Admin Did you get the chance to look at the logs I uploaded here?

10

yes, we have looked at the logs - and we have implemented some improvements in the upcoming MetaServer / MetaGrid Pro version

11

Thanks a lot, I’ll update the thread when the new version come out

12

I was able to get the plugin list as soon as I upgraded to the latest Metaserver version; this happened before upgrading to MGP 1.7.3, so the new Metaserver version solved the problem, thanks a lot for the update! I think now you can close this topic

13

Thanks for confirming. I’m glad the plugin list started working after updating MetaServer.

This topic is now marked Fixed and will be closed. If the plugin list stops loading again, please open a new support topic with the installed MetaGrid Pro, MetaServer, and Cubase versions.