Hi - not sure if this is a Cubase (13) or Dorico (6) problem, but when I export a musicxml and import it to Dorico 6, only the first 1/4 of the piece shows. All events are selected in Cubase (there’s only 2 instruments with one event each) and the whole piece is visible in the score editor when I export. however, after 37 bars, the render in Dorico stops.
If I export a MIDI file, it does all show, but for other reasons I need the musicXML to work in Dorico.
Can anyone please help with this?
Hi - I know what someone is going to ask you, in trying to help - and that’s to zip up and attach the MusicXML file you’ve exported from Cubase (if that’s an option, i.e. posting work on a public forum, etc…), so it can be scrutinised.
FWIW - I might say, that this may always be something of an issue coming from Cubase 13, because it hasn’t received nearly as much attention in this area (MusicXML export) as C14 has, with it’s all-new Score Editor based on the Dorico engine.
If you can be bothered, here’s a little experiment you could try when you have time… Download a free trial of C14 Pro and install and run that.. (it’ll live happily alongside your C13 install and won’t disrupt it in any way). Now, load your C13 project and conduct a fresh experiment from there.
Of course, it may be that it too shows some anomalies and if so, I’d again suggest you zip up and attach that MusicXML file for investigation. At least you’ll be further along the road to nailing down what’s occuring here…
Anyway, good luck.!
Basson Duet.xml (810.5 KB)
Thank you - here it is. It 's very rudimentary, but it seems to fully show the first 37 bars (out of about 150). Interestingly, it catches the time signatures for most of the rest, but wihout any content. It’s strange because it’s all on one event per track, so there’s nothing that isn’t highlighted.
I’ve never had this issue before, so downloading Cubase 14 may or may not work. If it doesn’t, I used up my free trial of it when I don’t need to. if it does, then I’m trapped into paying to upgrade for something that is actually a feature of the version I have… So, I’m really hoping this can be resolved here if possible.
Hi @guy500,
importing the xml in Cubase 14 I have the same result.
I opened the xml in Musescore (that is more forgiving for errors in the xml) and all music appears (with strange tuplets, thought*).
You may want to check the quantisation of that bar in Cubase, before re-exporting your XML file.
Anyway, after exporting the xml from MS and reimporting into Dorico, all music appears
Dorico file:
Basson Duet from MS.dorico (1.7 MB)
(*)
Dorico’s problems importing XML from other source programs may be at issue here. (Tuplets seem to be tough.) What does measure 39 (for example) look like in Cubase’s score editor, and what does that measure (for example) look like in Dorico when resolved from a MIDI import?
Hi - the bar looks exactly the same in cubase as it did in Christian’s MuseScore, BUT - looking again at what Dorico rendered for me from the xml, it looks like that’s the bar that “broke” the import somehow. It doesn’t display fully, and no notes appear after it.
Unfortunately, when I try to install Musescore, I’m not able to (something about a .net framework, which I’m definitely not going to try and play around with…).
If you’re able to consider updating to Cubase 14, you would have the option of saving a Dorico project directly from the Cubase Score Editor, which would guarantee identical appearance when opened in Dorico.
But, Christian, you’ve actually solved this for me inadvertently. If I change these 2 bars in Cubase from a 7/8 and a 5/8 to 2 x 3/4 (which is actually a much better choice anyway), the triplets in the bass display properly without a break in the last one, and now the amended file opens in full in Dorico.
So, thank you!!
It does, however, still say that the XML validation has failed, with the following message. Do you know what it means? “ERROR - Element ‘beam’: [facet ‘enumeration’] The value ‘’ is not an element of the set {‘begin’, ‘continue’, ‘end’, ‘forward hook’, ‘backward hook’}.
At line 11988 of file”
You can ignore that XML validation message.
I’ve also found that tuplets are usually the issue, preventing any subsequent music from being imported.
And as you figured out, changing the notation at exactly that place in the source application usually solves it. Even if one were to simply delete those notes and recreate them in Dorico later.
