As soon as Cubase 14 opens I get a window called MIDI Remote Script Console showing an error message.
Mac OS Mac Studio Ventura 13.6.6
MGP 1.6.5 Beta 3 - Metaserver 5.2.0
iPad Pro (iOS 18.1.1)
Cubase 14
Coincidentally, the iPad is being quite flakey when trying to connect to the Mac Metaserver. Connects for a few minutes, then crashes. Comes back and connects automatically, then crashes. Then needs to be ‘refreshed’. Connects. Crashes. Won’t connect at all now.
Have you installed the MIDI Remote devices that come with MGP 1.6.5 Beta 3? We don’t have this message on the console - everything compiles ok. Please confirm.
Yes, Commands and Selected Channel from the download link in the ‘Adding MIDI Remote Devices in Cubase’ post.
I continue to get the error message (shown in my original post above) every time I open Cubase 14. I’ve heard nothing more from you. Do you have any suggestion for fixing this?
Mac OS Mac Studio Ventura 13.6.6
MGP 1.6.5 Beta 3 - Metaserver 5.2.0
iPad Pro (iOS 18.1.1)
Cubase 14
Thanks - Joe
OK, we can’t replicate this error on our test systems - Cubase 14 loads without any issues. So I believe the device is not loaded right? Or is it working but you have only the error on startup? If it is working, does it happen on every project you open?
The Error message does not appear on starting up Cubase 14, it appears when I open any existing project or a new project from a template. Whatever the error message is indicating does not seem to affect Cubase’s functionality. Although I wasn’t sure that some of the ‘bugs’ I’ve been reporting here weren’t caused by the error. What do you suggest I do?
We have checked the code at line 700 - no issue with the code - it is the line that gets the data for the first insert. From syntax/API perspective it is correct - and as mentioned before, we don’t get this code anywhere across all the projects. Can you please create a new project from scratch, don’t add any tracks and see if it appears as well.
Same error occurs when opening a new empty project.
This error persists with 1.6.5 beat 4 and new metaserver 5.2.0 (Jan. 21).
Continuing to get an error on opening any Cubase 14 project. Although it’s changed from 700 to 699. It doesn’t seem to be affecting anything, but it’s still concerning.
Mac OS Mac Studio Ventura 13.6.6
MGP 1.6.5 Master Gold - Metaserver 5.2.0 (Feb. 8)
iPad Pro (iOS 18.1.1)
Cubase 14
Thanks,
Joe
We can’t replicate this - we have pinged Steinberg about this - generally it seems that Remote MIDI implementation in Cubase is far from being perfect - the code compiles OK and no errors on our test machines and no problem per compilation. The error you are showing should make the whole script not working at all… It is very frustrating - not to mention the Windows side…
Hello !
I followed the exact steps to setup midi remote to cubase 14.
I have installed the latest Metaserver and Metagrid Pro versions in both my machines.
Procedure completed fine on my MacBook Pro (M3 Max - Sonoma OS).
The same procedure on my Mac (Intel - Ventura OS) gives an error for the selected channel script.
In metagrid pro Some buttons are working and some don’t .
e.g. Phase 0 , all the pre filter section buttons , control room level fader.These don’t work
Track volume , pan , work fine…
The funny thing is that on my MacBook everything works as expected.
Thanks in advance
Same issue here.
On the iPad the sends and inserts aren’t populated or responsive.
In at the point of giving up.
It’s too buggy to take a Premium subscription out.
It seems to be Steinberg API error - as mentioned above, the js script works fine on Sonoma - while on Ventura we have error messages. We have moved this to Steinberg for clarification and we are still waiting for the answer. As mentioned, our code is OK and should work as expected on any MacOS version.
Hello !
I followed the exact steps to setup midi remote to cubase 14.
I have installed the latest Metaserver and Metagrid Pro versions in both my machines.
Procedure completed fine on my MacBook Pro (M3 Max - Sonoma OS).
The same procedure on my Mac (Intel - Ventura OS) gives an error for the selected channel script.
In metagrid pro Some buttons are working and some don’t .
e.g. Phase 0 , all the pre filter section buttons , control room level fader.These don’t work
Track volume , pan , work fine…
The funny thing is that on my MacBook everything works as expected.
Thanks in advance
Hello !
I followed the exact steps to setup midi remote to cubase 14.
I have installed the latest Metaserver and Metagrid Pro versions in both my machines.
Procedure completed fine on my MacBook Pro (M3 Max - Sonoma OS).
The same procedure on my Mac (Intel - Ventura OS) gives an error for the selected channel script.
In metagrid pro Some buttons are working and some don’t .
e.g. Phase 0 , all the pre filter section buttons , control room level fader.These don’t work
Track volume , pan , work fine…
The funny thing is that on my MacBook everything works as expected.
Thanks in advance
Hi Guys, I unfortunately get a script error when I try and install the new Cubase Channel Controller…
“TypeError: undefined not callable (property accessSlotAtindex’ of object Object) (line 699)”
It still allows me to add it and some of it works in metagrid, but it doesn’t show inserts and a whole host of features are missing.
Any clues how to fix this?
iMac Pro, latest Mac OS, latest Metagrid Pro and Metaserver (downloaded this week), Cubase 14.0.5
We can’t replicate it on our test systems. We have asked Steinberg for help - there are no issues in the code and we have done everything according to the Steinberg’s specs. We will be testing the controllers this weekend.
Hi, same issue here, i got this error message too.
