bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Manual beaming over rests and vertical spacing problem


From: Federico Bruni
Subject: Re: Manual beaming over rests and vertical spacing problem
Date: Sun, 10 Mar 2013 23:54:14 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130215 Thunderbird/17.0.3

Il 10/03/2013 20:00, Clément ha scritto:
I'm not top posting.

Hello,

Using oneVoice position (or indirectly, partcombineApart) while making a beam go
over a rest destroys vertical alignment in a staff.


I can see that in the first staff, where you've used manual beams, the dynamic signs and the reharsal mark are slightly more distant from the other objects comparing with the second staff (where you let the automatic beaming doing its job).

I don't know if this qualifies as a bug.
I hope a developer can jump in and reply..

Here is a small example, with or without manual beaming over the rest.

%%%

\version "2.17.13"

\relative c'' {
   \voiceOne \dynamicUp f4\fz f8 f f[ r16 f] f8 f |
   \override DynamicText #'X-offset = #-3 f4\fz f8 f f[ r16 f] f8 f | \mark
\default
}

\relative c'' {
   \voiceOne \dynamicUp f4\fz f8 f f r16 f f8 f |
   \override DynamicText #'X-offset = #-3 f4\fz f8 f f r16 f f8 f | \mark
\default
}

%%%

Overriding outside-staff-priority or Y-offset is uneffective.
It also affects BarNumber's vertical position.

I encountered this bug while updating a score from an older version of lilypond,
but I cannot remember which one exactly. I think it was 2.16.


If I compile your example with v2.16, the only difference is the reharsal mark at the end of the first staff: it's as close to the staff lines as in the second staff.
So something is changed in the development of 2.17
But let's wait for some developer's opinion on this matter.

Thanks for the report
--
Federico



reply via email to

[Prev in Thread] Current Thread [Next in Thread]