Re: [Gnu-music-discuss] Missing legal.ly, beam questions, padding...

[Mats Bengtsson]

> There doesn't seem to be anyway to indicate how one wants these inner
> beams done, I have auto beaming turned off, but adding []'s inside of
> []'s gives a warning 'already has a beam' and, in the second case,
> leads to worse results. These seems to me to be an important problem,
> since it's not just a question of  'prettiness', but actually affects
> how the music will be performed.

Take a look at the properties stemLeftBeamCount and
stemRightBeamCount.

> I'm following the coriolan-part numbers for padding, but there are
> some problems. When the line starts with a bass clef, the measure
> numbers are fine. When the line begins with a treble clef, they need
> to be raised, since the treble clef  prints over the number. But with
> padding, the opposite situation occurs, the numbers are too high when
> the bass clef is there.

You could set the property separately for the different
staff lines (hope you don't have too many clef changes 
in the parts). Of course, Lilypond should take the 
clef into account when it calculates the spacing.