bug-lilypond
[Top][All Lists]
Advanced

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

Re: ‘\note’ DURATION (string) DIR (number)


From: Sylvius Pold
Subject: Re: ‘\note’ DURATION (string) DIR (number)
Date: Wed, 21 Dec 2016 12:08:15 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.5.1

Hi Simon,

thanks for your explanation. Now I get it. I think that the unexpected use of #UP in the example in the docs is very confusing. Maybe it should be mentioned somewhere that #UP equals 1 and #DOWN equals -1.

Sylvius

On 20.12.2016 20:26, Simon Albrecht wrote:
Hi Sylvius,

there is no bug involved. If you don’t understand something, it’s better to ask on the user list. Help will be gladly given.


On 20.12.2016 20:10, Sylvius Pold wrote:
Hi,

I seem to have some problems understanding the manuals. In lilypond-notation (instrument specific markup) I read:


‘\note’ DURATION (string) DIR (number)

     This produces a note with a stem pointing in DIR direction, with
     the DURATION for the note head type and augmentation dots. For
     example, ‘\note #"4." #-0.75’ creates a dotted quarter note, with a
     shortened down stem.

This description says that the \note markup command takes _two_ _mandatory_ arguments. The first is for the duration, which, as shown in the doc string example, can include one or more augmentation dots. The second is for the stem direction _and_ length. #UP evaluates to 1, #DOWN evaluates to -1. Positive numbers make the stem go up, negative numbers make it go down, the absolute amount is a factor for the length. So using #0.2 gives you a very short up stem, #-10 gives you a very long down stem.




It's not clear to me how to achieve e.g. a dotted quarter note, with a shortened *up* stem. This does not work:

1. \markup { \note #"4" #UP #0.75 }
2. \markup { \note #"4" #UP #-0.75 }

The function doesn’t take a third argument.


It's also not clear to me why it is necessary to define a DIR direction in order to get a whole note.

First way to answer: Technically, whole notes do have stems, only they are invisible. Though that’s really just an internal detail. Second way: The function just isn’t implemented such as to have an optional argument, so you always need to give both arguments, even for whole notes.

HTH, Simon




reply via email to

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