#1402 Need some way to override massive beam collisions

Next Release
open
None
1
2013-10-08
2013-09-24
No

In "Romanza" at the end of the A section, the bass line walks while the melody and middle voices kind of do the same thing repeatedly. Both Rosegarden and LilyPond do a hideous job of rendering this bar, and believe it or not LilyPond is the worse of the two by far.

In the main tab score I'm using for reference, somebody has really gone in to tweak those beams, and on the first beat of bar 15, the middle voice triplet beam has just a minuscule vestige of a stem on the G. It reads well.

I have no earthly idea how I'm going to figure out a way to make Rosegarden/LilyPond render this file well automagically, without hand editing the exported .ly, but I intend to try.

Not relevant, but here is a useful snippet for the other problem:

http://www.lilypond.org/doc/v2.16/Documentation/snippets/rhythms#rhythms-avoiding-collisions-with-chord-fingerings

OK, that took an age to dig up. Here's a snippet where they've accomplished this sort of thing:

\relative c, {

\key as \major \time 3/8 \clef bass

<< { des'8 } \ { as8[ ges16] } \ { \stemDown bes,8. \stemNeutral } >> r16
<beses des="" ges="">8 |

<< { des'8 } \ { \override Beam #'positions = #'(-2 . -5) as8[ ges16] } \ {
\stemDown bes,8. \stemNeutral } >> r16 <beses des="" ges="">8 |

<< { des'8 } \ { as8[ ges16] } \ { \stemDown \override NoteColumn

'force-hshift = #0.8 bes,8. \stemNeutral } >> r16 <beses des="" ges="">8 |

}

How to hook that Beam #'positions nonsense up in an automagic and automated way seems sketchy at best, but maybe I'll come up with something.

Discussion

    • summary: Need some way to override massive beam conflicts --> Need some way to override massive beam collisions