-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mismatch midi and musicxml scores #8
Comments
Create a minimal example that we can send to the Music21 developers.
…On Thursday, June 27, 2019, David Garfinkle ***@***.***> wrote:
indexers.notes does not return the same data running on a midi file
versus the musicxml output of that midi file as output by
music21.converter.parse(midi).write('xml')
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8?email_source=notifications&email_token=AADYFRNMEZIKXEIMSECT3UTP4S5MHA5CNFSM4H336AI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G4CLAUA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADYFRPEIBMDCE52FZ6TAG3P4S5MHANCNFSM4H336AIQ>
.
|
with test mass and found the first mismatch occurs at a tied note i think this means the bug is on our end, but there remains some thinking.. |
This bug occurs because we can arrive at a solution by calling |
todo: include the expected behaviour of finding occurrences through ties in the documentation & ask peter |
the current solution has been to ensure that the data we search over is the same from which we extract measures |
indexers.notes
does not return the same data running on a midi file versus the musicxml output of that midi file as output bymusic21.converter.parse(midi).write('xml')
The text was updated successfully, but these errors were encountered: