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

fix #53936: incomplete MusicXML text for 7sus4 #1923

Merged
merged 1 commit into from Apr 7, 2015

Conversation

MarcSabatella
Copy link
Contributor

Previously, for 7sus4, we exported kind of suspended-fourth, text of "sus4", and the 7 was a degree tag with no specific text. We import this just fine, but other applications apparently would interpret this as "sus4add9". So on advice of Michael Good, we now export the kind text as "7sus4", and explicitly set the degree text for the 7 to "". Similarly for 9sus4 etc.

This PR also fixes a chord parsing issue where we would try to parse b913 as b 913, rather than b9 13, potentially leading to a crash.

@lasconic
Copy link
Contributor

lasconic commented Apr 7, 2015

Regarding the sus chord, I guess it would make sense to have a test case that read MusicXML, write it and compare with the reference one for chord symbols no?

lasconic added a commit that referenced this pull request Apr 7, 2015
fix #53936: incomplete MusicXML text for 7sus4
@lasconic lasconic merged commit e3d51b9 into musescore:master Apr 7, 2015
@MarcSabatella
Copy link
Contributor Author

Seems like it. The import changes are done now?

@lasconic
Copy link
Contributor

lasconic commented Apr 8, 2015

Mostly. You can do a PR and mention Leon in it.

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.

None yet

2 participants