Tuplet Arch Feature Request
Currently, there are two options for notating tuplets: "bracket" or "none".
It has been requested to create a third option for notating tuplets. The arch as shown in the attached image. Is this possible?
I understand that this is not a popular notation approach (I much prefer the bracket) but it is still used by many people. I can find more examples if needed.
| Attachment | Size |
|---|---|
| Screen Shot 2021-02-18 at 3.08.21 PM.png | 2.45 KB |
Comments
Workaround two dotted/dashed slurs?
In reply to Workaround two dotted slurs?… by Shoichi
Yes, this is a workaround; however, it would be better to have a set option for this since this method doesn't work when doing any automation. For example, if you create "parts" the slurs automate back to the stems or something like that.
See #111626: Add option to display tuplet brackets as slurs to match historical notation
In reply to See #111626: Add option to… by Jojo-Schmitz
Jojo, other than workarounds (small white rectangle) would it be feasible to have adjustable half ties (right/left) or slurs to avoid collisions?
In reply to Jojo, other than workarounds… by Shoichi
'hanging' ties/slurs would be good for other purposes too
In reply to Jojo, other than workarounds… by Shoichi
See #318113: 'Hanging' ties/slurs
I agree. The current received wisdom of a number only behind the beam is NOT the best choice in all cases. Particularly in a jazz font, where sightreadability is the priority (or should be) having the number always as far away from the noteheads as possible is just wrong. The rule should be 'with the noteheads wherever posiible and where it isn't (because of the stave lines maybe) then elsewhere'.
In reply to I agree. The current… by rockleyhome@gm…
You can force the tuplet bracket to show even in cases where by default it won't
In reply to I agree. The current… by rockleyhome@gm…
No, that's not the rule followed by professional editors. It's true sight-readability is the goal, but that's precisely why the number is normally placed on the ste/beam side - because the stem/beam is how you read rhythm. So info relating the rhythm belongs on that side.
But, there are exceptions - basically, cases where the notes are outside the staff. In these cases, the beam is somewhere within the staff, and now you are faced with having to either place the tuplet number on the staff as well (seldom a good idea), or allowing it to be all the way on the other side of the staff. So that's the main case where professional editors will move the number ot the notehead side. Here's an example showing the three options:
I could imagine someday MuseScore implementing a rule like this, with a maximum allowed distance from the beam to the number. If placing the tuplets in the standard position leaves it too far from the beam, we could flip it to the notehead side automatically.