Skip to content
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

Parse harmony (chord symbols) from MusicXML files #83

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

maximoskp
Copy link

@maximoskp maximoskp commented Nov 29, 2024

Hi!

I made a version that produces a Harmony field in Track objects. Harmony includes an array of objects of a new class that I named ChordSymbol.

An "intermediate" class ChordSymbolParses is used in utils.py that extract all the relevant MusicXML information for chords ("harmony" tag). This feeds the ChordSymbol objects with several information, including an mir_eval-compatible chord representation.

Therefore, this version requires mir_eval - specifically, a version of mir_eval that fixes a "bug" that prevented encoding some chord types. This version of mir_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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant