lilypond-devel
[Top][All Lists]
Advanced

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

Re: Questions about articulation settings for the GDP


From: Graham Percival
Subject: Re: Questions about articulation settings for the GDP
Date: Tue, 23 Oct 2007 12:47:16 -0700
User-agent: Icedove 1.5.0.12 (X11/20070607)

Eyolf Østrem wrote:
I'm working on the articulations for the GDP, and I've ran into some
things that I would need assistance on:

In the absence of other replies, here's my best guesses.

1. Automatic placement. I think there should  be a brief note about
what the rules are for how they are placed by default. Opposite of the
stem? How about polyphony? According to the voice number?

I think the best answer is to experiment -- make up examples with and without polyphony (or perhaps simply altering \voiceOne to \voiceTwo or no command at all), give it a bunch of articulations, and see what happens.

...
Actually, this could be a candidate for LM 3 Fundamental concepts, since it affects -\markup{} as well.

...
It's still worth investigating this and writing up some text. The text+examples might end up in LM instead of notation reference, but for now add it to Expressive marks.


2. I've tried to work with different values for crescendoSpanner, but
there is no difference between line and dashed-line -- they both
produce a dashed line. Here's the example from the manual (ran with v.
2.11.34):

\set crescendoText = \markup { \italic "cresc. poco" }
\set crescendoSpanner = #'line
a'2\< a a a a a a a\!\mf

My first thought was that this could be an old format, but running it through convert-ly (guessing at version 2.10.0) didn't improve it.

Mats?  I haven't looked at this in detail; is this a bug or changed syntax?

3. similar problem with \override Hairpin #'after-line-breaking = ##t
It should, as I've understood it, let the hairpin continue to the
first note on the following line, but that doesn't happen here.

Create a minimal example and file a bug report? We're certain to find bugs while we work on this. :(

Cheers,
- Graham




reply via email to

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