Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #9 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are lis

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #8 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_38 -- You received this me

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #7 by gpermus: (No comment was entered for this change.) Issue attribute updates: Labels: -fixed_2_11_38 -- You received this message because you are l

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #6 by v.villenave: Thanks a LOT! This was really an annoying bug (speaking from personal experience). I'll verify it as soon as I can. Issue attribute updates

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #5 by joeneeman: See the attachments to 533 for patches fixing this bug (parts 1, 6 and 7 of the patch set, I think). Issue attribute updates: Status:

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #4 by v.villenave: No duplicate then? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #3 by gpermus: Of course it would be better, but that's an enhancement. :) Issue attribute updates: Status: Accepted Labels: -Type-Defect -Prior

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

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, whi

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #1 by v.villenave: lol duplicate of #336 :) but it *is* an annoying issue though. -- You received this message because you are listed in the owner or CC fiel

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 New issue report by trevorbaca: Hi, The last two pitches in the following snippet are badly wrong. %%% BEGIN %%% \version "2.11.32" \new Staff { #(set-octavation