Comment #16 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
Issue 2259 has been merged into this issue.
___
bug-lilypond
Comment #15 on issue 621 by kie...@alumni.rice.edu: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
This is true of arpeggios as well. Currently, piano-centered dynamics
collide with arpeggios.
Updates:
Status: Accepted
Labels: -Patch-review
Comment #11 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
One argument against having Lilypond make space
Updates:
Owner: k-ohara5...@oco.net
Cc: v.villen...@gmail.com
Labels: -Patch-new Patch-review
Comment #10 on issue 621 by pkx1...@gmail.com: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
Comment #8 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
Patch at http://codereview.appspot.com/4805054/
Regression test suite shows the expected changes: dynamic text
Trevor Daniels t.daniels at treda.co.uk writes:
It's section 4.4.3 that would be affected. We'd need to
think of another example where it is preferable to space
out the notes rather than stack outside-staff objects.
I can't think of any similarly-realistic case for /outside-staff/ objects,
It is very tempting to make
\override DynamicText #'extra-spacing-width = #'(-0.5 . 0.5)
be the new default.
I have been happily using this, and the regression tests are not
harmed by the change.
I think this would be a better default.
We would need to rewrite the end of Learning Manual
Comment #5 on issue 621 by perpeduu...@googlemail.com: Dynamics should
avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
+1 for the extra-spacing-width, although it sounds more like a workaround.
Can this be related to issue
Comment #6 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
although it sounds more like a workaround.
Well, the purpose of 'extra-spacing-width' is to specify how much
Updates:
Labels: Patch-review
Comment #4 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
It is very tempting to make
\override DynamicText #'extra-spacing-width
Comment #3 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
If we want dynamics to get the space they need when notes are placed
relative to barlines, then we can say
Comment #2 on issue 621 by markpolesky: Dynamics should avoid cross-staff
BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
I'm adding the phrase DynamicText SpanBar collision to
this post so others can find this issue with a search.
Jay
Comment #1 on issue 621 by PhilEHolmes: Dynamics should avoid cross-staff
BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
Image added
Attachments:
621.png 3.6 KB
___
bug-lilypond mailing
Issue 621: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff,
PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
New issue report by v.villenave:
% When short durations occur after a bar line, dynamics
% can collide with the BarLine.
\version 2.11.45
\new
14 matches
Mail list logo
