lilypond-user
[Top][All Lists]
Advanced

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

Re: "non adjacent" glissando: state of the art?


From: Trevor Bača
Subject: Re: "non adjacent" glissando: state of the art?
Date: Thu, 29 Mar 2007 06:09:49 -0500

On 3/29/07, Andrea Valle <address@hidden> wrote:

Thanks Mats.

here's the mail starting the thread I'm referring to, and pointing to a
previous and related one:

http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00271.html

Best

-a-



On 29 Mar 2007, at 09:16, Mats Bengtsson wrote:

It would be much easier to realize exactly what you want to achieve if you
included an example of the LilyPond code you use today (or at least provide
an exact reference to some of the earlier emails you mention).

  /Mats

Andrea Valle wrote:

Hi to all,
I'm experimenting what seems to be a common problem. I have to use
glissandos connecting non adjacent notes, e.g. g4~g16 a8. . The common
notation, and also the one suggested by Stone (p. 21), is to indicate the
rhythm without noteheads. So, I'd like to have a straight line connect the g
and the a and a headless note on the g16.
I've searched thru the list, and see some (recent) posts related exactly to
this topic.
There was also a proposal for sponsoring.

As I have been out of the list for a year,  I'm not understanding the actual
situation.
1. Is there a way to notate a glissando precisely in this way (avoiding the
trick of using many glissandos connecting the composing notes)?

2. Is there (still) a sponsoring project for such a feature? In the case, I
could participate. I saw something about 100 eu, if I understood clearly.
2b. What about sponsoring? Is it still active? It isn't clear to me from the
usual page:
http://lilypond.org/web/sponsor/options

Hi Andrea,

Noncontiguous (or nonadjacent) glissandi haven't been implemented yet.

If the opportunity is still open, I'll be happy to help sponsor.

Trevor.


--
Trevor Bača
address@hidden

reply via email to

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