New style option for tuplets

• Sep 2, 2013 - 19:13

I was in need of more options for tuplet brackets and tuplet numbers positionning and there were a couple of open issues about them. So I implemented a couple of new style parameters.

shot_130902_195425.png

Vertical positioning

Maximum slope

Default 0.5 = 30° -- Between 0.1 and 1.0.
When the tuplet bracket slope goes over this value, the angle of the bracket doesn't change and the full bracket is shifted up or down.

Vertical distance from stem

Default 0.25 spaces -- Between -5 and 5 (because we can)
If the bracket is on the same side than the stem, this is the distance between the stem tip and the bracket tip.

Vertical distance from notehead

Default 0.5 spaces -- Between -5 and 5 (because we can)
If the bracket is on the same side of a notehead, or there is no stem, this is the distance between the notehead and the bracket tip.

Avoid the staves

On by default -- Off for MuseScore 1.3 scores.
If this checkbox is checked, brackets and tuplet numbers will stay out of the staves.

Horizontal positioning

Distance before the stem of the first note

Default 0.5 spaces -- Between -5 and 5
If the tuplet starts with a stem, so an down note, this is the distance between the bracket and the stem.

Distance before the head of the first note

Default 0.0 spaces -- Between -5 and 5
If the tuplet starts with a notehead, so a up note or a note without stem, this is the distance between the bracket and the notehead.

Distance after the stem of the lastnote

Default 0.5 spaces -- Between -5 and 5
If the tuplet ends with a stem, so an up note, this is the distance between the stem and the last bracket.

Distance after the head of the last note

Default 0.0 spaces -- Between -5 and 5
If the tuplet ends with a notehead , so a down note, this is the distance between the notehead and the last bracket

Feedback please

Default values are from more or less the one of Sibelius 7. Elaine Gould in "Behind Bars" disagrees (horizontal distances should be 0). I didn't check Finale, Lilypond or other software/books.
Personally, I like this defaults and I would like to avoid a sterile debate about them... I welcome any constructive feedback though.

Attachment Size
shot_130902_195425.png 15.29 KB

Comments

In reply to by chen lung

There's an awful lot of examples there and different aspects to the question. And are you sure you are using a build that incorporates these changes? Your original problem description certainly appears fixed to me - the file posted in the original report now *does* extend fully - but perhaps there's some further corner case buried within one of the responses that isn't?

When I look over the hundreds of classic hand-engraved scores as well as computer-typeset from the past few centuries I have in my collection, I see enormous variety in how tuplets are handled. So I think it is pretty much impossible to say there is one set of defaults that is "correct". And given that these are now style options - meaning you can tweak them to your hearts content and save them as your own personal defaults - I can't really see much basis for worrying about it as long as the defaults seem to be within the (rather large) range of what is historically accepted. And in all respects I can see, the new defaults are. And the choices presented are quite simple and logical.

What *is* missing for me, though, is a curved bracket option. I personally detest that option - way too easily mistaken for slurs - but there is no denying that there did exist a period in history when this style of notation was common, and MuseScore should support it for the sake of people who want that look.

Do you still have an unanswered question? Please log in first to post your question.