@MetaGrid_Admin
Bumping this to a new, specific thread so people can search for it better.
Stability seemed to improve, and I can now stay in the app, but now none of the Cubase templates will work. Transport controls don’t work; send faders, selected tracks, etc. I wonder if this is because the Command’s remote can’t be added. Some of these controls worked yesterday, but today none of them do. I have not changed anything since.
I set everything up to a tee from the documentation, except for installing the commands remote on page 10. It’s because Cubase won’t let me set it up. The other day when I tried setting it up, it wouldn’t let me save it because there weren’t any elelemnts on it and when I tried to put a fader or a button on it, it wouldn’t let me because it’s not a real control surface.
But today when I tried again, It doesn’t even list the Metasystem Cubae out in the output section when adding a new device. It’s in the device list, but not selectable when trying to add a new remote. Please see the screenshots.
I’m hoping I can resolve this and start using the app; the videos got me so excited. But since day 1, every day presents a different challenge. If something showed up or worked one day, it didn’t the next. I might have to give up in a few days if I can’t figure this out. I’m supposed to be making music 
I appreciate the help!
OK, let’s walk through this methodologically. I need the screenshot from your MIDI Remote devices - it should look as follows:
@MetaGrid_Admin When I tried adding the “commands” device, it wasn’t pre-populated so I tried to make my own. I did it just like the screenshots, but it said the surface wasn’t stored because there aren’t any elements. I had to put a knob on it and assign it to something before I could proceed.
As of now, the only things working are things like selected track volume, gain, and panning, but the MIDI functions and transport controls don’t work.
Can you include the screenshot of your MIDI devices panel - same as I published here? There is definitely a device misconfiguration on your setup - let’s clear it out step by step.
Oh shoot, I don’t know why the images didn’t stick, I uploaded them. Here they are again.
and this is what it looks like when I try to add the commands device before I added a dummy knob to it.
You MIDI Remote config seems to have some problems - first of all, why some many Panorama devices on our system - they are inactive but there shouldn’t be duplicated.
Our Selected Channel device is active on your system and it seems that it is functional - correct ports are assigned. Can you confirm that the commands like play, record (handled by this device) are working correctly? And can you also send me the screenshot of the content in your MIDI Remote Devices folder:
*Documents > Steinberg > Cubase > MIDI Remote > Driver Scripts > Local
@MetaGrid_Admin I am happy to say, I got it working. I’m not sure why, but I deleted the metagrid folder and just re-added it and it worked. The app does crash in a cubase session about twice every 30 minutes though.
One thing, though, since I have it now hooked up via USB C directly to the computer, I want it to connect like that all the time, unless the cord is disconnected. However, even when the ipad is connected via USB, it always shows wifi connection, and when I go to the connections tab, it doesn’t even show the USB C connection, just wifi. Any thoughts?
@esimone00 The problem with iPad / iOS handling is that when you put your computer to sleep (close the lid) - macOS looses the USB device info and what it is needed is to plug and replug the cord. I know it is sub-optimal - we are working on this and have implemented some workarounds but so far all our attempts don’t provide a reliable solution - on some systems it is OK, some systems they’d don’t work. We have contacted Apple with this.
Regarding the crash - please ensure you have the crash log shared with the devs - we are monitoring and actively fixing the crashes reported by the users.
https://metagrid.zendesk.com/hc/en-us/articles/31182256867985-How-to-Enable-Crash-Logs-on-Your-iPad-and-Share-Them-with-Developers