lilypond-user
[Top][All Lists]
Advanced

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

Re: Acciaccaturas and slashed stems


From: David Kastrup
Subject: Re: Acciaccaturas and slashed stems
Date: Thu, 19 Sep 2013 19:25:01 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Gilberto Agostinho <address@hidden> writes:

> Well, a single grace note upon a single note cannot be beamed since there is
> nothing to beam it to.

Tell that to LilyPond:

{ c'8[] }

is valid music.

> But I imagine you meant a single unbeamed note in among other grace
> notes in a complex situation, as in the piano sonata example you sent,
> right? So, about it: you are totally right on this one, in this case
> the autobeaming wouldn't work out well and the user would need to make
> manual adjustments. But my point is: isn't this is a complex example
> and the by far the most common is to have same duration grace notes?
> Also, the user who would type such passage with LilyPond still would
> need to manually set the beams, so actually it would make little
> difference for him if autoBeam was on.

You are presuming that LilyPond has some greedy "autoBeam" setting which
will be broken by any manual beaming instruction and will exclude single
notes.  Or that it should have that.

> It is not like I am proposing to make these complex examples
> impossible, I just believe that they are the minority and thus it
> would be more practical for the regular user to have all grace notes
> beamed together.

So how do you propose the minority should be input?

You are calling out significant savings in typing, but then the effort
for typing something like [] contrasted to \appoggiatura does not seem
all that large.

And we are talking about an incompatibility that can't easily be cast
into a convert-ly rule, so at the very least, scores relying on grace
notes without any beaming instructions remaining separate will require
manual changes.  And I don't know how this might affect things like
bagpipe music.

-- 
David Kastrup




reply via email to

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