severe bug: broken ties too short
\version "2.13.4"
\header { texidoc = "
A broken tie must not degenerate to a dot-like shape if a staff starts
with a time signature, and the tied chord has accidentals.
This is a really severe bug.
" }
\paper {
ragged-right = ##t
}
\relative {
1 ~ \break
\time 3/4 2.
}
% EOF
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \RemoveEmptyStaffContext and cross-staff beams
I can see the problem you report with version 2.12, but with the latest
2.13 version (compiled from todays GIT), it's even worse, since the beam
stays flat also if you don't have \RemoveEmptyStaffContext.
I haven't tracked down exactly what has changed, but I had to reduce the
setting of the auto-knee-gap property of Beam from the default value 5.5 to
\override Score.Beam #'auto-knee-gap = #4.75
to get the kneed beam that was obtained in earlier versions.
Regression bug!(?)
On the other hand, the problem you report has been in LilyPond for a
very long time and seems to date back to
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=17332ae36b238193723983455a91366be4e88e0b
I'm not sure why Han-Wen added this setting in the definition of
\RemoveEmptyStaffContext, but he probably had a good reason. The
question is if the same reason still applies or if it would work to
allow kneed beams also in \RemoveEmptyStaffContext. If somebody is
interested to try it out, just use
\layout {
\context {
\RemoveEmptyStaffContext
\override Beam #'auto-knee-gap = #4.75
}
}
and check if anything breaks. There doesn't seem to be any regression
test on the combination of \RemoveEmptyStaffContext and kneed beams, so
you would have to invent some yourself.
/Mats
Jonathan Wilkes wrote:
Hello,
In the following code, the beam goes between the staves when
\RemoveEmptyStaffContext is commented out but goes above the top
staff when it's used.
This means you have to explicitly state all the stem directions to
get the beam to go in the middle of the staves when using \RemoveEmptyStaffContext.
Is this a bug?
-Jonathan
Snippet below:
\version "2.13.3"
staffPiano = \new PianoStaff {
<<
\new Staff = "rh" { \relative c' {
c8[ c c c \change Staff = "lh" g, g g g]
}
}
\new Staff = "lh" { \relative c {
\clef bass
c1
}
}
>>
}
\score {
\staffPiano
}
\layout {
\context {
\RemoveEmptyStaffContext
}
}
___
lilypond-user mailing list
lilypond-u...@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengts...@ee.kth.se
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \RemoveEmptyStaffContext and cross-staff beams
On Wed, Sep 23, 2009 at 10:35 AM, Mats Bengtsson wrote: > There doesn't seem to be any regression test > on the combination of \RemoveEmptyStaffContext and kneed beams, so you would > have to invent some yourself. Yeah, I was supposed to add one last year but I forgot :-) http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00019.html Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: severe bug: broken ties too short
On Wed, Sep 23, 2009 at 9:46 AM, Werner LEMBERG wrote: > This is a really severe bug. Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=840 Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 840 in lilypond: broken ties too short when time signature changes
Status: Accepted
Owner: v.villenave
CC: lemzwerg
Labels: Type-Defect Priority-Medium
New issue 840 by v.villenave: broken ties too short when time signature
changes
http://code.google.com/p/lilypond/issues/detail?id=840
New report from Werner:
% A broken tie must not degenerate to a dot-like shape if
% a staff starts with a time signature, and the tied chord
% has accidentals.
% This is a really severe bug.
\version "2.13.4"
\paper {
ragged-right = ##t
}
\relative {
1 ~ \break
\time 3/4 2.
}
Attachments:
without_timesig.png 3.4 KB
with_timesig.png 4.1 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \RemoveEmptyStaffContext and cross-staff beams
2009/9/23 Mats Bengtsson :
> I haven't tracked down exactly what has changed, but I had to reduce the
> setting of the auto-knee-gap property of Beam from the default value 5.5 to
> \override Score.Beam #'auto-knee-gap = #4.75
> to get the kneed beam that was obtained in earlier versions.
> Regression bug!(?)
The staves are slightly closer together due to Joe's new spacing code,
so it's probably just a case of tweaking the default value for
'auto-knee-gap.
> On the other hand, the problem you report has been in LilyPond for a very
> long time and seems to date back to
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=17332ae36b238193723983455a91366be4e88e0b
> I'm not sure why Han-Wen added this setting in the definition of
> \RemoveEmptyStaffContext, but he probably had a good reason.
There's a message in the deleted bug snippet harakiri-autoknee.ly
which suggests there used to be a problem:
Autoknee-ing triggers hara-kiri too early.
Here's the same snippet updated, which compiles fine under current master:
\version "2.13.4"
\score {
\relative c''' {
\new PianoStaff <<
\context Staff = up {
c4 c c c \break
c4 c c c
}
\context Staff = mid {
c4 c c c \break
s1
}
\context Staff = down {
c8
\change Staff = mid
c8
\change Staff = down
c8 c c4 c
c4 c c c
}
>>
}
\layout {
\context {
\RemoveEmptyStaffContext
\revert Beam #'auto-knee-gap
}
}
}
Regards,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
