lilypond-devel
[Top][All Lists]
Advanced

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

Re: Chromatic transposition -- a very small starting step


From: Joseph Wakeling
Subject: Re: Chromatic transposition -- a very small starting step
Date: Thu, 08 Jul 2010 23:06:17 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100528 Thunderbird/3.0.5

On 07/08/2010 10:25 PM, Neil Puttock wrote:
> On 8 July 2010 19:47, Joseph Wakeling <address@hidden> wrote:
> 
>>        (Example: take the music of bb. 9-10 in the sample music, and
>>        put it through the _original_ naturalizeMusic function.  You get
>>        left with a g-double-flat instead of an f-natural.)
> 
> You're using 2.12, I assume?

Yup.

> Since 2.13.14, transpositions greater than a double are normalized
> automatically, so the original \naturalizeMusic also produces an f
> natural here (see attached output using latest git).

Hah!  I've not kept up, I missed that being introduced ... :-P

('original' and 'revised' refer to the original and my version of
naturalizeMusic?)

So ... other than that it might be nice to have the snippet for 2.12, is
there any contribution that I can meaningfully make to 2.13 with this?
The ensuring-convergence-of-naturalization seems superfluous now, but
the variable determination of maximum alteration might be worthwhile.

The reason I was working on this was with the longer-term aim of being
able to have an option to set transposition style in music:

       \set Staff.transpositionStyle = #'chromatic
       % what follows will be transposed in chromatic fashion

       \set Staff.transpositionStyle = #'tonal
       % tonal transposition

       \set Staff.transpositionStyle = #'chromatic-harp
       % chromatic transposition tailored for harp, so
       % no alterations of > 1/2-tone

In any case, I should clearly update to 2.13.x before making further
revisions ...



reply via email to

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