Status: Accepted
Owner: ----
Labels: Type-Defect
New issue 3220 by [email protected]: partcombineChords affects preceding
note and gives wrong output
http://code.google.com/p/lilypond/issues/detail?id=3220
Pavel Roskin reported here:
http://lists.gnu.org/archive/html/bug-lilypond/2013-03/msg00008.html
about a problem with partCombine. There are several open trackers for
partCombine, but this appears to be a distinct problem.
Hello!
Following code gives incorrect output:
\version "2.16.1"
soprano = {
\partcombineApart g'8 \partcombineChords g'8
}
alto = {
c'16 [ c'16 ] c'8
}
\score {
\partcombine \soprano \alto
}
The first c'16 is drawn without a beam, the second c'16 has its beam
attached to the subsequent chord and has its stem up. It means that
partcombineChords not only fails to produce the right output, but it
affects the notes that precede it in time.
Replacing partcombineChords with partcombineAutomatic fixes the problem.
That's weird because partcombineChords is meant to make chords only, and it
fails at that, whereas partcombineAutomatic is a more complicated mode, and
it makes a good looking chord.
It would be a real problem when the parts are separated by more than an
octave. partcombineAutomatic would draw the notes separately.
partcombineChords would be needed to produce a chord.
The problems exists both in the current development version and 2.16.1.
--
Regards,
Pavel Roskin
Attachments:
partcombine-stem-chord.png 3.0 KB
partcombine-stem-auto.png 2.9 KB
--
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
