Hi Karim and OM Hivemind,
I have had a good time subdividing a rhythm in a VOICE object in OM (using integers in the key commands for the POLY editor.)
Unfortunately, twice now, this seems to have corrupted the file and made it unrecognizable to notation software. Please see attached.
The original file before I do this is uncorrupted.
I am still running OM 7.6. Is there a semiurgent workaround for this?
Much Appreciated!
Brandon
Corrupted_Voices.omp (159.8 KB)
Dear Brandon,
The exact term is not corrupted. The problem IS the musicxml export WHEN you have nested tuplets. Some engravers that you mention don’t support this. This has been a problem, since the musicxml standard which apparently isn’t a standard. Each engraver parses it at its convenience. We cannot support ALL third parties commercial engravers format.
So, our advise is to use our omlily library and use lilypond for engraving music. This will avoids such problems.
Furthermore, not having Dorico, i cannot test this. Maybe if you can give us some feedback about what’s wrong with the “corrupted” nature of the rendering, we might find a way to fix it. And please try to keep your example a MWE one.
Merry Xmas
Karim
Dear rc,
Yes it opens in musescore, but all nested tuplets will be transformed into simple ones.
I don’t think that’s what Brandon expects.
K
Ok, so i thought corrupted = unable to open 
sorry for the confusion!
rc
Yes i must admit Brandon’s message is somehow confusing. The trouble comes from Musescore’s xml parser. And as I remember, it doesn’t allow nested tuplets. As for Dorico, i can’t say, don’t have Dorico. I am on Linux and i use mainly Lilypond.
k
Dear Karim and rc,
Thank you for your messages! I have reduced to MWE and attach here.
I recognize this could certainly be an issue with Dorico XML decoding. When I tried to open in MuseScore there was a window that said the file was corrupted before opening as rc did.
For the time being I have continued on the project by “manually” subdividing the rhythms in Dorico. I would be open to using Lilypond in future works but given it seems Dorico is the “emerging standard” (whatever that means!), with other features that I do need, I thought it might be important to sort these issues out there, too.
If you can confirm this is not at all an issue with OM I can post on Dorico’s blog for future investigation on their end.
Best Regards and Happy New Year!
Brandon
Glitch.dorico (535.2 KB)
Glitch.xml (28.5 KB)
Dear Brandon,
First of all, happy new year to you too.
Now for this:
This means this is a statement from promo guys of Dorico, and it doesn’t mean anything.
Some people are still using Sibelius, others something else. This depends really on the the choice of the user’s end. Personally i use Lilypond and very glad to do so, meaning it satisfies my needs in typesetting.
Now, for the confirmation part, sorry I can’t confirm anything related to Dorico, since I don’t have Dorico. But you can! Here what you should try to do:
create a measure in dorico with an embeded tuplet like so:
Then export it in musicxml
import it again in Dorico.
If this works, just send me the xml exported file from Dorico to see what are THEIR standards concerning embeded tuplets.
If you do the same using Musescore, you will see that musescore althought exporting embeded tuplets, doesn’t know how to import it again.
Best
K
