While I agree 2.3.2 was wrong to have the slope backwards, I would also agree this seems a steeper than necessary. Maybe rests should be ignored when calculating slope. Or maybe the max should be less. BTW, the max slope unit seems wrong, 0.5 sp makes no sense. Seems it is actually 0.5, period. Or maybe it's clearer to present it as 50%.
" Format > Style > Tuplets > Max. slope to 0"
Thank you, that's really useful!
And as regards the slope of the bracket, Elaine Gould says in "Behind Bars" on page 197:
"The angle of the slant should not be too acute; match an equivalent beam slant."
I just came across an example where tuplet brackets are used, in a situation where the triplet starts with a rest followed by two repeated chords.
In this situation I think it would be much more elegant if the tuplet bracket defaulted to "horizontal", rather than introducing some slope calculated on... what? The difference in position between the rest and the repeated chord's note closest to the beam?? It's a repeated chord, so surely the bracket should be horizontal?
Comments
"wrongly" seems the wrong word...
Also please attach sample scores
I actually get this in MuseScore 2.3.2:
![triplet-2.3.2.png]( "triplet-2.3.2.png")
which is pretty bad IMHO, I like the 3.2.3 way much better
You get that in 3.2.3, if you set Format > Style > Tuplets > Max. slope to 0
Open the attached score and compare the tuplet bracket angles in MS3 with those in MS2.
See above for a workaround, should you not like this.
It is different, no doubt, but IMHO better now
While I agree 2.3.2 was wrong to have the slope backwards, I would also agree this seems a steeper than necessary. Maybe rests should be ignored when calculating slope. Or maybe the max should be less. BTW, the max slope unit seems wrong, 0.5 sp makes no sense. Seems it is actually 0.5, period. Or maybe it's clearer to present it as 50%.
To 2 bugs for the price of one then...
In reply to You get that in 3.2.3, if… by Jojo-Schmitz
" Format > Style > Tuplets > Max. slope to 0"
Thank you, that's really useful!
And as regards the slope of the bracket, Elaine Gould says in "Behind Bars" on page 197:
"The angle of the slant should not be too acute; match an equivalent beam slant."
I just came across an example where tuplet brackets are used, in a situation where the triplet starts with a rest followed by two repeated chords.
![Tuplet brackets not horizontal.png]( "Tuplet brackets not horizontal.png")
In this situation I think it would be much more elegant if the tuplet bracket defaulted to "horizontal", rather than introducing some slope calculated on... what? The difference in position between the rest and the repeated chord's note closest to the beam?? It's a repeated chord, so surely the bracket should be horizontal?
relates to #271331: [EPIC] Positioning, symbols, notation related issues
see also #120051: Tuplets: bracket max. slope values are out by a factor of 10