lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: line breaks and broken beams


From: Carl Sorensen
Subject: Re: line breaks and broken beams
Date: Tue, 27 Oct 2009 20:27:52 -0600



On 10/27/09 3:01 PM, "Joe Neeman" <address@hidden> wrote:

> On Tue, 2009-10-27 at 12:06 -0700, Patrick McCarty wrote:
>> On 2009-10-27, Joe Neeman wrote:
>>> On Tue, 2009-10-27 at 01:54 -0700, Patrick McCarty wrote:
>> 
>>> It should just be a matter of setting breakable to ##t by default in the
>>> Beam grob.
>> 
>> Oops, thanks for catching that.  However, I found a comment in
>> ly/declarations-init.ly:
>> 
>> %% FIXME
>> %% should also set \override Beam #'breakable, but how to do it
>> %% "portably"? (ie. also working with lyric sections)
>> %%
>> %% try \once \override Score.Beam #'breakable = ##t
>> 
>> 
>> A real solution sounds more complicated, in other words.
> 
> Can you try to figure out what the problem is with lyrics? That is, what
> happens for properly engraved scores and what happens in lilypond if you
> set Beam #'breakable to ##t and whether the problem could be solved by
> adding unbreakable-spanner-interface to LyricExtender or LyricHyphen
> (see Spanner_break_forbid_engraver).

Isn't the problem that beams create melismata in vocal music, and you don't
want to have a line break in the middle of a melisma?

So for vocal music with beams indicating melismata, no breaking at a beam
makes sense.  Perhaps not so much for instrumental music.


Carl





reply via email to

[Prev in Thread] Current Thread [Next in Thread]