Re: long dynamic strings displace low notes

[David Kastrup]

Thomas Morley <address@hidden> writes:

> 2016-04-26 11:13 GMT+02:00 David Kastrup <address@hidden>:
>> Thomas Morley <address@hidden> writes:
>>
>>> 2016-04-26 10:53 GMT+02:00 Phil Holmes <address@hidden>:
>>>> Why do you say that expected behaviour is to force the dynamic down?  
>>>> Moving
>>>> the note is potentially equally valid behavior, depending on the
>>>> typesetter's preference.
>>>
>>> It's clearly a bug. See this small (not tiny) example plus comments
>>> from my earlier post at
>>> http://lilypond.1069038.n5.nabble.com/Dynamics-placement-td188833.html#a188851
>>>
>>> %% Following note is moved away by DynamicText
>>> %%
>>> %% Bad behaviour goes away if the second note has no Accidental
>>> %% or \voiceTwo is used
>>> %% or if \new StaffGroup is deleted or replaced by \new ChoirStaff
>>> %% \new GrandStaff does not work as well, though
>>> %%
>>> %% Worked fine with "2.18.2"
>>>
>>> \version "2.19.38"
>>
>> Is the cause known or should I try to bisect it to a particular commit?
>
> Cause unknown.
> Can't track down it myself yet, my regular job's calling :(

That list of concerned contexts sounds sort-of familiar.

Conceivable that it is

commit 9edf3715c2b2cca09785dcd015724ad3c29cba8a
Author: David Kastrup <address@hidden>
Date:   Thu Dec 26 16:07:50 2013 +0100

    Issue 621: Dynamics should avoid cross-staff BarLines
    (e.g. GrandStaff, PianoStaff etc)
    
    Dynamics usually have extra-spacing-width set to an empty interval so
    that their placement does not cause other elements to shift.
    
    With span bars, however, the resulting overlap is a worse cure than
    the problem.  So this switches off the width-hiding setting of
    extra-spacing-width inside of staff groups using span bars by default.
    No extra space is allocated, so dynamics will clear the span bars only
    narrowly, a reasonable compromise.

which would be version 2.19.0?


It would affect GrandStaff, PianoStaff, StaffGroup.  And its description
very much seems to match the reported problem.

If this is indeed the culprit: do we have better options of addressing
issue 621?

-- 
David Kastrup