Sorry, but another problem. No plugins show. W11 Cubase 15.0.21
I get the same screen
Are you running Selected Channel MIDI Remote script?
I gather I am doing something wrong, how would I install this script? I only see the commands script in the MID remote manager.
Go to MetaServer > Installations and install / reinstall the Selected Channel script. Then in Cubase / Nuendo open the MIDI Remote Manager, add the new surface and select the Selected Channel device from Metagrid Pro group - you should see two devices there - Selected Channels and Commands.
MetaServer > Installations and install / reinstall
However, I did see in Cubase both selected channels and commands. I added a surface for selected channel but not sure about which port. there was no port available that said āmetasystem cubase inā like the commands has. i picked āmetasystem cubase sync inā and i still donā[t see any plugins. not sure how the input and oiutput ports needs to be set up.
It should be Metasystem - Cubase Sync port - thatās the issue I guess.
Nothing, I closed all and started again and still nothing.
Wait, I went back into cubase and it does not save the surface. only commands stays, no channel
I tried again, but when I close Cubase and reopen the surface is no longer there. Only the commands surface persists. (and even when i set up the channel surface, no plugins showed up)
OKay, now there are several problems. I have it with windows midi loop and using cubase sync, and still nothing comes up in the list.
ALso, now the Commands surface never saves. I delete Channel surface and when I restart all I see is the Channel surface, no matter what I do, delete it, add the Command surface, have both of them, no matter what, when close and reopen cubase I only see the Channel surface, nothing else.
I donāt know if this is a Cubase or MG problem, i have to add the Command surface every time i launch CUbase and also the Channel surface does not show the vsts.
Is there a way to reinstall the scripts? Where do we get the scripts? They seem to have installed during the installation process and I donāt have access to them directly.
Now I donāt see Selected Channel" as an option to install in MIDI Remote, I verified the file is in the correct folder
Iām having the identical problem as the OP. Honestly, isnāt this stuff that should be readily availableā¦maybe even idiot-proofed PRIOR to watching the new video tutorial where everything justā¦works?
Iām an idiot. I donāt venture into Cubase Midi Remote often. Itās one of those āset it and forget itā things once your devices are working. Anyway, Iāll stumble through this tomorrow and see if I can get lucky.
For the OP, thanks for bringing this up. You are not alone, and sureā¦it could be something stupidly simple.
Understand your frustration, guys. Thereās nothing simple for Windows at this very moment, and to be clear up front: the root cause here is on the Windows side, not MetaGrid.
-
MIDI Services arenāt officially bundled with Windows yet ā you need to download the GitHub repository. There are instructions in MetaServer for this.
-
loopMIDI and legacy support ā recent Windows 11 updates (the new MIDI 2.0 / Windows MIDI Services stack in 25H2) have broken loopMIDI badly. Virtual ports disappear after reboot and control surfaces fail to persist ā which is exactly what youāre seeing with the Selected Channel surface not saving. Thereās no clean permanent fix from Microsoft yet, but the known workaround is to restart the Windows MIDI Service (Win+R ā
services.mscā Windows MIDI Service ā Stop, then Start) whenever ports go missing.
On timing ā thereās no fixed date from Microsoft yet. Windows MIDI Services is now rolling out in-box via Windows Update (phased, so not everyone has it), which means the separate install is gradually going away. But the loopMIDI-style loopback support is still preview-stage ā Microsoft has said the proper fix is still in progress ā and thereās no published timeline for when the legacy breakage is fully resolved. For now, the GitHub install plus the workarounds above remain the reliable path.
On our test setups MetaServer with MIDI Services work like a charm - all ports are kept, MIDI scripts work amazingly well, Metagrid Pro is super responsive - especially through USB - no perceivable latency on faders etc.
So the solutions are:
- go full MIDI Services with all latest Windows updates
- use the workarounds for legacy MIDI - which means that you will have to add MIDI Remote devices each time you start Cubase / Nuendo.
I havenāt updated my Windows machine, so I donāt have the new MIDI services. Is it possible to use Metagrid 1.7 with Loop MIDI ports and the new channel MIDI remote script? Right now Metagrid 1.6.9 is working really well on my windows machine, but I really would like to have the new functions of MGP 1.7.0
Yesterday I installed 1.7.0. Iām on Windows 10. The main reason I did that is to take advantage of the 1-button press to open a Cubase VST which looks wonderful! Watching the video tutorial, I noticed Metagrid had created that script.
I installed 1.7.0 and everything looked and ran good. I noticed some new features such as Icons underlayed with button text added, but didnāt pursue any others. I wanted to make sure what has generally worked for monthsā¦still works on 1.7.0.
After an hour feeling confident there were no issues with 1.7.0, I attempted to get the Cubase 1-button feature going. That is when I ran into issues. As said above, Iām not fluent with Cubase Midi Remote because once things are set up, I tend to forget about it.
First of all, where or how do I get the Cubase scriptā¦the thing shown in the tutorial? I have the latest Cubase Pro and the latest MIDI API. Then, I noticed there was a new Metaserver! I uninstalled the old Metaserver, installed the new Metaserver which is much more elaborate, then experienced errors that were shown in Metaserver. I made some changes, but the midi port errors shown in Metaserver did not go away. Initially, I thought I read that you no longer need Midi Loop Back. Iām still using it today.
Eventually, to clear the Metaserver errors, I did a PC re-start and then Metaserver showed no errors. See what I mean by lack of documentation here? There is too much trial and error. For myself, I need baby steps. Maybe even a flow-chart?
So, on day 2 now, I can say 1.7.0 works as intended. But not the new Cubase buttons feature for VST. And donāt forget to download and install the new Metaserver!
My connectivity issues that have been happening for monthsā¦ever since upgrading from Legacy where I had no connectivity issues to the Pro version have continued with 1.7.0. On my end with connectivity, one work-around is re-plugging the usb wire. The work-around that works 100% of the time is opening Device Manager, then under Universal Serial Bus Devices, and Apple Mobile Device usb composite device,ā¦disablingā¦then enabling it.
Also in the new Metaserver, I have configured it so it should start when my PC starts up every day. It does not automatically start, so I manually start it from my desktop.
I have written several support requests to figure out what is wrong, as itās probably on my end, and why every day I must go to Device manager but so far, no replies. And now Iām guessing time will be taken up with other 1.7.0 issues.
@greggybud see this:
Thanks, but Iām still on Windows 10. Do you have something similar for Windows 10 users?
When I try to add a plugin or through the AI it doesnāt work and in the log I see a message to install Apple device, does this feature require USB connection? anyone using only WiFi has this working?
I am on wifi (PC W11) and cannot get the vst list. I tired to connect using USB but MG server does not see my ipad, only on Wifi. I gather there is some setting to fix this.
Today I updated Cubase to version 15.0.30, so far everything is working, selected channel shows all information, commands work, plugin list shows and works, fingers crossed! CC sliders work.
1 Like