bug-lilypond
[Top][All Lists]
Advanced

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

Re: [GLISS] why the hell all this fuss


From: Janek Warchoł
Subject: Re: [GLISS] why the hell all this fuss
Date: Thu, 6 Sep 2012 09:38:01 +0200

On Thu, Sep 6, 2012 at 8:19 AM, Werner LEMBERG <address@hidden> wrote:
> His very point is that deprecated syntax must either cause a warning
> or an error *by running LilyPond itself*.  I fully second that, and it
> would be a valuable task to check that for the transition from version
> 2.14 to 2.16.

+1

>> Example: hairpins.  There is no convenient way of specifying
>> hairpins that don't align with the notes (you have to use spacer
>> rests, which is bad for a number of reasons).  We need to have a
>> convenient way.  Adding this will be a syntax change, so let's do it
>> now instead of later.
>
> IMHO the `convenient way' is to define a macro; I don't see a need for
> a syntax change, since you always need rhythmical arguments to specify
> the start and end.

Hmm.  Maybe.
It would be useful for other kinds of spanners, and also articulations
(for example to place a turn during a note).  Would creating macros
for all of them be feasible? (maybe i miss something obvious?)
My rough idea would look something like this (this is just a musing,
not a proposal for discussion yet):

{ b2 \<@0.5 a2 address@hidden } meaning { << b1 { s2 \< s2 \! } >> }

>> Another example: vertical hairpins attached to arpeggios (Elaine
>> Gould shows them).
>
> Interesting.  I've never seen that before, I believe.  Can you give a
> link to an image?

Attached.

>> I don't think we have a simple way of extending our syntax to
>> express them - some basic design principles would have to be changed
>> a bit, i suppose.  So let's change them now.
>
> As far as I can see, what you want is not syntax changes.  You simply
> want new, additional commands.

Not quite :)  \arpeggioUpWithHairpinDown and
\arpeggioUpWithPianoFirstThenHairpinToPianissimo don't sound like fun!
;)

> Or rather, an improved set of standard macros which come with LilyPond.

That's more like it, but i'm not totally sure.
What i think of is a general way of attaching objects to another
objects.  For example '&' would attach objects:
<c e g>\arpeggio&\<  meaning  a hairpin attached to arpeggio
g\fermata&\markup \italic {10 seconds}  meaning  a "10 seconds" markup
attached to the fermata.

Again, this is just a musing for now.  I'm still looking for objects
that attach to other objects; i'll post something about it on new
GLISS mailing list, ok?

cheers,
Janek

Attachment: hairpins to arpeggios.jpg
Description: JPEG image


reply via email to

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