At 12:28 PM -0800 12/01/03, Chuck Israels wrote:
Darcy wrote:

[N.B. In jazz, bracketed triplets are always supposed to go above the
staff, so I'm kind of constrained there.  It would be convenient to put
all the triplet brackets below the staff and all the slurs above, but
jazz players aren't used to seeing triplet brackets below the staff.]


Darcy,


I have always adhered to the convention that tuplet brackets go above the notes when the stems go up or are mixed and below when the stems are all down. No one has complained (almost all of my players are jazz musicians at one level or another), and the page looks neater to me that way. Slurs crashing through tuplet brackets are not beautiful, and I'd avoid the condition when possible but, if it's the only solution, I prefer it to moving the brackets.

Chuck


Yes, that agrees with my authorities, except for Clinton Roemer, who insists on tuplets going ABOVE the passage. I am used to seeing them as you describe. However, your (and I believe, the standard) solution still puts slurs and tuplets both above the staff when stem directions are mixed, with the resultant possibility of collisions.

The Norton Manual (Heussenstamm) suggests moving bracketed tuplets below the staff to avoid collisions with slurs above, while unbracketed tuplets would stay where they are. He also suggests moving tuplet brackets to avoid collisions with dynamics, hairpins, text, or anything else. He also puts slurs generally outside tuplets where the slur lasts longer than the tuplet, and there is one notable exception where two notes of a triplet are slurred INSIDE the bracket. THere is no example given where three notes with mixed stem directions are all slurred AND there is a bracket, which I would like to see, as I write that kind of thing all the time and never know what to do about it. I would not allow a collision (not on purpose, anyway!)

Christopher
_______________________________________________
Finale mailing list
[EMAIL PROTECTED]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to