Expression maps STILL BUGGED making Cubase IMPOSSIBLE TO USE ANYMORE

Cubase
,
1

I feel utterly frustrated and defeated that this bug still hasn’t been fixed with Cubase 15.0.20

Expression maps are vital for orchestral composers. Everything worked fine in Cubase 14. We could select articulations, they were instantly called, and they just worked. Now, with this “new and improved” expression map editor, they just stop working randomly. For instance. You can write in your articulations and they will work, but then you click an articulation from within either the instrument itself, or (as i do) trigger the key switch from an external iPad (All i’m doing is sending a note - ie: C-2) and it can throw everything out, or not trigger at all. It will randomly just move all the articulations up into random articulations ( i think it might be transposing all the articulations up to a random place), or it will just freeze out and not let you select any different articulations at all. And you have to delete tracks, delete data, reinitialise the patch etc etc. This is an absolute gamebreaker for orchestral composers. My whole work process has now had to change to “Do i want Legato?” use this track… “Do i want Spiccato for these notes?” Make a new track with only Spiccato selected.

Obviously, this then makes it impossible to export sheet music for a live orchestra, as it’s just tons of separate tracks.

Please respond. Please please please. This is utterly breaking everyone who uses Cubase for Orchestral composition.

2

I actually thought it was me doing something wrong. I wondered why it was not consistent.

It’s not only this that keeps me from using it. I don’t have as complex of arrangements, so I will just use midi notes on the editor until this all gets streamlined.

3

Is your iPad also sending the note-off?

See this post: Cubase 15 Expression Maps - A fix for software articulation trigger unreliability

4

You, sir, are an absolute superstar.

I searched high and low for a fix. You’re absolutely right. Cubase 15 now requires a note off as well as a note on. In its own expression map it doesn’t require it, but if you’re using an external controller (I am using Metagrid Pro like the post you linked) it also now needs to send a note off on a small delay.

Now i just need to go through each and every one of my kewyswitch grids in Metagrid Pro and add the extra code. Joy…

But still, you’ve made me a VERY happy boy. Thanks so much.