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

[codesite-noreply]

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 1) c''''1 #(set-octavation 0)
   \clef bass
   c,1
   #(set-octavation -1) c,1 #(set-octavation 0)
   c,1
}

%%%% END %%%



Notice that all three of the final pitches are c,1 but that the last two of
those c,1 notate incorrectly *as though they were in the treble clef*.

What seems to be necessary to trigger this is, in this order,

  1. a first call to set-octavation
  2. a clef change
  3. a secnd call to set-octavation

Notes in between the two calls are OK; notes after the second call print in
the wrong clef. (This obviously makes scores look quite bizarre.)


Attachments:
        octavation-insanity.png  8.1 KB 


Issue attributes:
        Status: New
        Owner: ----
        Labels: Type-Defect Priority-Medium

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