Well, there’s reason enough to redirect this to bug-lilypond, isn’t it?
Somehow, Mozilla Thunderbird messes up the code examples, so I can’t do
so well. Perhaps the OP’s and Harm’s first mails in the thread,
respectively, should suffice for illustration.
~Simon
Am 03.03.2015 um 23:01 schrieb David Nalesnik:
On Tue, Mar 3, 2015 at 3:59 PM, David Nalesnik
<david.nales...@gmail.com <mailto:david.nales...@gmail.com>> wrote:
On Tue, Mar 3, 2015 at 3:44 PM, David Nalesnik
<david.nales...@gmail.com <mailto:david.nales...@gmail.com>> wrote:
Harm,
On Tue, Mar 3, 2015 at 3:30 PM, Thomas Morley
<thomasmorle...@gmail.com <mailto:thomasmorle...@gmail.com>>
wrote:
thanks for testing. So this function may use as a test-case.
No idea whats causing this bug, though. And because I'm
not able to
reproduce it, I can't help furthermore :(
I don't think I could do anything either. I wouldn't know how
to build LilyPond for Windows to verify any fix...
An observation. In the following snippet, you'll note in the log
output that the default-direction of the downstemmed F and B is
0--CENTER. This means that Stem::calc-direction (in lily/stem.cc)
will take the property 'neutral-direction. This property is
supposed to specify the direction of a note on the midline--B only
in our case. F should have a default-direction of 1.
Note that adding
\override Stem.neutral-direction = #1
fixes the problem for the bad stems.
David
_______________________________________________
lilypond-user mailing list
lilypond-u...@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
