too many bugs in musicxml
hi guys,
Nice features BUTTTT the amount of bugs becomes a real problem. I can't even export to an older version as it's not a valid musicxml format... I tried to fix the xml but it takes too long... too many errors...
direction system=only-top attribute is just one example out of my head... but guys I'm now stuck. It becomes a very serious problem as sometimes I can't even save the changes as a muscore file... so I have to try to track the issue from the last save... :-(
PLEASE invest in musicxml compatibility!!!!!
thx a lot,
Comments
Musicxml has never been perfect from any software. It isn't clear just what you are using xml format for. There are three formats to use in export. Please provide a bit more information.
In reply to Musicxml has never been… by bobjp
thx for the prompt reply. i use it to export to another notation app/analysis tools.
i tried all the three format and got the same issue.
I guess that you do have some devop tests for this scenario.
Try to use a score with some drums and some time signature changes.
It's critical as users must have the confidence that they are not prisoners of a specific app :-)
In reply to Musicxml has never been… by bobjp
Incomplete measure: Part score: Flute, measure 79, staff 1. Found: 15/16. Expected: 3/4.
In reply to Incomplete measure: Part… by selasarig3
Reset the part(s)
In reply to Reset the part(s) by Jojo-Schmitz
thx! i tried these reset options (see attachment)... still the same issue. i've also deleted the parts that i have for each inst. as well just in case
In reply to thx! i tried these reset… by selasarig3
ahh, you mean in the part's list.. ok it worked THX!!!. Why is that? parts are out of sync with the main score and before saving there's a validation check? BTW - it would be great to ge a bit more description when such an error occurs so one can somehow find a bypass...