#376 tremolo beams can collide with notes

[Anonymous]

Originally created by: *anonymous

Originally created by: gpermus@gmail.com

\version "2.11.26"
\paper{ ragged-right=##t }
{
    \clef bass
    % Workaround
    % \override Beam #'positions = #'(-2 . -2)
    d'16:32 g: b: d': a4 a a
}

[Google Importer]

Originally posted by: pnorcks@gmail.com

There is no collision with 2.12.1; see the attached image.

Can anyone produce an example where a collision occurs?

[Google Importer]

Originally posted by: n.putt... (code.google.com)@gmail.com

There's no collision with 2.11.26 either; it looks exactly the same as 2.13.1 to me.

The default beams are possibly too short, but overriding #'positions doesn't change
the positions of the tremolos within staff spaces.  Optically, they're closer to the
line nearest the heads, but this appears to be necessary for consistency in the gaps
between beams.

[Google Importer]

Originally posted by: percival.music.ca@gmail.com

Hmm.  I think I was hoping that the entire beam would be moved a staff space lower
... the tremolo beam still looks awfully close to the second note to me.

Not a Medium item, though.

Labels: -Priority-Medium Priority-Postponed
Owner: ---

[Google Importer]

Originally posted by: percival.music.ca@gmail.com

(No comment was entered for this change.)

Labels: -type-Collision Type-Ugly

[Google Importer]

Originally posted by: mts... (code.google.com)@gmail.com

Can someone get evidence for this? Making the beam lower if there are tremoli is doable but I'd need to see what traditionally engraved scores look like. Vivaldi scores should have stuff that resembles this.

[Google Importer]

Originally posted by: PhilEHol...@googlemail.com

From reading Gould (and assuming we regard this as Gospel), then we're getting tremolos wrong anyway.  I had a vague recollection about discussing this and found Issue 1735 - you may want to look there.  Anyway, prior to this I've scanned the book and put an extract at http://philholmes.net/lilypond/typography/tremolos.htm.  Let me know if you still want it there - think it's probably too much of a copy to leave there long.

[Phil Holmes]

This bug no longer occurs with the current development version - it was fixed sometime between 19.23 and 19.28.