2014-10-07 20:16 GMT+02:00 David Kastrup <d...@gnu.org>:
> Peter Crighton <petecrigh...@gmail.com> writes:
>
> > 2014-10-05 16:38 GMT+02:00 David Kastrup <d...@gnu.org>:
> >> >
> >> > Okay, thanks for explaining. For now I am content with using “\omit
> >> > Staff.KeySignature” and “\revert Staff.KeySignature.stencil”
> respectively
> >> > to get rid of the problem.
> >> >
> >> > What I found strange, though, was that in my score the problem only
> >> > appeared when there was a time signature change at the beginning of
> the
> >> > line. I couldn’t reproduce this in a minimal example.
> >>
> >> Huh. Maybe LilyPond _does_ set the line/horizontal spacing fresh after
> >> determining the break points. But things like key/time signature
> >> changes are repeated on the _previous_ line. And maybe it's too late to
> >> redo the line spacing on _that_?
> >>
> >> You can try creating a minimal example with multiple lines by manually
> >> placing breaks with \break.
> >
> >
> > I know, what I meant was that in my minimal example the problem appears
> in
> > every line, not only those with a time signature change.
> >
> >
> > \version "2.19.13"
> >
> > <<
> > \new Staff <<
> > \relative c'' {
> > c1 \break
> > c2.
> > c \break
> > c1
> > c
> > }
> > >>
> > \new Staff \with {
> > \RemoveEmptyStaves
> > } <<
> > {
> > \key d \major
> > R1 \break
> > \time 3/4
> > R2. \break
> > R2.
> > \key c \major
> > \time 4/4
> > R1 \break
> > R1
> > }
> > >>
> >>>
>
> I don't really see what you are getting at. The horizontal spacing in
> your example is, as I conjectured first, fixed before removing the
> frenched staff: it is in all cases identical to the version without
> \RemoveEmptyStaves. Fixing that would require another pass through the
> horizontal spacing, redistributing the additionally available space
> without considering the frenched staff. I don't know how well this
> could be implemented given current LilyPond's internals, but it is
> certainly going to be a non-trivial expense.
Maybe I misunderstood what you had written before, but you seemed to be
surprised about the problem appearing in my score only at time signature
changes. And that’s the one thing I can’t reproduce in a minimal example,
there the problem appears in every line, regardless of there being a time
signature change or not. In my score there would be no extra space before
the first note at the beginning of the line in a situation like measure 3.
--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de
--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de
2014-10-07 20:16 GMT+02:00 David Kastrup <d...@gnu.org>:
> Peter Crighton <petecrigh...@gmail.com> writes:
>
> > 2014-10-05 16:38 GMT+02:00 David Kastrup <d...@gnu.org>:
> >> >
> >> > Okay, thanks for explaining. For now I am content with using “\omit
> >> > Staff.KeySignature” and “\revert Staff.KeySignature.stencil”
> respectively
> >> > to get rid of the problem.
> >> >
> >> > What I found strange, though, was that in my score the problem only
> >> > appeared when there was a time signature change at the beginning of
> the
> >> > line. I couldn’t reproduce this in a minimal example.
> >>
> >> Huh. Maybe LilyPond _does_ set the line/horizontal spacing fresh after
> >> determining the break points. But things like key/time signature
> >> changes are repeated on the _previous_ line. And maybe it's too late to
> >> redo the line spacing on _that_?
> >>
> >> You can try creating a minimal example with multiple lines by manually
> >> placing breaks with \break.
> >
> >
> > I know, what I meant was that in my minimal example the problem appears
> in
> > every line, not only those with a time signature change.
> >
> >
> > \version "2.19.13"
> >
> > <<
> > \new Staff <<
> > \relative c'' {
> > c1 \break
> > c2.
> > c \break
> > c1
> > c
> > }
> > >>
> > \new Staff \with {
> > \RemoveEmptyStaves
> > } <<
> > {
> > \key d \major
> > R1 \break
> > \time 3/4
> > R2. \break
> > R2.
> > \key c \major
> > \time 4/4
> > R1 \break
> > R1
> > }
> > >>
> >>>
>
> I don't really see what you are getting at. The horizontal spacing in
> your example is, as I conjectured first, fixed before removing the
> frenched staff: it is in all cases identical to the version without
> \RemoveEmptyStaves. Fixing that would require another pass through the
> horizontal spacing, redistributing the additionally available space
> without considering the frenched staff. I don't know how well this
> could be implemented given current LilyPond's internals, but it is
> certainly going to be a non-trivial expense.
>
> --
> David Kastrup
>
>
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
