Comment #1 on issue 1607 by carl.d.s...@gmail.com: patch for mandolin
freboard diagrams
http://code.google.com/p/lilypond/issues/detail?id=1607
Issue is now posted on Rietveld for review.
http://codereview.appspot.com/4384055/
Thanks,
Carl
___
Comment #2 on issue 1604 by percival.music.ca: MultiMeasureRest staff
position 0 is taken as staff position 2
http://code.google.com/p/lilypond/issues/detail?id=1604
Issue 1608 has been merged into this issue.
___
bug-lilypond mailing list
bug-lil
Updates:
Status: Duplicate
Labels: -Patch-new
Mergedinto: 1604
Comment #3 on issue 1608 by percival.music.ca: patch to prevent rests from
shifting
http://code.google.com/p/lilypond/issues/detail?id=1608
yep, it's a dupe.
__
On Sun, Apr 10, 2011 at 10:06:52PM -0600, Colin Campbell wrote:
> My fault, Graham. I raised issue 1604 last night, and Mike posted a
> patch on reitveld in response, this morning. Unusually for Mike,
> bless his productive cotton socks, his posting on -devel actually
> referred to 1604.
Whoops.
On 11-04-10 09:36 PM, lilyp...@googlecode.com wrote:
Updates:
Status: Accepted
Labels: Patch-new
Comment #2 on issue 1608 by percival.music.ca: patch to prevent rests
from shifting
http://code.google.com/p/lilypond/issues/detail?id=1608
err, really? I don't see any patch for issue 16
Updates:
Labels: Patch-needs_work
Comment #1 on issue 1604 by colinpkc...@gmail.com: MultiMeasureRest staff
position 0 is taken as staff position 2
http://code.google.com/p/lilypond/issues/detail?id=1604
Mike Solomon has proposed a patch against this issue:
http://codereview.appspot
Updates:
Status: Accepted
Labels: Patch-new
Comment #2 on issue 1608 by percival.music.ca: patch to prevent rests from
shifting
http://code.google.com/p/lilypond/issues/detail?id=1608
err, really? I don't see any patch for issue 1604. If this patch is
supposed to fix that
Updates:
Status: Duplicate
Labels: -Patch-new
Comment #1 on issue 1608 by colinpkc...@gmail.com: patch to prevent rests
from shifting
http://code.google.com/p/lilypond/issues/detail?id=1608
Already added as 1604
___
bug-lilypond ma
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium Patch-new
New issue 1608 by percival.music.ca: patch to prevent rests from shifting
http://code.google.com/p/lilypond/issues/detail?id=1608
http://codereview.appspot.com/4385053/
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium Patch-needs_work
New issue 1607 by percival.music.ca: patch for mandolin freboard diagrams
http://code.google.com/p/lilypond/issues/detail?id=1607
http://lists.gnu.org/archive/html/lilypond-devel/2011-04/msg00121.html
This pa
hello,
.
On 10 Apr 2011, at 17:18, "Friedrich Fischer"
mailto:fried.fisc...@gmail.com>> wrote:
This time the stems are really much too long!
Regards FF
\version "2.13.59"
\new Staff {
\time 6/8
\key a \major
\clef treble
<<
{ 4 d'''16 b'' e'''4. }
\\
{ d'4. e }
\\
\\
{ s
Comment #1 on issue 1606 by philehol...@googlemail.com: Slurs avoid
collision with beam better than ties
http://code.google.com/p/lilypond/issues/detail?id=1606
Nick subsequently commented:
Actually, with a bit more poking around I've found that I did actually have
\override Fingering #'avo
Patch at
http://codereview.appspot.com/4390042>
Check the warnings output from the regression test file in there:
\version "2.13.59"
\header {
texidoc = "
Combine several kinds of stems in parallel voices.
"
}
\new Voice { \time 4/1
<< c'\breve e'8 >>
<< c'8 e'\br
This time the stems are really much too long!
Regards FF
\version "2.13.59"
\new Staff {
\time 6/8
\key a \major
\clef treble
<<
{ 4 d'''16 b'' e'''4. }
\\
{ d'4. e }
\\
\\
{ s4 s8}
>>
}
--
View this message in context:
http://old.nabble.com/stemle
"胡海鹏 - Hu Haipeng" wrote in message
news:17bcd0f5.477.12f2f5a09fb.coremail.hhpmu...@163.com...
Hello,
Lilypond 2.13.58 still has bug on mid output. Because the max number of
instr is 16, and now the midi output considers every instr instead of
track as an item, the result of program change still
"胡海鹏 - Hu Haipeng" wrote in message
news:17bcd0f5.477.12f2f5a09fb.coremail.hhpmu...@163.com...
Hello,
Lilypond 2.13.58 still has bug on mid output. Because the max number of
instr is 16, and now the midi output considers every instr instead of
track as an item, the result of program change sti
Comment #1 on issue 1605 by bordage@gmail.com: PS -> PDF conversion
fails
http://code.google.com/p/lilypond/issues/detail?id=1605
This commit is the cause : eab591fe423ef0eeb03d8bbedf7d43185d2fbc74
It seems that metadata-lookup-output doesn't handle parentheses that are
not closed.
Th
Status: Accepted
Owner:
Labels: Type-Collision Priority-Low
New issue 1606 by philehol...@googlemail.com: Slurs avoid collision with
beam better than ties
http://code.google.com/p/lilypond/issues/detail?id=1606
Reported by Nick Payne:
See image. If I have a tie between the two Gs in the
Comment #2 on issue 480 by philehol...@googlemail.com: collision: tie after
line break with sharp/natural accidental
http://code.google.com/p/lilypond/issues/detail?id=480
Magnified image added. Pretty minor collision.
Attachments:
TieCollision.png 2.7 KB
On 10 April 2011 14:06, Phil Holmes wrote:
>
> David has explained the layout issue. What is the problem with the midi,
> please?
I see \version "2.13.33" in the bug report.
Javier, please consider upgrading to the latest development release
(2.13.59) to test the MIDI.
There have been major c
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1605 by philehol...@googlemail.com: PS -> PDF conversion fails
http://code.google.com/p/lilypond/issues/detail?id=1605
In the following file, the closing parenthesis has become a curly bracket,
and the PS -
"Nick Payne" wrote in message
news:4da16be1.7010...@internode.on.net...
See below. If I have a tie between the two Gs in the top voice, it
collides with the beam. If I fake the tie with a slur, it automatically
avoids the beam.
\version "2.13.58"
\relative c'' {
<< { g'2 ~ g }
\\ { s1 }
"Javier Ruiz" wrote in message
news:loom.20110410t035412-...@post.gmane.org...
I'm not top posting.
%{
Starting a piece with grace notes on one staff, or the beginning of a
\repeat volta block, will cause undesired formatting (adds extra clef,
extra set of time signagures, key is offset)
plus .
On Sun, Apr 10, 2011 at 11:23 AM, Federico Bruni wrote:
> (BTW, who maintain the LSR?)
I'll have a look. Thanks!
Valentin.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi,
I've seen an error in a snippet in NR 2.4.1, Default tablature:
http://lilypond.org/doc/v2.13/Documentation/notation/common-notation-for-fretted-strings#default-tablatures
The section is Slides in tablature.
There are two errors actually:
- last two 5 and 7 frets are printed badly (because
See below. If I have a tie between the two Gs in the top voice, it
collides with the beam. If I fake the tie with a slur, it automatically
avoids the beam.
\version "2.13.58"
\relative c'' {
<< { g'2 ~ g }
\\ { s1 }
\\ { b,8 g a b ~ b a b a }
\\ { g,2 g }
>>
}
\relative c'' {
<< {
Comment #2 on issue 1542 by reinhold...@gmail.com: [PATCH] Add
springs-and-rods callback to DynamicTextSpanner, so minimum-length has an
effect (issue4187054)
http://code.google.com/p/lilypond/issues/detail?id=1542
Added minimum-length (Neil's concern) and pushed.
27 matches
Mail list logo
