I bought competitive crossgrade a month ago, lost 150 but that is just money that comes and goes.
But I wonder about a specific issue: is it musicXML or DOrico problem?
I attach 2 images. In Finale file there is a V2 entering mid-measure and V1 having a triplet at the same time. (All in Layer 1 in Finale.) Beyond that point there are no notes in Dorico file. The good thing is that this helps to find the issue fast. But the Q stays: is it something that could be improved/changed in Dorico or is it a shortcoming of MusicXML format?
Original in Finale:
I talked to the tuplet in question.
“Oh Tuplet, are you three quarters in the time of two?”
“Yes, my son, I am. Go in peace” answered the Tuplet.
I would expect, since MusicXML was based on the Finale file format from the start, that it can encode these old-fashioned V2 entries somehow, and it is just a matter of the importing software correctly interpreting the XML. But that is a guess.
If you can still run Finale, just delete the offending tuplet (add a text comment to remind you what you did) and try again. Then add back the tuplet in Dorico.
Yes, it affects us all. But it is an issue about how a bunch of different programs create and interpret MusicXML format documents. I don’t think it is easy to resolve.
Did you find a solution other than the one offered by @Janus and @MarcLarcher? If so, care to share? (Hope I didn’t miss it above if you spelled it out.)
Sorry for being unclear.
“Solved it for myself” meant the stalinist approach- no person, no problem. Same with this- if one annihilates the music that causes the problem then there is no issue.
But what if there are 80 similar places in a composition? Delete them all and re-enter in Dorico would be possible but the reason for opening this thread was that maybe the conversion issue could solved otherwise. This issue could be serious especially now that hordes of finalists are about to enter the conversion process. I myself became a convert a month ago
I agree this tuplet issue can turn into a major problem in some files (and probably never really bother hundreds of users…) that I would like to see solved one way or another…