You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Surfaced by the round-trip failure classifier (#211, PR #217).
What
51 files are classified "reorder-only" (category C): the output contains exactly the same elements as the input (the tag multiset is identical, nothing dropped or added) but in a different order. Every one of them diverges at the same place:
/score-partwise/identification/encoding/software
So the api is writing the children of <encoding> (software, encoding-date, supports, ...) in a different order than the source file. The music is fully intact; the file just isn't a byte-faithful copy.
Fix options
Make the api writer emit <encoding> children in MusicXML schema order, or
Surfaced by the round-trip failure classifier (#211, PR #217).
What
51 files are classified "reorder-only" (category C): the output contains exactly the same elements as the input (the tag multiset is identical, nothing dropped or added) but in a different order. Every one of them diverges at the same place:
So the api is writing the children of
<encoding>(software, encoding-date, supports, ...) in a different order than the source file. The music is fully intact; the file just isn't a byte-faithful copy.Fix options
<encoding>children in MusicXML schema order, orOption 1 is the more faithful fix; option 2 is the cheaper one if encoding order is deemed insignificant.
Severity
Low — content is preserved, only ordering differs. But it currently blocks 51 files from the strict pass-list.
Repro
References