bug-lilypond
[Top][All Lists]
Advanced

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

Issue 754 in lilypond: \transpose should not affect \transposition


From: codesite-noreply
Subject: Issue 754 in lilypond: \transpose should not affect \transposition
Date: Tue, 03 Mar 2009 22:27:13 +0000


Comment #2 on issue 754 by n.puttock: \transpose should not affect \transposition
http://code.google.com/p/lilypond/issues/detail?id=754

I was going to suggest a property which can mark music as untransposable, but a quick
check confirms that it already exists.  Unfortunately it doesn't work with
\transposition.

Using the test file and \withMusicProperty for convenience, it's easy to prevent the individual notes in each stave from being transposed, but it seems the pitch passed to \transposition has already been transposed by the time untransposable is set:

\score {
 \transpose c d {
 \new StaffGroup <<
   \new Staff {
     \key c \major
     % this works
     \withMusicProperty #'untransposable ##t c'1
   }
   \new Staff {
     % this fails
     \transposition \withMusicProperty #'untransposable ##t bes
     \key d \major
     d'1
   }
 >>
 }
 \layout {}
 \midi {}  % Should be a unison D, but is not
}

Having checked the music function for \transposition, it's clear that untransposable
= ##t for the note, but it seems to be to late to have any effect.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings




reply via email to

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