Open jacobtylerwalls opened 3 years ago
Good problem diagnosis. Because it fixes an existing bug, it can go in the v7 release series also (milestone is still fine) -- no one is counting on this behavior.
Maybe we want a recurse(voicesFirst=True)
argument that will match by id, and sort by whatever order those id's were first encountered. Linking a related issue from m21j.
Or, before falling back to id's and order of encountering them, we implement the VoiceSpanner idea from discussion on #915 and order it by order of the VoiceSpanners in the stream.
In terms of voices-first recursion, that would also solve this wrinkle (add test case when solved -- makeAccidentals created another F# even though tied):
music21 version dev
Problem summary stripTies() should bridge voices between measures rather than just flattening entire parts. Undesired deletions can happen. This was a known issue; we haven't made this worse recently AFAICT.
Steps to reproduce
Expected vs. actual behavior Before stripping ties
After stripping ties (inappropriate deletion)
More information We could match voices by
.id
or by sequence in the measure container. Matching by sequence will be easier after having a.sequence
attribute in #915.