Re: PianoStaff spacing in 2.11
Perhaps, this is related to
http://code.google.com/p/lilypond/issues/detail?id=445start=100
Try adding
\layout{
\context{
\Staff
\override VerticalAxisGroup #'minimum-Y-extent = #'(-4 . 4)
}
}
to your file and see if it improves the situation.
/Mats
Neil Puttock wrote:
Hi everybody,
A short while back, I was under the misapprehension that there was
something wrong with the spacing in piano staves when using version
2.11. Having erroneously submitted a bug report to this effect, I
found out that thanks to the new spacing engine, the fixed distance
workaround present in 2.10 was no longer necessary (hence why the
PianoStaff centred dynamics template no longer works properly).
I have been typesetting a few piano pieces, and have found that the
spacing can vary wildly, especially when adding dynamics. This is, in
my opinion, a rather unfortunate situation, and one not in keeping
with traditional engraving rules for piano music.
My question is this: Is it possible to force fixed distance between
the staves in a PianoStaff under version 2.11? I've tried various
overrides, but all they tend to do is influence the minimum spacing
and amount of system stretching.
Thanks,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
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
Re: PianoStaff spacing in 2.11
Hi Trevor Have you tried using the alignment-offsets part of the NonMusicalPaperColumn's line-break-system-details property? Here's an example where we override the NonMusicalPaperColumn grob in the Score's context block; the result is completely fixed vertical distance throughout the score: Excellent! Thank you. It would be nice to have this set by default for PianoStaff, but I suppose that's a bit difficult since NonMusicalPaperColumn lives in the Score context. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: PianoStaff spacing in 2.11
2007/9/11, Neil Puttock [EMAIL PROTECTED]: It would be nice to have this set by default for PianoStaff, but I suppose that's a bit difficult since NonMusicalPaperColumn lives in the Score context. No: the *real* question is: who's gonna add it to the Lilypond Snippet Repository ASAP? :) (to whoever is: the whole thing may need to be commented, since LSR is still running 2.10. Just add [needs upgrade] or something in the Subject, so I can remember to uncomment it once it's upgraded) Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: PianoStaff spacing in 2.11
On 9/11/07, Valentin Villenave [EMAIL PROTECTED] wrote: 2007/9/11, Neil Puttock [EMAIL PROTECTED]: It would be nice to have this set by default for PianoStaff, but I suppose that's a bit difficult since NonMusicalPaperColumn lives in the Score context. No: the *real* question is: who's gonna add it to the Lilypond Snippet Repository ASAP? :) OK, you've twisted my arm. ;) (to whoever is: the whole thing may need to be commented, since LSR is still running 2.10. Just add [needs upgrade] or something in the Subject, so I can remember to uncomment it once it's upgraded) Would you mind commenting http://lsr.dsi.unimi.it/LSR/Item?id=304 too? When I added it I was still using 2.10, but obviously under 2.11 tweaking spanners is quite different. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: PianoStaff spacing in 2.11
2007/9/11, Neil Puttock [EMAIL PROTECTED]:
Would you mind commenting
http://lsr.dsi.unimi.it/LSR/Item?id=304 too? When I added
it I was still using 2.10, but obviously under 2.11 tweaking spanners is
quite different.
I'll just mark it as unapproved for now; it works well with 2.10. If
you (or anyone) send the updated code, then I'll edit it and comment
it until the LSR upgrades.
\relative c'' {
\override TrillSpanner #'edge-text =
#(cons (markup #:line (#:halign -0.5 #:musicglyph scripts.trill
#:teeny #:raise 0.65 #:sharp)) )
b1\startTrillSpan b\stopTrillSpan
\override TrillSpanner #'edge-text =
#(cons (markup #:line (#:halign -0.5 #:musicglyph scripts.trill
#:teeny #:raise 0.5 #:flat)) )
c\startTrillSpan c\stopTrillSpan
}
Thanks
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
PianoStaff spacing in 2.11
Hi everybody, A short while back, I was under the misapprehension that there was something wrong with the spacing in piano staves when using version 2.11. Having erroneously submitted a bug report to this effect, I found out that thanks to the new spacing engine, the fixed distance workaround present in 2.10 was no longer necessary (hence why the PianoStaff centred dynamics template no longer works properly). I have been typesetting a few piano pieces, and have found that the spacing can vary wildly, especially when adding dynamics. This is, in my opinion, a rather unfortunate situation, and one not in keeping with traditional engraving rules for piano music. My question is this: Is it possible to force fixed distance between the staves in a PianoStaff under version 2.11? I've tried various overrides, but all they tend to do is influence the minimum spacing and amount of system stretching. Thanks, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: PianoStaff spacing in 2.11
On 9/10/07, Neil Puttock [EMAIL PROTECTED] wrote:
Hi everybody,
A short while back, I was under the misapprehension that there was something
wrong with the spacing in piano staves when using version 2.11. Having
erroneously submitted a bug report to this effect, I found out that thanks
to the new spacing engine, the fixed distance workaround present in 2.10 was
no longer necessary (hence why the PianoStaff centred dynamics template no
longer works properly).
I have been typesetting a few piano pieces, and have found that the spacing
can vary wildly, especially when adding dynamics. This is, in my opinion, a
rather unfortunate situation, and one not in keeping with traditional
engraving rules for piano music.
My question is this: Is it possible to force fixed distance between the
staves in a PianoStaff under version 2.11? I've tried various overrides, but
all they tend to do is influence the minimum spacing and amount of system
stretching.
Hi Neil,
Have you tried using the alignment-offsets part of the
NonMusicalPaperColumn's line-break-system-details property?
Here's an example where we override the NonMusicalPaperColumn grob in
the Score's context block; the result is completely fixed vertical
distance throughout the score:
%%% BEGIN %%%
\version 2.11.32
\layout {
\context {
\Score
\override NonMusicalPaperColumn
#'line-break-system-details =
#'((alignment-offsets . (0 -14))) } }
\new Score
\new PianoStaff
\new Staff {
c'1
\break
c'1
\break
c'1
}
\new Staff {
\clef bass
c'1
c'1
c'1
}
%%% END %%%
And here's an example where we override the NonMusicalPaperColumn grob
on the fly at different points (but always at line breaks) throughout
the score; the result is precisely controlled -- but varying --
amounts of vertical space between systems:
%%% BEGIN %%%
\version 2.11.32
\new PianoStaff
\new Staff {
\overrideProperty #Score.NonMusicalPaperColumn
#'line-break-system-details
#'((alignment-offsets . (0 -10)))
c'1
\break
\overrideProperty #Score.NonMusicalPaperColumn
#'line-break-system-details
#'((alignment-offsets . (0 -20)))
c'1
\break
\overrideProperty #Score.NonMusicalPaperColumn
#'line-break-system-details
#'((alignment-offsets . (0 -30)))
c'1
}
\new Staff {
\clef bass
c'1
c'1
c'1
}
%%% END %%%
Note that you can freely combine the two types of override shown here.
This will let you set a default fixed space for the entire score and
then freely override that default fixed space to other (but equally
specific) values as necessary.
Note also that you use plain old \override in a \context (or \with)
block but that you use the special \overrideProperty command when
making changes to the NonMusicalPaperColumn grob inline with note
entry.
(Note finally that these settings work for ALL types of staff ...
including, but not limited to, piano and other grouped staves.)
If you like this way of accounting for vertical positioning, there's
some more at 11.5.3 Explicit staff and system positioning.
Trevor.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
