Thank you for the response. After reading through the linked thread, though, I must admit that I am confused. I thought we are talking about a Windows-exclusive problem. The thread, however, doesn’t even mention Windows. It discusses a remote API problem on MacOS. Is it an issue that exists regardless of the operating system? If so, why do you recommend MacOS users to use the new remote API functionality and Windows users not to do so?
My bad for pointing to the wrong thread - the error in the console sometimes rarely appears on Mac (lot of people including all our test systems are running fine), however it is present on all Windows installations. So that’s the core of the issue.
Thank you, that makes sense. Is it always one particular call in the script that triggers the error? If so, could you please point out the relevant part of the code?
It seems that Metagrid might have given up on Cubase Midi Remote on Windows. There was no response to the @jditte request above for more details of the issue. The new website drops the year-long (?) commitment to getting it working with the text saying “MetaGrid Pro delivers powerful Cubase and Nuendo control through Steinberg’s MIDI Remote API on macOS and optimized Generic Remote workflows on both Mac and Windows” .… although the “Deep Integration” table suggests it works on Windows.
There appears to be a standoff. I’ve had a Steinberg support request querying the issue active since August 2025 via the local Yamaha process. They’ve stopped responding to my follow-ups seeking a response. The silence of Cubase representatives on the Cubase/midi-remote posts on the Steinberg forum is deafening. And there is a sense that Steinberg have dropped the ball on the project with the (Github) Midi Remote API Programmers Guide stationery on v1.1 for some time now.
Yet there seem to many working implementations on Windows. And Steinberg appears to have worked closely with Nektar on the CS12 with Nektar’s Tim Chandler a ‘frequent poster’ on CS12 related posts.
I have some concerns about Metagrid and Windows which may also impact. The MetaServer Mac 6.0.0 announcement made no mention of a schedule for a comparable Windows update. There are no ‘Windows’ or ‘Mac’ tags in the forum to make life easier following the bugs. There is no evidence that Metagrid had anticipated the rollout of the rewritten Midi stack, a project that had been evolving for a few years and had released a beta sometime ago. It’s welcoming to see the catchup.
The Cubase integration was a key marketing plank in the early days of Metagrid. And the Generic Remote has considerable power as users on this and the earlier forum have shown. It would good to have some confidence in the future of Windows compatibility including Cubase midi-remote.
Thanks for long post. MetaGrid Pro works fine with Cubase on Windows through our Generic Remote implementation. It just MIDI Remote that is faulty - one method - that is crucial in our implementation giving access to dynamic parameters for the inserts, sends etc for each slots - is not supported by Cubase on Windows but it is available in the documentation, works on most Cubase builds on Mac.
We have designed something unique that no other MIDI Remote controller does - to give you the full overview of all inserted plugins and sends. And this freaking method for getting access to these data is not consistently supported by Steinberg. We can’t do much about this - we asked Cubase PM about helping us with this, we reached out to the Steinberg people working on MIDI Remote - nothing - they are dead silent about this. Of course we can do a simplified MIDI Remote for Window - but feature wise it would be equal to our Generic Remote implementation so what’s the point in that? We are as frustrated as you Guys - we developed a beautiful and super useful solution for Cubase but the curcial component is not properly supported by Steinberg across all platforms and Cubase builds.
We are working on MetaServer 6.0 for Windows - it is substantial rewrite and we need some time for this - we hope to have it ready for beta testing at the end of April.
1 Like
I want to ask something that hopefully doesn’t get taken the wrong way. I created a controller using AI and OSC (Open Stage Control) in the course of about a week. The controller has fully functioning dynamic labels for QC, RCE, Inserts, you name it. Why is it possible with Open Stage Control but not Metagrid? Genuinely asking. Not trying to sound facetious.
Hi Dylan - first of all, congrats! It has nothing to do with MetaGrid Pro - do you have access to all slots at the same time? And are you on Windows?