[Sending to lilypond-devel also (with modifications) since I believe
this needs improvement in the documentation.]
> What can I do to improve the formatting? Note that globally
> increasing the distance between the staves is not a possible
> solution since this would ruin the layout of the whol
>> That said, this case is particularly thorny. To fix it, you could
>> add an invisible text spanner above the beam with the gs, for
>> example.
>
> Good idea, thanks! Will try soon.
Mhmm, this sort-of helps because there are other beams where the
beam-spanner collision algorithm works. Howe
On 12 févr. 2013, at 09:19, Werner LEMBERG wrote:
>
>>> There is an ugly clash between the two beams. Due to the
>>> cross-staff beam, this is sort-of expected. However, I wonder
>>> whether this can be improved: Isn't it possible to make the beaming
>>> algorithm simply ignore cross-staff ste
>> There is an ugly clash between the two beams. Due to the
>> cross-staff beam, this is sort-of expected. However, I wonder
>> whether this can be improved: Isn't it possible to make the beaming
>> algorithm simply ignore cross-staff stems so that the beam gets a
>> proper skyline?
>
> All of
On 12 févr. 2013, at 07:21, Werner LEMBERG wrote:
>
> Folks,
>
>
> consider this real-life example (omitting the unimportant voices).
>
> <<
>\new Staff = "R" \relative c' {
> \voiceTwo
> d16[ b
>\change Staff = "L" \stemUp
>g
>\change Staff = "R" \stem
Folks,
consider this real-life example (omitting the unimportant voices).
<<
\new Staff = "R" \relative c' {
\voiceTwo
d16[ b
\change Staff = "L" \stemUp
g
\change Staff = "R" \stemDown
b d b]
}
\new Staff = "L" \relative c' {
\c
