[Top][All Lists]

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

Re: Stave drawing behavior after a key change without following notes ch

From: Jean Abou Samra
Subject: Re: Stave drawing behavior after a key change without following notes changed in 2.19.16
Date: Wed, 5 Oct 2022 21:44:39 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1

Le 05/10/2022 à 21:30, Tobias Leupold a écrit :
Hi all!

After quite some time, I re-rendered some of my Lilypond sheets and tried to
update them from some 2.18 version to Gentoo's current stable 2.22.0.

I noticed that after a key change without following notes, the stave is no
longer drawn under the following signs.

I tracked this down, it happened with version 2.19.16.

Here's a minimalistic example to reproduce it:

     \version "2.19.15"
\score {
         \new Staff {
                 \key g \major c'1 \key a \major

This is still rendered correctly using version 2.19.15, cf. the attached
lilypond-2.19.15.png screenshot.

With version 2.19.16, the stave is no longer extended behind the bar
(compiling the same code, but with '\version "2.19.16"' set), cf. the
lilypond-2.19.16.png screenshot.

This still happens with version 2.22.2.

So ... is this a bug, or is this a feature?! I would not have expected
something like this to happen in a bugfix release, and I also didn't find any
change documentation about this ...

If this was intended then sorry for the spam; but how can I get the old (way
more meaningful) behavior back? If not: How can this be worked around?

Thanks for all help and/or fixes!

This change was intended.

commit 05ecaef595f5aff1de3f46edde90a0644a81e957
Author: David Kastrup <dak@gnu.org>
Date:   Sat Oct 4 01:12:55 2014 +0200

    Issue 660: ossia staff doesn't stop at correct horizontal position

This was done to fix

If you look at the pictures on the issue, you can see that
what seems more logical to you at the end of the piece
becomes less logical if the staff stops mid-piece, for
example if it is an ossia staff, or if you are just
changing the type of staff, as in

\version "2.22.2"

\new OneStaff {
    \new Staff { c'1 }
  \new RhythmicStaff { c'1 }

Nevertheless, it is possible to get the old behavior using

\version "2.22.2"

\layout {
  \context {
    \override StaffSymbol.break-align-symbols = #'(break-alignment)

\score {
  \new Staff {
          \key g \major c'1 \key a \major

Finally, 2.19.16 was not a bugfix release. LilyPond uses a versioning
scheme where x.y.z versions with y even are stable versions, and with
y odd are unstable versions. So this was just a development release in
the release cycle between the stable releases 2.18 and 2.20.


reply via email to

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