On Saturday 23 April 2005 17.39, Will Oram wrote: > I understand your concerns. If I had any more specific information, I > would have gladly posted it...this is by far not the first time I've > described a bug on bug-lilypond. I've tooled around with lily > for...wow, 1.5 years already. Anyway, I have done my absolute best to > identify the root of these problem chords (and it ain't an inverted V, > haw haw), but it seems to be a truly random problem.
Seems like a strange bug. If you want to isolate it, here are a few ideas you can experiment with: - Change the pitches globally (with search/replace), to just include a few ones (say c, e and g). Does this change the problem? If not, do the strange chords change pitch when the other notes do? In that case, which notes control the pitches of the strange chords? - How does the problem change if you remove one bar at the end or beginning of the piece, or if you remove one staff? How much can you remove before the problem disappears? - You can use midi2ly on lily's output to view the midi files' content - When you have done the above experimenting, I'm sure you have reduced the problem to something whose .ly source you can share. - You could try 2.4's midi output also, 2.5 is considered unstable. good luck! Erik _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
