Parse harmony (chord symbols) from MusicXML files #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I made a version that produces a
Harmony
field inTrack
objects.Harmony
includes an array of objects of a new class that I namedChordSymbol
.An "intermediate" class
ChordSymbolParses
is used inutils.py
that extract all the relevant MusicXML information for chords ("harmony" tag). This feeds theChordSymbol
objects with several information, including anmir_eval
-compatible chord representation.Therefore, this version requires
mir_eval
- specifically, a version ofmir_eval
that fixes a "bug" that prevented encoding some chord types. This version ofmir_eval
can be found here:https://github.com/maximoskp/mir_eval/tree/allchordtypes
I've created a pull request for that recently in
mir_eval
, so it will possibly be available in the main branch of ```mir_eval`` soon.I know that I didn't follow the high code and testing standards of the
muspy
repository, so I will be clad to receive any feedback and try again. Needless to say, you can do whatever you want with the current version of the code that I submit through this pull request. Thanks!