*The current situation*
a) Lilypond's default placement of tuplet brackets is from the stem of the
first note to the stem of the last note, if the bracket is on the stem side
(see second and fourth examples in the accompanying png file). If the tuplet
bracket is on the notehead side, the bracket ex
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:
Status: Fixed
Labels: Patch-review
Comment #3 on issue 1574 by colinpkc...@gmail.com: DOC: Need
updated/expanded documentation of percent repeat/beat slash
http://code.google.com/p/lilypond/issues/detail?id=1574
Doc entry LGTM.
__
Peter Woods wrote Thursday, April 21, 2011 9:18 PM
Thanks for pointing out these errors, Peter.
Also the beaming in the example
http://lilypond.org/doc/v2.13/Documentation/1f/lily-c1891aad.png
(bass staff, bar 29)
may not be what you wish to include in an example of what lilypond
can do.
Th
One or two quibbles with the language on this page:
" Everything looks neat and tiny, "
should this read:
" Everything looks neat and tidy,"
In the next example a motive is printed twice: "
should this read:
In the next example a motif is printed twice:
" Sibelius is their major rival and the
Thanks Carl,
yes, the issue is related to relative mode
Il giorno gio, 21/04/2011 alle 07.13 -0600, Carl Sorensen ha scritto:
>
> put an octave check on the second chord. That should solve the
> problem.
>
> 8
I made several tries but none worked.
This works:
\octaveCheck c'
\chordGlis
On 4/20/11 3:41 PM, "Federico Bruni" wrote:
> As it said here, chordGlissando is a hack:
> http://code.google.com/p/lilypond/issues/detail?id=1617
>
> However it's a nice hack so I hope this bug report will help to make it
> better.
>
> If you repeat this music two or more times, the notes o
Updates:
Labels: Patch-review
Comment #2 on issue 1626 by philehol...@googlemail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Patch that is said to fix this.
Attachments:
articulate-barcheck.patch.patch 1.8 KB
__
> "Phil" == Phil Holmes writes:
Phil> "Helge Hafting" wrote in message
Phil> news:cf93cf976a70dd40a48c64f5d4141e341ba...@ex-vs01.ad.hist.no...
>> Using articulate.ly and the \mark command causes barcheck failures
>> even when there is no fault in the music - as this file
>> demonstrates.
>>
Status: Accepted
Owner:
Labels: Type-Defect Priority-Low
New issue 1630 by philehol...@googlemail.com: Completion heads engraver
produces duplicate ties
http://code.google.com/p/lilypond/issues/detail?id=1630
Reported by Ornello:
The completion heads engraver produces duplicate ties (se
Updates:
Summary: Articulate produces faulty barcheck warnings
Comment #1 on issue 1626 by philehol...@googlemail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Spelling correction
___
Updates:
Status: Fixed
Labels: -Patch-review
Comment #8 on issue 1620 by jan.nieuwenhuizen: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
Thanks for a.ly -- using the slightly modified aa.ly, the wrapping bug is
fixed in dd213ae
12 matches
Mail list logo
