You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a valid interpretation? It doesn't really make sense to have <rest> combined with <notehead> – except for the possible side effect of the parentheses attribute.
To me it is not clear at all why <notehead> and <accidental> both have a parentheses attribute while <rest> has not. It feels unbalanced.
Additionally, using <level> doesn't feel right for some situations. As a composer, I have actually parenthesized rests by myself, which essentially means that the parentheses are not something added later by the editor... On the other hand, I can understand that there are so many different MusicXML elements that adding a parentheses attribute to all of them might not be prudent.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In a very old MusicXML test file I found the following to produce a rest in parentheses:
Is this a valid interpretation? It doesn't really make sense to have
<rest>
combined with<notehead>
– except for the possible side effect of theparentheses
attribute.To me it is not clear at all why
<notehead>
and<accidental>
both have aparentheses
attribute while<rest>
has not. It feels unbalanced.Additionally, using
<level>
doesn't feel right for some situations. As a composer, I have actually parenthesized rests by myself, which essentially means that the parentheses are not something added later by the editor... On the other hand, I can understand that there are so many different MusicXML elements that adding aparentheses
attribute to all of them might not be prudent.Beta Was this translation helpful? Give feedback.
All reactions