[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 467 in lilypond: Two calls to set-octavation confound intervening
From: |
codesite-noreply |
Subject: |
Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change |
Date: |
Thu, 13 Sep 2007 05:59:44 -0700 |
Issue 467: Two calls to set-octavation confound intervening clef change
http://code.google.com/p/lilypond/issues/detail?id=467
Comment #2 by trevorbaca:
Thanks for the quick response, Valentin.
OK, looking at #336 we find Han-Wen's comment #3:
"Clef and octavation operate on middleCPosition, which determines the vertical
offset
for a pitch. If you want to comibine both, set middleCPosition explicitly."
Which provides the following fix for the example above:
%%% BEGIN %%%
\new Staff {
#(set-octavation 1) c''''1 #(set-octavation 0)
\clef bass
c,1
#(set-octavation -1)
\set Staff.middleCPosition = #13
c,1
#(set-octavation 0)
\set Staff.middleCPosition = #6
c,1
}
%%% END %%%
That does, in fact, work (see attached).
So, from a user perspective, you need to think of calls to set-octavation and
middleCPosition coming *in pairs* (and in that order). UNLESS you're working in
treble clef, where you don't need to worry about calls to middleCPosition and
can
make calls to set-octavation with impunity.
Ugh. That's a bad pattern. set-octavation appears to be clef-aware when you're
working in treble; but then when you switch to another clef, set-octavation
appears
to break.
Wouldn't be it be better for set-octavation to be truly clef-aware?
Attachments:
sometimes-paired-octavation.png 7.4 KB
--
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