Phil Holmes <mail <at> philholmes.net> writes: > From: "David Kastrup" <dak <at> gnu.org> > > Keith OHara <k-ohara5a5a <at> oco.net> writes: > >> Petr Gajdos <pgajdos <at> suse.cz> writes: > >> > >>> I have same symptoms like Phil described. > >> > >>> Core was generated by `/usr/bin/lilypond -dpreview -dresolution=150 -o > >>> ./ > >> out-www orchestra.ly'. > >> > >> If I understand correctly, this gives a way to reproduce the bug, on a > >> 64-bit GNU/Linux system, without building the entire Documentation.
> > It's a nuisance that I can't reproduce on my 32bit system. Maybe I need > > to see what it would entail to install a 64bit system in addition (my > > CPU would allow that). David's recently-pushed patch looks quite promising, under the theory that the problem depends on the initial estimate of the placement of the "Presto" tempo mark. If that patch does not solve the problem, we can narrow down the causes by testing the "Presto" theory. > If that is so, an \override MetronomeMark.Y-offset=#0 > at line 99 of orchesra.ly should avoid the problem. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel