Re: improving staff-padding

> > % . `staff-padding' correctly sets the minimum distance to > > % DynamicText and DynamicLineSpanner objects. As can be seen in > > % the example below, the horizontal axis for the two objects > > % isn't aligned. I wonder whether another parameter can be > > % introduced to fine-tune

Re: rests problem

> > % . Rests belonging to a voice in a multi-voice staff are > > % incorrectly moved to the default position. IMHO, this should > > % only happen if a `skip' rest is used. > > % > > % This is a severe bug. > > % > > How far should the rests be moved? IMHO, as if a there were another rest

Re: another convert-ly problem?

> > \score { > > \notes \relative c' { > > c1 \tieUp ~ c1 > > } > > } > > > > In lilypond 2.1.15 this causes a syntax error. convert-ly doesn't > > fix this -- or this is a bug in lilypond 2.1.15 instead? > > This case is hard to catch, sorry. Write > > \tieUp > c~ c

rests problem

[EMAIL PROTECTED] writes: > > % > % This file shows a problem with rests in multi-voice staves in lilypond > % CVS 2004-01-27 07:18 MET. > % > % . Rests belonging to a voice in a multi-voice staff are incorrectly > % moved to the default position. IMHO, this should only happen if > % a `skip'

another convert-ly problem?

[EMAIL PROTECTED] writes: > > The following input was possible with lilypond 1.6.5: > > \score { > \notes \relative c' { > c1 \tieUp ~ c1 > } > } > > In lilypond 2.1.15 this causes a syntax error. convert-ly doesn't > fix this -- or this is a bug in lilypond 2.1.15 instead?

another convert-ly problem?

The following input was possible with lilypond 1.6.5: \score { \notes \relative c' { c1 \tieUp ~ c1 } } In lilypond 2.1.15 this causes a syntax error. convert-ly doesn't fix this -- or this is a bug in lilypond 2.1.15 instead? Werner ___

rests problem

% % This file shows a problem with rests in multi-voice staves in lilypond % CVS 2004-01-27 07:18 MET. % % . Rests belonging to a voice in a multi-voice staff are incorrectly % moved to the default position. IMHO, this should only happen if % a `skip' rest is used. % % This is a severe bug.

Re: widening measures with rests

[EMAIL PROTECTED] writes: > > > Jan Nieuwenhuizen wrote: > > Mats Bengtsson writes: > > > > > >>Question to those understanding the LilyPond internals better than I do: > >> > >>Why doesn't > >>\property Voice.MultiMeasureRestText \set #'no-spacing-rods = ##f > >>do the same job? Doesn't it wor

Re: widening measures with rests

Jan Nieuwenhuizen wrote: Mats Bengtsson writes: Question to those understanding the LilyPond internals better than I do: Why doesn't \property Voice.MultiMeasureRestText \set #'no-spacing-rods = ##f do the same job? Doesn't it work together with spanners, or? You mean = ##t, right? Comparing

improving staff-padding

[EMAIL PROTECTED] writes: > > % > % This file shows a problem with the `staff-padding' property in lilypond > % CVS 2004-01-27 07:18 MET. > % > % . `staff-padding' correctly sets the minimum distance to DynamicText > % and DynamicLineSpanner objects. As can be seen in the example below, > % t

beam positioning buglet

% % This file shows a problem with beam positioning in lilypond % CVS 2004-01-27 07:18 MET. % % . Beams get different vertical offsets in spite of covering the same % interval. I wonder which parameter can be fine-tuned to avoid this % artifact. IMHO the rightmost stem of the left beam is to

improving staff-padding

% % This file shows a problem with the `staff-padding' property in lilypond % CVS 2004-01-27 07:18 MET. % % . `staff-padding' correctly sets the minimum distance to DynamicText % and DynamicLineSpanner objects. As can be seen in the example below, % the horizontal axis for the two objects isn