On 9 July 2010 22:35, Carl Sorensen wrote:
> Yes, but it's only in LilyPond miscellany, so it's really not important ;)
Heh, not important enough to deserve a separate menu node. ;)
> BTW, are you OK with me pushing the auto-beaming stuff?
Sorry, I was expecting another patch set for some reas
On 07/10/2010 12:25 PM, Joseph Wakeling wrote:
> On second thoughts, it seems like transposition constraints for the
> whole of LP could be set by four naturalize-limits: upper and lower
> limits respectively for c, e, f, b; and upper and lower limits for
> everything else.
OK, done. The attached
On 07/10/2010 12:16 PM, Joseph Wakeling wrote:
> In principle I can also use these to define custom cases for the notes
> c, e, f, b as well; not sure if I should, since the whole point of the
> naturalizeMusic function is to kill things like c-flats and e-sharps,
> and tonal transposition is alrea
On 07/09/2010 10:34 PM, Neil Puttock wrote:
> Sounds good to me.
So, here we go ... (faster to achieve than I expected, thanks to a
conversation with a friend who is Scheme-experienced).
I've defined a Scheme function "naturalize-limit" which can be used to
define limits for different cases, and
On 7/9/10 2:34 PM, "Neil Puttock" wrote:
> On 9 July 2010 21:02, Joseph Wakeling wrote:
>> Neil -- thanks ever so much for the detailed explanations.
>
> You're welcome.
>
> I hope what I've said is correct, since Carl's pinched my post and
> added it to the Contributor's Guide. :)
Yes, bu
On 9 July 2010 21:02, Joseph Wakeling wrote:
> Neil -- thanks ever so much for the detailed explanations.
You're welcome.
I hope what I've said is correct, since Carl's pinched my post and
added it to the Contributor's Guide. :)
> The transpose_mutable() function seems to be where it's at ... :
Neil -- thanks ever so much for the detailed explanations.
> Take a look at lily/music.cc to see where the transposition takes place.
The transpose_mutable() function seems to be where it's at ... :-)
I note the following lines which are surely responsible for cleaning up
anything larger than a
On 8 July 2010 23:20, Joseph Wakeling wrote:
> Can you explain more precisely ... ? This seems like something I should
> understand very well in order to provide an effective solution.
Context properties (using \set & \unset) are tied to engravers: they
provide information relevant to the gener
On 07/09/2010 12:09 AM, Neil Puttock wrote:
> That sounds like a useful enhancement, except that it would be a music
> property rather than a context property, since transposition happens
> before translation.
Can you explain more precisely ... ? This seems like something I should
understand very
On 8 July 2010 22:06, Joseph Wakeling wrote:
> On 07/08/2010 10:25 PM, Neil Puttock wrote:
> ('original' and 'revised' refer to the original and my version of
> naturalizeMusic?)
Yes.
> So ... other than that it might be nice to have the snippet for 2.12, is
> there any contribution that I can
On 07/08/2010 10:25 PM, Neil Puttock wrote:
> On 8 July 2010 19:47, Joseph Wakeling 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-natur
On 8 July 2010 19:47, Joseph Wakeling 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?
Since 2.13.14,
Hello all,
As per earlier discussion on the -user list:
http://www.mail-archive.com/lilypond-u...@gnu.org/msg51183.html
... I finally managed to put some time and mental energy towards
chromatic transposition, in particular, the naturalizeMusic function
from the LSR.
I've attached a draft versio
13 matches
Mail list logo
