I'm forwarding this to the bug-lilypond@gnu.org, so our Bug Squad won't miss
it.
cheers,
Janek
2011/3/31 胡海鹏 - Hu Haipeng
> Hello,
> I found a problem of Midi output in 2.13.56. If you write a timpani roll
> like this:
> \repeat tremolo 4 c32\mp\< \repeat tremolo 8 c c8\!f
> and use unfold in
Comment #3 on issue 795 by mts...@gmail.com: Beams do not take grace notes
into account
http://code.google.com/p/lilypond/issues/detail?id=795
http://codereview.appspot.com/4337045/ fixes this.
Attachments:
beam-collision-beamcount.png 3.1 KB
_
Updates:
Labels: Patch-needs_work
Comment #2 on issue 795 by colinpkc...@gmail.com: Beams do not take grace
notes into account
http://code.google.com/p/lilypond/issues/detail?id=795
Beams are avoiding stems, but still colliding with noteheads, in
beam-collision-beamcount.ly
_
Status: Accepted
Owner:
Labels: Type-Other Priority-Low website
New issue 1588 by percival.music.ca: optimizing lilypond.org speed
http://code.google.com/p/lilypond/issues/detail?id=1588
Various tips here:
http://pagespeed.googlelabs.com/#url=lilypond.org&mobile=false
___
Comment #1 on issue 1585 by percival.music.ca: LilyPond segfaults on beams
with headless stencils
http://code.google.com/p/lilypond/issues/detail?id=1585
According to my trusty printf, it seems like queue.top() is dying:
lily/beam-quanting.cc
// line 483
while (true) {
printf("zzz ccc
Updates:
Status: Fixed
Comment #2 on issue 1587 by jan.nieuwenhuizen: midi2ly --key option only
reaches first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
Fixed in 928bfc5.
___
bug-lilypond mailing list
bug-lilypond@gnu.or
Comment #1 on issue 1587 by jan.nieuwenhuizen: midi2ly --key option only
reaches first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
Here's the result
Attachments:
key-option-all-staves-midi.png 12.5 KB
___
bug-lilypond m
Status: Accepted
Owner:
Labels: Type-Defect
New issue 1587 by jan.nieuwenhuizen: midi2ly --key option only reaches
first staff
http://code.google.com/p/lilypond/issues/detail?id=1587
When setting the key in midi2ly using --key, this key
signature is only printed on the first staff.
See
Updates:
Status: Verified
Comment #10 on issue 400 by colinpkc...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Verified with 2.13.57
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.
Updates:
Status: Verified
Comment #13 on issue 76 by colinpkc...@gmail.com: beams should not collide
with accidentals
http://code.google.com/p/lilypond/issues/detail?id=76
Verified with 2.13.57
___
bug-lilypond mailing list
bug-lilypond@gn
Updates:
Status: Fixed
Comment #12 on issue 76 by mts...@gmail.com: beams should not collide with
accidentals
http://code.google.com/p/lilypond/issues/detail?id=76
Fixed with the newest beam-collision-engraver
Attachments:
foo.png 1.4 KB
___
Updates:
Status: Fixed
Comment #9 on issue 400 by mts...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Removed with the beam collision engraver (version 2.13.57).
Attachments:
foo.png 1.1 KB
_
Comment #1 on issue 795 by mts...@gmail.com: Beams do not take grace notes
into account
http://code.google.com/p/lilypond/issues/detail?id=795
Better with the beam collision engraver, but still buggy.
Attachments:
foo.png 1.3 KB
___
bug-
Comment #1 on issue 1586 by percival.music.ca: midi cresc happens instantly
http://code.google.com/p/lilypond/issues/detail?id=1586
(No comment was entered for this change.)
Attachments:
foo.midi 169 bytes
___
bug-lilypond mailing list
bug-
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=1586
Note that I created a Tiny example for this.
Cheers,
- Graham
On 3/31/11, Phil Holmes wrote:
>
>
> --
> Phil Holmes
>
>
> - Original Message -
> From: 胡海鹏 - Hu Haipeng
> To: lilypond-user
> Sent: Wednesday, March 3
Status: Accepted
Owner:
Labels: Priority-Critical Type-Defect
New issue 1586 by percival.music.ca: midi cresc happens instantly
http://code.google.com/p/lilypond/issues/detail?id=1586
% the MIDI note velocities are 53 90 90 90 ; that doesn't look
% like a crescendo to me.
%
% there is an un
Updates:
Status: Verified
Comment #6 on issue 742 by percival.music.ca: Delayed ties influence lyrics
(even with tieWaitForNote unset)
http://code.google.com/p/lilypond/issues/detail?id=742
ok
___
bug-lilypond mailing list
bug-lilypond@gnu
Updates:
Status: Accepted
Owner: jan.nieuwenhuizen
Comment #6 on issue 1534 by percival.music.ca: midi2ly does not show \breve
or if a note lasts longer than one bar
http://code.google.com/p/lilypond/issues/detail?id=1534
But the whole notes have 1*2, which means that they _sh
Status: Accepted
Owner: mts...@gmail.com
Labels: Type-Defect Priority-Critical
New issue 1585 by mts...@gmail.com: LilyPond segfaults on beams with
headless stencils
http://code.google.com/p/lilypond/issues/detail?id=1585
This segfaults:
{
\override Voice . NoteHead #'stencil = ##f
\repeat u
should not all header items behave the same? at least they did earlier - with
copyright = #f i had no error before version 2.13.48!
\version "2.13.56"
\header {
% works only with ##f
title = ##f
subtitle = ##f
copyright = ##f
poet = ##f
composer = ##f
arranger = ##f
% works with
"Friedrich Fischer" wrote in message
news:loom.20110331t093249-...@post.gmane.org...
I'm not top posting.
% stems to long and to short
\version "2.13.51"
\new Staff {
\time 3/8
\key a \major
\clef "treble_8" {
<<
{ 16 e'32 e'' eis'[ eis'' fis' fis''] g' g'' gis' gis'' }
\\
{ e,4 r8 }
}
}
W
Comment #5 on issue 742 by tdaniels...@googlemail.com: Delayed ties
influence lyrics (even with tieWaitForNote unset)
http://code.google.com/p/lilypond/issues/detail?id=742
I currently see: one () two three
Is that intended?
This test file has incorrect syntax. A tied note is not
--
Phil Holmes
- Original Message -
From: 胡海鹏 - Hu Haipeng
To: lilypond-user
Sent: Wednesday, March 30, 2011 11:18 PM
Subject: Critical bug of midi output
Hello,
I found a problem of Midi output in 2.13.56. If you write a timpani roll like
this:
\repeat tremolo 4 c32\mp\< \repea
Comment #1 on issue 1584 by d...@gnu.org: removing parser DIGIT rule
http://code.google.com/p/lilypond/issues/detail?id=1584
With regard to "magically works": that would have been my initial regtest.
However, after repeating the regtest, I can corroborrate that the patch
fails in the manner
> I'm not top posting.
% stems to long and to short
\version "2.13.51"
\new Staff {
\time 3/8
\key a \major
\clef "treble_8" {
<<
{ 16 e'32 e'' eis'[ eis'' fis' fis''] g' g'' gis' gis'' }
\\
{ e,4 r8 }
>>
}
}
___
bug-lilypond mailing list
bug-lilypond@
25 matches
Mail list logo
