I have a musicxml file from Finale which is not fully loaded on Dorico. The first screenshot is the Finale Window. In Dorico, the measures appear empty after bar 64, although some measure attached items are still loaded. Please, how may I have the file correctly loaded in Dorico? I work with a MacBookPro MacOS 15.3.1.
There will be an error in the Finale XML file that Dorico cannot understand (usually caused by tuplet calculations not adding up, or errors in bar lengths)
1 Like
How do I fix it? Is there any app which can fix such miscalculations? It is strange that a machine-made file would contain such errors. Certainly a professional software should treat properly such āerrorsā.
Try deleting the ornaments in bar 65 in Finale and re-export.
Just a guess though. They might contain some hidden playback.
Jesper
I deleted the tuplet at bar 64 before re-exporting it. Strange way to work around. I hope the developers can fix this issue.
The problem is how Finales creates the xml file, not how Dorico imports it.
2 Likes
I understand the xml file may have some problems, but a professional user relies on a software that can properly deal with minor errors. A software would be expected to mark and comment such isolated measures and thus saving major parts of the file.
I experienced the same with a MusicXML file from PlayScore 2. I was frustrated at first, but then I took the trouble upon me to look at the file with an XML editor and found some weird entries in the measure where the import stopped. Nothing really wongly formed like incomplete XML tags (which DORICO reports correctly), rather inconsistent note lengths that didnāt add up in a sensical way. I erased the strange looking entries and everything went smoothly.
I can get riled up myself when I have to deal with apps that donāt deliver on their promises. In this case, knowing a bit about software development myself, Iām personally think that itās impossible for the DORICO team to write an import parser code that accounts for ALL possible MusicXML glitches in advance.
After all, music is a complex language and music notation is multidimensional and context dependent in ways that we as prolific readers who āhearā the notation sometimes forget. Writing consistent MusicXML (on PlayScoreās or Finaleās side) or accounting for all possible errors (on Doricoās side) and thus, on both sides, safely transferring notational code in a way that mirrors the composerās intent is way more complex than one might think at first.
So, while I think itās a good idea to send in a bug report, I wouldnāt realistically expect 100% accuracy in the forseeable future.