-
Notifications
You must be signed in to change notification settings - Fork 58
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
'tacet al fine' multi-measure rests #557
Comments
This is a very good idea. But I wonder if Tacet al Fine is also a semantic idea that should also be encoded, to indicate to an editor that if the number of measures changes in the future the assumption is that they are tacet. I want to double check the spec to make sure there's not another way to specify text to go with multimeasure rests and to think through the possibility of displaying a number and also alternative text. |
Yes, I think so, but adjusting the number of measures is something that an editor has to do, no? Would this have any consequences in the MusicXML encoding?
An alternative would be to add a |
Ah, now I got it 🙂 What about allowing value 0 for |
A value of 0 doesn't seem like a good idea. It could confuse the heck out of existing apps. New attributes or elements added to support this would just be ignored, so they wouldn't cause problems. I think we need the actual number of tacet measures in the element content, but figure out a good way to specify text instead of a number. |
My initial suggestion would be to add an optional |
Yeah, your concerns regarding my suggestion for value zero are valid. To address Myke's 'semantic' argument I could imagine to have an attribute
Sounds good. |
Gould writes the following in her book Behind Bars: “When a player has finished playing for the remainder of a piece, this is indicated tacet al fine. For orientation in rehearsal, place the instruction after a subsequent rehearsal mark:”
As far as I can see, this is not supported yet in MusicXML. To do that I suggest that the
<multiple-rest>
element gets a new attributetext
, say, which replaces the normally displayed number of bars (but see also issue #537 regarding attributes that control the appearance of multi-measure elements).Such a feature would benefit from the fact that
<multiple-rest>
is a transformator function (as are all children of<measure-style>
): it converts – at least theoretically, if you follow the documentation verbatim – the specified number of measures to a single multi-measure object, ignoring any time signature changes.The text was updated successfully, but these errors were encountered: