Again, I don't know what the expected behavior of autochange is, it
seems to be a pretty simple tool, however you may be able to achieve
the desired result with a spacer rest.
<<
\new PianoStaff {
<<
\new Staff = "up" {
\new Voice = "melOne" {
\key g \major
\autochange \relative c' {
b'16*1/2\rest
s16*1/2
\change Staff = "up"
b,16 e g fis
}
}
}
\new Staff = "down" {
\key g \major
\clef bass
}
>>
}
>>
On 27.02.2010, at 22:21, James Bailey wrote:
I can add the bug to the tracker, but can you make a short snippet
(http://lilypond.org/doc/v2.13/Documentation/web/tiny-examples#Tiny-
examples) that demonstrates the problem. and then a sentence or two
that explains what the behavior should be. Then I'll know what to
add, 'cause I don't ever use the autochanges, so I don't really
know what the expected outpus should be.
On 27.02.2010, at 21:32, George_ wrote:
Is there any particular format I need to conform to for bug
reports, or do I
just write 'freestyle'?
Patrick McCarty-3 wrote:
On 2010-02-27, George_ wrote:
So where can I report this?
If you run LilyPond without arguments, you'll see the bug report URL
listed at the very bottom:
http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs
-Patrick
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
View this message in context: http://old.nabble.com/Strange-
message-with-autochange-tp27710824p27730746.html
Sent from the Gnu - Lilypond - User mailing list archive at
Nabble.com.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
