On Wed, 2009-10-28 at 21:54 +0100, Nicolas Sceaux wrote:
> Le 28 oct. 09 à 08:37, David Kastrup a écrit :
>
> > Carl Sorensen writes:
> >
> >> 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?
> >
> > Baroque mel
Le 28 oct. 09 à 08:37, David Kastrup a écrit :
Carl Sorensen writes:
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?
Baroque melisme can go on for lines. Do we have a way to discourage
breaks but not complete
Carl Sorensen writes:
> 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?
Baroque melisme can go on for lines. Do we have a way to discourage
breaks but not completely disallow them?
--
David Kastrup
> 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?
Hmm. How often does this happen in real scores? I think that in most
circumstances good (and thus flexible) spacing is much more important,
and a user should loc
On 10/27/09 3:01 PM, "Joe Neeman" 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.
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:
> > > On 2009-09-27, Werner LEMBERG wrote:
> > > >
> > > > >> What's the reason that line breaks are by default forbidden if
> > > > >> there i
On 2009-10-27, Joe Neeman wrote:
> On Tue, 2009-10-27 at 01:54 -0700, Patrick McCarty wrote:
> > On 2009-09-27, Werner LEMBERG wrote:
> > >
> > > >> What's the reason that line breaks are by default forbidden if
> > > >> there is a broken beam crossing the bar line, and that you have to
> > > >> s
On Tue, 2009-10-27 at 01:54 -0700, Patrick McCarty wrote:
> On 2009-09-27, Werner LEMBERG wrote:
> >
> > >> What's the reason that line breaks are by default forbidden if
> > >> there is a broken beam crossing the bar line, and that you have to
> > >> set the `breakable' flag manually to override
On 2009-10-27, Patrick McCarty wrote:
> On 2009-09-27, Werner LEMBERG wrote:
> >
> > >> What's the reason that line breaks are by default forbidden if
> > >> there is a broken beam crossing the bar line, and that you have to
> > >> set the `breakable' flag manually to override it?
> > >>
> > >> BT
On 2009-09-27, Werner LEMBERG wrote:
>
> >> What's the reason that line breaks are by default forbidden if
> >> there is a broken beam crossing the bar line, and that you have to
> >> set the `breakable' flag manually to override it?
> >>
> >> BTW, it is very unpleasant that lilypond doesn't emit
Ping!
Werner
==
From: Werner LEMBERG
Subject: Re: line breaks and broken beams
Date: Sun, 27 Sep 2009 16:08:31 +0200 (CEST)
>
>>> What's the reason that line breaks are by default forbidden if
>
Werner LEMBERG writes:
>>> What's the reason that line breaks are by default forbidden if
>>> there is a broken beam crossing the bar line, and that you have to
>>> set the `breakable' flag manually to override it?
>>>
>>> BTW, it is very unpleasant that lilypond doesn't emit any kind of
>>> warn
>> What's the reason that line breaks are by default forbidden if
>> there is a broken beam crossing the bar line, and that you have to
>> set the `breakable' flag manually to override it?
>>
>> BTW, it is very unpleasant that lilypond doesn't emit any kind of
>> warning if it produces an overlong
+1.
(I've always felt this way, too.)
Trevor (B).
On Thu, Sep 24, 2009 at 5:44 PM, Werner LEMBERG wrote:
>
> What's the reason that line breaks are by default forbidden if there
> is a broken beam crossing the bar line, and that you have to set the
> `breakable' flag manually to override it
What's the reason that line breaks are by default forbidden if there
is a broken beam crossing the bar line, and that you have to set the
`breakable' flag manually to override it?
BTW, it is very unpleasant that lilypond doesn't emit any kind of
warning if it produces an overlong staff caused by
15 matches
Mail list logo
