Cubase 14 does not load custom midi remote scripts

Cubase
1

Hi,
Cubase 14 does not load custom midi remote scripts e.g. for Presonus FP8. I have to add a new surface each time after Cubase is loaded. Same issue as in 13.0.50.

13.0.41 worked well

2

Hi,

This is a known and already reported issue.

3

I reported it a moth ago and it 's still not fixed. Can we at least get an approximate timeframe when that might happen?
I am not using my controller anymore, I am too lazy to keep adding it every single time.
Thank you

4

Hi,

There was no maintenance release since then, so there was no release, where it could be fixed.

Cubase 14 is not out for month already. Today it’s 16 days from the release. Please, be realistic.

1 Like
5

I understand, i said over a month because that issue was already in 13.0.50. I’ll continue to wait.
Thanks

6

Problem is still present in 14.0.10.

7

Additional question. Has anything changed regarding the JS midi remote scripting that can create this issue? Does someone know?

Regards
RBV

8

Well, I was realistic and waited patiently and it’s not what you said it’s going to be. This is so frustrating. Cubase 14.0.10 did NOT fix the basic problem.
I don’t know what to do anymore, why Steinberg is not listing and fixing basic features. Who cares about modulations and all other fancy features if we can’t fix the basic MIDI remote automatic script loading!!!
I am so disappointed…

9

Nothing changed, I have the same issues and they promised it will be fixed in 14.0.10 an it’s not. VERY VERY VERY disappointing.

10

This happens to me as well, I don’t think it will be fixed in version 14, maybe 15. The new update did NOT fix this issues. So annoying

11

My FaderPort8 is recognized again

I finally find my issue: There was a typo in my script for the name in expectOutputNameEquals

It looks like that Cubase now proves exact the names of the ports. In the previous version you could use places holder and assign the correct port names later in Cubase, and these names are remembered. But it seems that this behavior has now changed (perhaps accidentally).

With these settings - as these are the names in Cubase -, my script is loaded complete and then started

_deviceDriver.makeDetectionUnit().detectPortPair(_midiInput, _midiOutput)
.expectInputNameEquals(‘PreSonus FP8 Port 1’)
.expectOutputNameEquals(‘PreSonus FP8 Port 1’)

So try to check your port names.

It is also now working in Cubase 13.0.51

Regards
Rolf

12

Well, yes, but it’s not that strict (i.e. checking for equality) as far as I can tell. Even “contains” works here as well. For example:

.expectInputNameContains('PreSonus')
.expectInputNameContains('FP8 Port 1')

.expectOutputNameContains('PreSonus')
.expectOutputNameContains('FP8 Port 1')

This can help when we’re facing Windows adding things like ‘-1’ etc…

1 Like
13

Hi I am using a qcon icon lite and it is not saving
is there some kind of text editor i could use to find and replace port names I need a step by step guide hopefully some guru can help us musicians who cannot program many thanks Mal

14

okay by sheer blind luck I edited expected port names to the exact name that shows in midi devices and IT WORKS now saves and auto loads my qcon lite in both cubase 14 and 13.050 whoo hoo

15

@m.c good to know.

As I had this typo also in 13.0.40. where it works, It looks like that they have changed something under the hood - which now checks the string more closely. :slight_smile:

Regards
RBV

1 Like
16

Would you please let me know exactly what you did and where do you go to fix this? My script is still not automatically loading.
Thanks I appreciate it

17

If you are using a custom script:

In the bottom area in Cubase:

  • select “Midi Remote” tab
  • click on open midi remote manager (gear)
  • select Scripts tab
  • select your script (model, manufacturer)
  • click on the icon beside the “Script Path”
  • here you find the related script, which you can edit now (make a copy before :slight_smile: )

If the path is under “public” you need to contact Steinberg. As these files can be overwritten from Cubase or updates.

18

Thank you so much for your help. I appreciate it. I think I am missing something. I tried adding the three lines to that script but I didn’t work. Please see my script attached and let me know what you think.
Thank you

image
image857×634 26.9 KB

19

They are in a wrong place. Try to put them right below the const outputPort... line. At the same time, I see your ports’ variables named inputPort and outputPort while in the detectPortPair you’re using an underscore as a prefix and wrong port names. You should remove these and use the correct names. I don’t even get why you have _deviceDriver, while just previously you had it named simply driver.

20

Thank you again for your help, I really appreciate it. I spent hours trying to fix this and no matter what I do, it just doesn’t work. I don’t have just one script file, I have 2 folders and a few different files for my one controller (MP MIDI) *see the attached image
The controller is amazing but unfortunately I need to manually add it every time I start Cubase. All of Steinberg support is completely silent on any support.
Martin.Jirsak asked me to wait for the new version as this issue was supposed to be resolved but even he is no longer providing any insights after finding out the issue didn’t get fixed. I don’t blame him, I would hide too LOL
So I am on my own but no matter what I do just doesn’t work. Not sure why I am paying for Cubase if I get zero support and not just use torrents like some people I know.
Thank you M.C, again for trying to help me.
Cheers!

image
image1107×930 70.5 KB