In this specific example, it seems that you have an extremely wide
key signature in one stave and none at all in the other stave. This is
a typical situation where you want to use
\override Score.SpacingSpanner #'average-spacing-wishes = ##f
since by default, LilyPond takes an average value of the ideal spacing for
each separate stave (see also
http://lists.gnu.org/archive/html/bug-lilypond/2005-12/msg00043.html,
which shows that this specific problem has been present at least since
version 2.6).
/Mats
Kieren MacMillan wrote:
Hello, all --
I hope you have seen the earlier followups in this email thread [...]
Fair enough, but it's a *lot* more work in recent versions to have a
acceptable-looking score (with respect to initial measure spacing)
than it was in previous versions.
For example, I've included a screenshot of untweaked Lilypond output
for an instrumental part I cranked out yesterday -- you'll see that
the initial spacing is totally unacceptable without a good deal of
tweaking (the rests are almost completely swallowed by the key
signature); in other parts of the score, it is nearly impossible to
distinguish the barline from the left-hand side of the leading flat; etc.
Cheers,
Kieren.
p.s. Once the show opens (this weekend), and I have more time, I'll
submit specific bug reports...
------------------------------------------------------------------------
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
