Dragging chord events from Cubase to Dorico mostly works well with basic triads, but not so well with extended chords.
In Cubase, we build extended chords by adding one or more tensions to one of the six triads. The best is to illustrate this with the screenshots of few examples:
The last one is Cmin Maj7. Cubase uses j7 label for major 7th.
And this is what Dorico gets when the above chords are dropped into it:
As you can see, it got only Cmin7 and Cm6 (add9) right, everything else was misinterpreted. Cmin (add11) is imported as Cmin11, Cmin (add9, add11) as Cmin9, Cmin13 as Cm7 and Cmin Maj7 as plain Cmin.
Another issue is with importing enharmonic chords . Cubase tries to automatically infer from the context whether, for example, G# is G# or Ab and it’s terribly bad at it. Luckily, it allows us to override its decision by choosing # or b manually in most cases (we unfortunately can’t have Cb, Fb, B# or E# in the Chord Track, but those are shown correctly in the Key Editor when its scale assistant is set to follow the chord track). However, Dorico always gets Cubase’s automatic decision. If Cubase wrongly decides that the chord is Ab and we change it to G#, Dorico will still get Ab even though Cubase shows G# after our change.
I am not sure if the above issues are partially or totally on the Cubase side, but it certainly wouldn’t hurt if Cubase gets more music theory aware while being made interoperable or integrated with Dorico…