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

Implement accidental-mark elements for trill imports from MusicXML #19764

Open
craigsapp opened this issue Oct 18, 2023 · 1 comment
Open

Implement accidental-mark elements for trill imports from MusicXML #19764

craigsapp opened this issue Oct 18, 2023 · 1 comment
Assignees
Labels
feature request Used to suggest improvements or new capabilities MusicXML P2 Priority: Medium

Comments

@craigsapp
Copy link

Your idea

When importing MusicXML data containing trills with accidentals, the accidentals are ignored. Trill accidentals are encoded using <accidental-mark> as a sibling element of <trill-mark>.

See MusicXML documentation example related to this issue: https://www.w3.org/2021/06/musicxml40/musicxml-reference/examples/accidental-mark-element-ornament

Problem to be solved

Here is an example:

Click to view MusicXML data for the following rendering in Musescore 4.0.1
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE score-partwise PUBLIC "-//Recordare//DTD MusicXML 3.1 Partwise//EN" "http://www.musicxml.org/dtds/partwise.dtd">
<score-partwise version="3.1">
  <work>
    <work-title>Trill + Accidental</work-title>
    <!-- https://www.w3.org/2021/06/musicxml40/musicxml-reference/examples/accidental-mark-element-ornament -->
  </work>
  <part-list>
    <score-part id="P1">
      <part-name/>
    </score-part>
  </part-list>
  <part id="P1">
    <measure number="1">
      <attributes>
        <divisions>4</divisions>
        <key number="1">
          <fifths>0</fifths>
          <mode>none</mode>
        </key>
        <staves>1</staves>
        <clef number="1">
          <sign>G</sign>
          <line>2</line>
        </clef>
      </attributes>
      <note>
        <pitch>
          <step>G</step>
          <octave>4</octave>
        </pitch>
        <duration>16</duration>
        <voice>1</voice>
        <type>whole</type>
        <stem>up</stem>
      </note>
    </measure>
    <measure number="2">
      <attributes>
        <divisions>4</divisions>
      </attributes>
      <note>
        <pitch>
          <step>G</step>
          <octave>4</octave>
        </pitch>
        <duration>16</duration>
        <voice>1</voice>
        <type>whole</type>
        <stem>up</stem>
        <notations>
          <ornaments>
            <trill-mark/>
            <accidental-mark placement="above">flat</accidental-mark>
          </ornaments>
        </notations>
      </note>
    </measure>
    <measure number="3">
      <attributes>
        <divisions>4</divisions>
      </attributes>
      <note>
        <pitch>
          <step>E</step>
          <octave>4</octave>
        </pitch>
        <duration>16</duration>
        <voice>1</voice>
        <type>whole</type>
        <stem>up</stem>
        <notations>
          <ornaments>
            <trill-mark/>
            <accidental-mark placement="above">sharp</accidental-mark>
          </ornaments>
        </notations>
      </note>
      <barline location="right">
        <bar-style>regular</bar-style>
      </barline>
    </measure>
  </part>
</score-partwise>
Screenshot 2023-10-18 at 6 24 25 AM

There should be a flat above the trill in the second measure (to create a minor-second trill), and a sharp above the trill in the third measure (to create a major-second trill).

Prior art

Here is an example rendering from Dorico 4.0.31 for the same MusicXML example given in the previous section:

Screenshot 2023-10-18 at 6 28 34 AM

In this case the <accidental-mark> is correctly being read for the <trill-mark>.

Additional context

No response

@muse-bot muse-bot added the feature request Used to suggest improvements or new capabilities label Oct 18, 2023
@bkunda bkunda added the P2 Priority: Medium label Oct 20, 2023
@jrbowden
Copy link

This is also a problem when exporting to MusicXML, the accidentals on ornaments are lost.
This is of importance for example, for translating to braille. The XML does not contain the accidental, therefore neither does the braille.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Used to suggest improvements or new capabilities MusicXML P2 Priority: Medium
Projects
None yet
Development

No branches or pull requests

6 participants