On Sunday 22 January 2006 22.44, Christian Hitz wrote: > Am 22.01.2006 um 21:56 schrieb Graham Percival: > > On 22-Jan-06, at 7:57 AM, Christian Hitz wrote: > >> in case a hairpin dynamic happens during a line break and ends on > >> the first note after the line break, it is only drawn up to the > >> line break. > > > > Not a bug; it's a feature! :) > > > > There should be an internal property you can turn on/off to draw > > the end on the beginning of the next line. I complained about this > > because IMO they look terribly ugly. I should have documented this > > property, though... I'll fix the docs later today. Before that > > happens, check the Internals documentation about Hairpins to see > > what it is. > > (\override Score.Hairpin #'after-line-breaking = ##t) turns on the > (one-note) cresc/decresc on the next line. > > However, I'm not sure that this behaviour of omitting the short ends > of the hairpins as a default is a good idea. With the crescendo, the > performer has no way of knowing that it should continue for another > note, and the open decrescendo looks awkward too.
I agree, especially with the decrescendo point. I'll let the bug stay in the cvs repository. -- Erik Sandberg Maintainer of the Lilypond bug CVS archive, http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/ http://lilypond.org/bugs/v2.7/ _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
