Anyone know how this is going to work ? Metagrid works so well with Cubase Generic remote I can’t image how complex its going to be setting up MIDI Remote Controllers for the hundreds of functions and page of MG I have
It’s not ready yet, they tried to roll it out but there’s a bug in the midi remote API (I hear only on the windows side) that’s blocking it from functioning properly.
Even if you’re on OS X I strongly recommend sticking with generic remote unless you’re comfortable dealing with a lot of early adopter pain.
Thanks , I’m happy with what we have now just was a little worried that I might lose functionality MG is key to my workflow !
From my understanding, Steinberg needs to communicate with the Metagrid developer in order to get this solved. God knows how long that will take.
I know what it says when you open the GR. I too felt the word “degraded” was quite harsh and I had your same fears.
I don’t think the GR is going away for a while. I feel the strong wording is to push users who can…away from the GR and use the Midi Remote. Too many Metagrid users would be left out in the cold perhaps looking for an alternative DAW if they just dropped the GR.
Even when a way becomes possible to transition from the GR to Midi Remote, it’s going to be a very long and tedious task. I can’t fathom any type of converter being developed for the transition.
It’s been years.
How about the developer of Metagrid approaching Steinberg? He is a busy guy putting out meta server update fires, while seemingly pushing Metagrid too fast resulting in too many issues. IMO this is part of the problem. He is trying to morph traditional Metagrid functions toward the DAW controller market.
I personally prefer 2 separate machines, 2 very different tasks. But I’m probably the minority as I notice many users loving the sliders or things that takes up a lot of screen space. It’s sort of like going back to the Lemur… 
1 Like
He’s said they’ve tried to reach out but haven’t heard back yet.
Fixing/tweaking the API is the same reason it took Nektar 12 months+ to port their CS12 to Cubase after it released for Logic.
Midi Remote is still not ready for prime time, evident from the countless posts of disconnects, corrupted preset files, functionality gaps from MCU Protocol, etc. Generic Remote on the other hand is dependable and rock solid, so I’d say stick with that for as long as possible and avoid any temptation to early adopt.
1 Like
Przemyslaw has written that in his forum from day 1 when the new MIDI API control was first released. I get the feeling it’s not as important to him as aiming Metagrid in other directions that in a nutshell, seem like it’s morphing into DAW controller territory. I hope I’m wrong!
Midi Remote certainly has a long ways to go as you say. I’m grateful for the users who have integrated my X-Touch controller so I can focus on other things.
And I agree, Generic Remote, while it’s been mostly ignored for years, is rock solid. I don’t think it’s going to be “depreciated” any time soon. That is just my guess.
There’s certainly a learning curve. But the Mapping Assistant is excellent; way faster than the GR. And overall (besides the controller surfaces not always loading with my projects and basically dying mid session) the MIDI Remote is way better than the Generic Remote IMO.
To set the MIDI Remote up, here’s a few tips:
It is definitely worth spending an hour or so setting up your workflow with a dedicated Scene and Grid in MGP with a bunch of hot keys to navigate. Like Ctrl/Alt/M to open the Mapping Assistant. If you have AHK Or Bome MIDI Translator, I would recommend setting up additional buttons in your grid that can perform mouse movement, clicks and scroll in order to avoid RSI. Definitely set up a numeric key pad in that grid.
Set up a button for ‘Map’ as well as ‘Assign Channel’ and ‘Assign CC’ and ‘Learn’. So after creating a button or fader, you can can hit the ‘Map’ button and the mouse will carry out all the necessary movements and clicks. And go full screen, don’t do it in the Lower Zone.
The things I like about the MIDI Remote are that bug shooting is really easy because conflicted CC’s or note messages are highlighted. Also, hovering over a fader or button shows you which function or parameter it is mapped to. As I stated above, the Mapping Assistant is so fast, just make sure to resize the UI and use its zoom function.
Wow this looks amazing , I have set up lots of custom functions for my workflow , visibility agent stiffly lots of PLE each , I don’t use any M( presets just my own ,
What I’m a little confused about As I don’t fully understand the connection from MG to Cubase .
I use Eucon and just hit the add button in studio set up and it works ,
I thought adding the MG midi remote was the same of thing and created a connection , which you then can select PLE and scene etc ..
I’m really a little confused about how this would work with the new midi remote as there would be no PLE or screnes and I’m not sure how you would access the menus etc
In the Lower Zone
Select ports
Go to full screen
Assign channel and CC
Learn channel and CC
Right click button
Find function
That’s great I’m gonna look into this , so we’re do you set MG ?
What I’m trying to get my head around (sorry if I’m asking silly questions here) is at the moment I am selecting a cubase function inside MG on the iPad app which is listed inside the MG it’s self ,
Are you create functions your self and just sending some kind of message from MG to trigger that function in midi remote ?
Yeah I am. Because I already had everything set up in the GR way before MG was a thing. And using the scripts that Metasystems provides would have no doubt caused many conflictions with my existing CC and Note On messages.
Here’s an illustration of how to get MG connected to the MIDI Remote. This screen pops up after hitting the + in the Lower Zone.
Okay, I really like what you’ve done, but for me it’s overcomplicated compared to the scripts in MG , as you would have to create a button, then assign that button to a function in which controller or midi triggers that function , coming back to it after time you’d have to keep checking which many notes you haven’t haven’t used I imagine.
it’s so intuitive programming buttons , functions and meu items on the iPad with MG scripts and Menu commands, as you’ve got your workflow all sorted, before MG came along, I can see how it works for you,. But go forward I would really like to see MG have a section like Eucon does in Studio set up.
I really hope Steinberg take this seriously it’s such a powerful tool for Cubase
Well, that is the actually one of the main advantages of the MIDI Remote - any conflicts are highlighted. So as soon as a CC is assigned to a button, a (!) pops up telling you that that CC is already in use.
Well that is great ! I’m sure it’s an amazing system you have , and midi remote is really powerful. As I use Eucon and MG I haven’t had much need to program in Midi remote at this point . Thx again for you epic info
Andy