Dorico (using keyswitches) to Cubase

Hello,
I’ve been using Dorico for a couple of years now and it has emerged victorious over everything else. Now I want to add Cubase 14 and am trying it.
everything I’ve read indicates that Cubase (14) should understand my keyswitches after importing a midi exported by Dorico.
However I doesn’t quite look like everyone elses. Here’s a picture

I have made some extensive keyswitches in Dorico (mostly for East West) Is AI making things up or is this possible?
thanks🫡

1 Like

Unfortunately, this isn’t the case. There is nothing in a MIDI file that gives any clue to whether each note is a key switch or not, or which application exported it. Cubase and Dorico expression maps are quite different.

We’re looking at ways of improving the use of Cubase and Dorico projects together for the future.

2 Likes

Thank you

Just jumping in as a fellow Dorico to Cubase user currently involved in this exact workflow… what I am doing which seems to work ok is ensuring I am using all the same instruments/patches with keyswitch settings, as I have them mapped in Dorico, when I bring over to Cubase and don’t bother mapping, the keyswitches from the midi still effectively trigger the instrument’s techniques as it should, without me having to do anything additional.

Unfortunately I can’t really see them as techniques in the same was as I would in Dorico, or in Cubase if I were to set up an expression map manually, but it is nice knowing that the data does seem to work fine as long as I’m using all the same instruments in the same way (I use VEPro to make this even easier). I can see they are keyswitches and then tab over to Dorico to view the score for reference if needed.

Also just as a tip keyswitches are generally easy to spot (though not always), on higher/middle range instruments they will usually be extremely low out of range, like C0, F-1, etc. And for bass instruments they will be the opposite, so you’ll see stuff like C6, G7 etc. Also they are really long making them easy to see compared with most music (with the exception of long pedal tones!). Apologies if this is all already obvious to you, I just mention since it does make it easier if you want to build expression maps in Cubase to match, you could then see the existing keyswitches as a guide, and then mute them when finished.

I look forward to the Steinberg team finding a way for the apps and their maps to talk to each other!