This is a known problem that has not made it into the bug tracker, as
far as I can see.
See http://lists.gnu.org/archive/html/lilypond-devel/2007-04/msg00136.html
Also, as you can see later in the same thread, it doesn't help to add
the bar engraver
to the context. Here comes a somewhat modified version of the example in
the above
email, that more clearly shows the problem. Note that this is different
than issue 621.
\version "2.11.47"
upper = \relative c'' {
\clef treble
\key c \major
\time 4/4
a4 b c d |
e4 e e e |
}
lower = \relative c {
\clef bass
\key c \major
\time 4/4
a2 c |
a1 |
}
dynamics = {
s1\fff\> |
s1\!\pp |
}
% When the dynamics and music are in the same voice, the bar lines are
avoided:
\new GrandStaff <<
\new Staff \new Voice << \upper \dynamics >>
\new Staff \lower
>>
% When the dynamics is in a separate Voice, you get a collision
% with the bar line. Bug!
\new GrandStaff <<
\new Staff << \new Voice \upper \new Voice \dynamics >>
\new Staff \lower
>>
/Mats
Jonathan Kulp wrote:
Well, it's not very elegant but it works o.k. I just override the
dynamics positioning each time I need it. I just experimented to find
the right values. To make life easier I define the override as a
variable:
nuj = \once \override DynamicText #'extra-offset = #'(+1.0 . -0.0)
Then I just go through and put \nuj before each dynamic marking that
needs a nudge to the right. If someone can make a fix that will let
Lilypond avoid the collisions in the first place that'd be amazing.
What I observe is that the dynamics are placed just fine as long as
the notes in the music staves have some kind of accidental in front of
them. Otherwise they're positioned pretty close to the barline and
the dynamics below end up colliding with a barline. Best,
Jon
Valentin Villenave wrote:
2008/6/4 Jonathan Kulp <[EMAIL PROTECTED]>:
Well, since no one is going to answer this I guess I'll answer it
myself:
RTFM (the Learning Manual, that is) :D
I have encountered similar problems with dynamics colliding with
cross-staff barlines, but I never really found a way to get rid of
this annoyance.
My best (and only) guess would be to use the classic workaround used
for lyrics:
http://lsr.dsi.unimi.it/LSR/Item?id=356
i.e. adding the barline engraver to the dynamics context.
But in fact, it didn't work great so far. Please try it and tell us if
you're luckier than me :-)
Cheers,
Valentin
--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
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
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond