#621 Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)

[Anonymous]

Originally created by: *anonymous

Originally created by: v.villenave

When short durations occur after a bar line, dynamics can collide with the BarLine.

:::TeX
\version "2.11.45"

\new GrandStaff <<
  \new Staff { c'1 c'8\fff c'2.. }
  \new Staff { r1*2 }
>>

[Google Importer]

Originally posted by: Elu...@gmail.com

(No comment was entered for this change.)

Status: Verified

[Google Importer]

Originally posted by: Karol.Ma...@gmail.com

The patch doesn't work for Dynamics context:

:::TeX
\new GrandStaff <<
  \new Staff { c'1 c'8 c'2.. }
  \new Dynamics { s1 s8 \fff s2.. }
  \new Staff { r1*2 }
>>

and 'fff' still hits SpanBar.

[Google Importer]

Originally posted by: dak@gnu.org

\ffff makes the problem more apparent.  Throwing a variety of settings and engravers at the Dynamics context did not faze it: it would appear that I am missing the right incantation here.

Cc: -v.villenave

[Google Importer]

Originally posted by: k-ohara5...@oco.net

The patch for issue 910 separated the printing of span bars (using the grob SpanBar) form the spacing of span bars (SpanBarStubs).  It looks like the patch for issue 910 should have changed the engravers in Dynamics as it did for Lyrics, so a workaround is to change the engravers explicitly:

:::TeX
\new Dynamics \with {
   \remove Bar_engraver
   \consists Pure_from_neighbor_engraver
} { s1 s8 \ffff s2.. }

Labels: -Fixed_2_19_0
Status: Accepted

[Google Importer]

Originally posted by: janek.li...@gmail.com

Why do you say it's a workaround?  Is there anything wrong with removing Bar_engraver and adding Pure_from_neighbor_engraver to the Dynamics context?

[Google Importer]

Originally posted by: dak@gnu.org

Keith?  Any word on Janek's comment #30?  Would your change in comment #29 be what we should be doing in the Dynamics context?

It looks ugly as heck so if it is "the right thing to do"™ regarding our current code base, I'd prefer if we just changed it in LilyPond ourselves instead of advertising that kind of setting to the world at large.

Then we have more leeway to quietly solve this differently at some later point of time without fearing too many backward compatibility repercussions.

[Google Importer]

Originally posted by: dak@gnu.org

(No comment was entered for this change.)

Owner: ---