Updates:
Status: Verified
Comment #27 on issue 1612 by philehol...@googlemail.com: Change staff
produces long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Labels: -backport fixed_2_13_62
Comment #26 on issue 1612 by carl.d.s...@gmail.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
The following patches were backported to affect beam collision:
275ef7f1fdbe Fixes bug with covered_gro
Updates:
Status: Fixed
Comment #25 on issue 1612 by colinpkc...@gmail.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Unverified in 2.13.61
___
bug-lilypond mailing list
bug-lilypond@gnu.org
ht
Updates:
Status: Verified
Comment #24 on issue 1612 by colinpkc...@gmail.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Verified 2.15.0 (the original report)
___
bug-lilypond mailing list
bug-
Updates:
Status: Fixed
Labels: fixed_2_15_0 backport
Comment #23 on issue 1612 by k-ohara5...@oco.net: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
The original example (not comment 17 which is moved to issue 1632) started
working
On 5/2/11 7:48 AM, "m...@apollinemike.com" wrote:
> On May 2, 2011, at 5:21 AM, lilyp...@googlecode.com wrote:
>
>>
>> Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
>> http://code.google.com/p/lilypond/issues/detail?id=1612
>>
>> I have missed something very pr
On May 2, 2011, at 5:21 AM, lilyp...@googlecode.com wrote:
>
> Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
> http://code.google.com/p/lilypond/issues/detail?id=1612
>
> I have missed something very probably, but: this issue is of type "Collision"
> (not "Doc") st
Comment #22 on issue 1612 by byu9...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Once things have settled down, I'll backport the whole set. But I'm
waiting a bit.
Thanks,
Carl
___
bug
Comment #21 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I'm guessing that my comment 18 about "already pushed his patches" is
referring to some subset (not necessarily a proper subset, though) of:
275ef7f1fdbe
Updates:
Status: Accepted
Labels: -fixed_2_13_61
Comment #20 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
"what's wrong"? What's wrong is that the initial snippet causes the same
problem in the
Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I have missed something very probably, but: this issue is of
type "Collision" (not "Doc") still _and_ the initial snippet produces the
very same picture with 2.
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_13_61
Comment #18 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Hmm. Mike already pushed his patches, so let's make comment 17 into
another is
Comment #17 on issue 1612 by n.putt...@gmail.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Unfortunately, Mike's patch doesn't fix these cases (they're probably a
related, but separate bug):
<<
\new Staff = up \relative c' {
c8 c c c
Updates:
Labels: -Patch-new Patch-review
Comment #16 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Clean regtests,
___
bug-lilypond mailing list
bug-lilypond@gn
Updates:
Labels: -Patch-review Patch-new
Comment #15 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
New patches from Mike here:
http://codereview.appspot.com/4423062/
http://codereview.appspot.com/4431058/
Updates:
Labels: -Patch-new Patch-review
Comment #14 on issue 1612 by colinpkc...@gmail.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Doc entry LGTM, no regressions.
___
bug-lilypond mailing
Updates:
Labels: Patch-new
Comment #13 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug
Comment #12 on issue 1612 by k-ohara5...@oco.net: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Switching off beam-collision-prevention for cross-staff beams seems very
sensible.
Generally, collision-prevention is turned off for cross-staff graph
Comment #11 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
maybe we should just switch off beam collisions for x-staff beams.
___
bug-lilypond mailing list
bug-lilypond@
Comment #10 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
actually, we may have to ponder a bit more how to do collisions. I think
manual changes may also be fubar'd when the voice changes mid-beam, and the
ot
Comment #9 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Do I understand correctly that lilypond can no longer handle staff changes
with automatic beaming?
If so, then I think this should be noted in the change
Comment #8 on issue 1612 by pkx1...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
@knownissue added for acceptance/rejection
http://codereview.appspot.com/4440041/
___
bug-lilypond mailing lis
Comment #7 on issue 1612 by m...@apollinemike.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I propose, then, that we downgrade this to `high' with a @knownissues in
the docs suggesting manual beams and a NOT_SMART convert-ly rule telling
peo
Comment #6 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
just as an extra clarification: the auto beam engraver only knows if it can
emit a beam after the timestep has already passed, so "LilyPond to cleanly
I
Comment #5 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
another heuristic is to guess a stem length rather than infinity. I'm a
bit worried that this leads to a lot of other corner cases, though.
___
Comment #4 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
One simple solution is to switch off beam collisions for automatic beams.
reduced snippet:
\version "2.13.58"
<<
\new Staff{
\clef treble
\time 2
Comment #3 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
the autobeam engraver will emit the beam at after the staff switch has
occurred, so the top beam will appear to be in the bottom staff (although
from a t
Comment #2 on issue 1612 by m...@apollinemike.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
More news.
When one beams these beams manually, the problem goes away (and the beam is
correctly identified as not being cross staff).
I would recomm
Comment #1 on issue 1612 by m...@apollinemike.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
This seems like it needs to be fixed in the Beam_collision_engraver such
that the notes on the lower staff never enter into the equation.
After putti
Status: Accepted
Owner:
Labels: Type-Collision Priority-Critical Regression
New issue 1612 by philehol...@googlemail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
The code below produces excessively long stems. This was not present in
2.
30 matches
Mail list logo
