[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 3643 in lilypond: Autochange clef assignment broke
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 3643 in lilypond: Autochange clef assignment broken by multiple initial rests |
Date: |
Sun, 03 Nov 2013 01:44:02 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Defect
New issue 3643 by address@hidden: Autochange clef assignment broken
by multiple initial rests
http://code.google.com/p/lilypond/issues/detail?id=3643
Reported by address@hidden:
Here is a case where autochange weirdly sends the top note to the
bass clef, using lots of ledger lines:
+++++++++++++++++++++
\version "2.17"
\score
{
\new PianoStaff
<<
\new Staff = "up" {
<<
\new Voice {
\voiceOne
\autochange
\relative c'' {
r2 r4 e4 % problem case: both voices go to bass clef
% r2. e4 % workaround
% e1 r2 r4 e4 % this will also work
}
}
\new Voice {
\voiceTwo
\autochange
\relative c {
r2 r4 a4 % problem case: both voices go to bass clef
% r2. a4 % workaround
% a1 r2 r4 a4 % this works
}
}
>>
}
\new Staff = "down" {
\clef bass
}
>>
}
++++++++++++++++++
Behaviour seems to be triggered by two initial rests; changing to a dotted
rest in *both* voices restores correct behaviour, changing only one is
still broken. Adding a note before the rests also gives expected output.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Lilypond-auto] Issue 3643 in lilypond: Autochange clef assignment broken by multiple initial rests,
lilypond <=