lilypond-user
[Top][All Lists]
Advanced

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

Re: [SPAM] Re: Exact stem length?


From: Urs Liska
Subject: Re: [SPAM] Re: Exact stem length?
Date: Wed, 26 Mar 2014 12:25:54 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0

Hi Piaras,

I'm sorry, this has somehow slipped me. Your message had been posted last night.

This is already _very_ close to what I had in mind, thank you very much. I'll definitely have a closer look and study it.

There are two things I'd like to add:

a)
being able to explicitly define the beam shape. This can be manually done by once overriding Beam.positiony, but it should be an optional argument to the function. I would (without already knowing how) add this to the "props" argument either by changing this to a list and check if it has two or more elements or by checking if the pair is a pair of numbers (as used currently) or a pair of pairs (which would represent the current pair plus the pair of Beam.positions).

b)
Optionally add a slash because that gesture is often used with a slash. No idea yet, but I recall that Gilberto recently worked on that.

I will modify your example so it can be included in the openLilyLib snippet repository. We can then go from there to improve and enhance it.

BTW: Does anybody have a good name for that notation?

Thank you very much again.
Urs

Am 26.03.2014 12:10, schrieb Piaras Hoban:
Hi Urs,

(sent this last night but I seem to have issues getting my messages to the
list...)

It should do what you want in terms of generating stems.

It's a work in progress and still needs to be able to handle slurs,
dynamics, articulations, different stem patterns etc...

best wishes,

piaras




On 26 March 2014 08:38, Urs Liska <address@hidden> wrote:

Am 25.03.2014 13:45, schrieb Fredrik Wallberg:

  ...a way to override the distance between notehead and stem...


\override Stem.Y-offset = 2

(Sorry about the typos in my last message -- I wrote "beam lenghts"; I
meant "stem lengths of beamed notes".)



This works basically.
The attached image is the result of manually offsetting the stem for every
second note (i.e. any repeated pitch) by 0.25.

Of course that's an inacceptable amount of manual work for a general
solution. I think for a function it would be better to

- print the initial pitch
- print the last note at its pitch (without notehead of course)
- repeat the initial pitch for all intermediate events and
- calculate the offsets as a linear function.

Urs

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user







reply via email to

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