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

[MusicXML] Add missing Gould arrow quartertone accidentals #6263

Merged
merged 1 commit into from
Jul 7, 2020

Conversation

rettinghaus
Copy link
Contributor

This PR is a simple addition to allow import/export of the added Gould arrow quartertone accidentals in MusicXML 3.1.

  • I signed CLA
  • I made sure the code in the PR follows the coding rules
  • I made sure the code compiles on my machine
  • I made sure there are no unnecessary changes in the code
  • I made sure the title of the PR reflects the core meaning of the issue you are solving
  • I made sure the commit message(s) contain a description and answer the question "Why do those changes fix that particular issue?" or "Why are those changes really necessary as improvements?"
  • I made sure the commit message title starts with "fix #424242:" if there is a related issue
  • I created the test (mtest, vtest, script test) to verify the changes I made

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jun 26, 2020

Looks good to me. @lvinken , what do you think?
Can you please have a look at #6182, whether that should enable the added accidentals also for MusicXML?

I think you should rebase this to the 3.x branch though. As far as I can tell you can do that here on GitHub, via the Edit button

Not sure what's up with Travis, seems to have hit a timeout, but the build and all the tests passed.
Not sure where the GitHub tests went. Seems we're having an issue with out build enironment, @anatoly-os ?

@rettinghaus rettinghaus changed the base branch from 3.5rc to 3.x June 26, 2020 10:15
@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jun 26, 2020

case AccidentalType::SHARP2_ARROW_DOWN: s = "double-sharp-down"; break;
case AccidentalType::SHARP2_ARROW_UP: s = "double-sharp-up"; break;
case AccidentalType::FLAT2_ARROW_DOWN: s = "flat-flat-down"; break;
case AccidentalType::FLAT2_ARROW_UP: s = "flat-flat-up"; break;
case AccidentalType::SORI: s = "sori"; break;
case AccidentalType::KORON: s = "koron"; break;
default:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the default should be s = "other"? While keeping the qDebug() message, I guess.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think so. The other value is supposed to go together with the @smuflattribute.
See the answer bei @mdgood here: w3c/musicxml#263

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, then let's just add that?
Probably something for a different PR though

map["double-sharp-down"] = AccidentalType::SHARP2_ARROW_DOWN;
map["double-sharp-up"] = AccidentalType::SHARP2_ARROW_UP;
map["flat-flat-down"] = AccidentalType::FLAT2_ARROW_DOWN;
map["flat-flat-up"] = AccidentalType::FLAT2_ARROW_UP;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure though how or whether to handle an import of "other". Seems the current defaulting to AccidentalType::NONE alone with a qDebug() message is reasonable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned above, handling "other" would only make sense, if we'd check the @smufl attribute. So, for now, I think it's ok to ignore "other".

Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 26, 2020
and default to "other" for all otherwise unknown accidentals.

This change/commit will cause a merge conflict with musescore#6263
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 26, 2020
This change/commit will cause a merge conflict with musescore#6263
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 26, 2020
and fix some MusicXML todos

This change/commit will cause a merge conflict with musescore#6263
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 27, 2020
and fix some MusicXML todos

This change/commit will cause a merge conflict with musescore#6263
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 27, 2020
and fix some MusicXML todos

This change/commit will cause a merge conflict with musescore#6263
@lvinken
Copy link
Contributor

lvinken commented Jun 27, 2020

Looks OK to me. Note that this should go in 3.x and master, I am not quite sure if automatic sync from 3.x to master is in place.

@Jojo-Schmitz
Copy link
Contributor

Thanks. There is no automatic sync between 3.x and master

Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 27, 2020
and fix some MusicXML todos

This change/commit will cause a merge conflict with musescore#6263
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 27, 2020
and fix some MusicXML todos

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 28, 2020
and fix some MusicXML todos and complete the accifental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 28, 2020
and fix some MusicXML todos and complete the accifental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jun 28, 2020
and fix some MusicXML todos and complete the accifental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
@anatoly-os anatoly-os merged commit 5229e68 into musescore:3.x Jul 7, 2020
anatoly-os added a commit that referenced this pull request Jul 7, 2020
[MusicXML] Add missing Gould arrow quartertone accidentals
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Jul 8, 2020
and fix some MusicXML todos and complete the accifental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
@rettinghaus rettinghaus deleted the dev-arrowaccid branch July 22, 2020 07:25
anatoly-os added a commit that referenced this pull request Jul 22, 2020
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Aug 27, 2020
and fix some MusicXML todos and complete the accifental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Oct 20, 2020
and fix some MusicXML todos and complete the accidental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
Jojo-Schmitz added a commit to Jojo-Schmitz/MuseScore that referenced this pull request Oct 20, 2020
and fix some MusicXML todos and complete the accidental mappings

This change/commit will cause a merge conflict with musescore#6263 (it actually
includes it completly)
vpereverzev pushed a commit that referenced this pull request Oct 22, 2020
and fix some MusicXML todos and complete the accidental mappings

This change/commit will cause a merge conflict with #6263 (it actually
includes it completly)
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

4 participants