Using articulate.ly and the \mark command causes barcheck failures even
when there is no fault in the music - as this file demonstrates.
Remove the \mark, and there is no failure. Or drop articulate.ly,
and there is no failure. With both, there is a failure.
This makes bar checks (and parallel mu
Comment #7 on issue 1620 by k-ohara5...@oco.net: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
(Oops, the warning from 2.12.3 is a false alarm; LilyPond starts with
channel 1 for actual sounds, so wrapping around to channel 0 does not hurt
t
Comment #6 on issue 1620 by jan.nieuwenhuizen: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
To elaborate on that; I really have no idea if this patch fixes the
problem, or not.
And, while the printing/not printing of the warning message is
Comment #5 on issue 1620 by jan.nieuwenhuizen: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
Haven't checked with 2.13.50/52, but 2.12.3 also prints warning: MIDI
channel wrapped around once.
Without the patch, the message is printed 9 times
On Tue, Apr 19, 2011 at 09:39:58PM +0200, Valentin Villenave wrote:
> Have a look at the following snippet, pretty straightforward:
...
> This compiles fine, but with any recent build you'll get a "no viable
> configuration found" warning. Since I didn't remember having
> encountered such a warnin
Greetings everybody,
I've been pulling my hair all day long on this one, I may be getting
crazy or perhaps you'll be able to reproduce this as well;
Have a look at the following snippet, pretty straightforward:
<<
\new Staff = "md" \relative c' {
r4 r8 s s2
r4 r8 s s2
r4 e, r2 |
Updates:
Labels: -Patch-new Patch-review
Comment #4 on issue 1620 by colinpkc...@gmail.com: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
Patch applied to 2.13.61 (today's git). No regtests notable, just the usual
shed-load of midi log
Comment #1 on issue 1625 by philehol...@googlemail.com: Slurs over rests
have wrong direction
http://code.google.com/p/lilypond/issues/detail?id=1625
Keith O'Hara added:
I noticed a while ago that LilyPond treats rests as if they had stems, with
the
direction of the imaginary stems being
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1625 by philehol...@googlemail.com: Slurs over rests have wrong
direction
http://code.google.com/p/lilypond/issues/detail?id=1625
Reported by MusFelix:
When a slur connects two notes that have a rest in between, the s
Updates:
Status: Fixed
Labels: fixed_2_15_0 backport
Comment #3 on issue 1624 by percival.music.ca: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
(No comment was entered for this change.)
___
Comment #5 on issue 1613 by mts...@gmail.com: Beamed stems too long when
avoiding low note in other voice
http://code.google.com/p/lilypond/issues/detail?id=1613
After the most recent round of fixes to the beam code, the problem (as
reported by Phil 5 days ago) still exists in version 2.13.
Comment #2 on issue 1624 by mts...@gmail.com: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
Fix pushed after clean regtests.
06722df9f31ec6a7b516605418d9598071544edc
___
bug-lilypond mailing
Comment #1 on issue 1624 by mts...@gmail.com: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
I'm on it, patch soon.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mail
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1624 by philehol...@googlemail.com: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
Reported by ornello:
The code below causes a segfault
\layout {
\context {
\
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #4 on issue 1502 by percival.music.ca: DOcument information in PDF
headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
(No comment was entered for this change
Updates:
Labels: -Patch-review Patch-needs_work
Comment #3 on issue 1582 by percival.music.ca: flag variants patch
http://code.google.com/p/lilypond/issues/detail?id=1582
Some concerns about this one.
___
bug-lilypond mailing list
bug-lilypon
Updates:
Status: Fixed
Labels: fixed_2_15_0 backport
Comment #6 on issue 1619 by percival.music.ca: Incorrect beam/stem
http://code.google.com/p/lilypond/issues/detail?id=1619
If you say "pushed", could you also update the tags?
___
b
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
Updates:
Labels: Patch-new
Comment #3 on issue 1620 by percival.music.ca: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Status: Fixed
Labels: backport fixed_2_15_0
Comment #9 on issue 1605 by percival.music.ca: PS -> PDF conversion fails
http://code.google.com/p/lilypond/issues/detail?id=1605
Agreed, it's in git master right now, and should be backported.
___
% Hi Frogs
% set-global-staff-size affects grace notes stem length
% seems to me that appears only on the 3rd line
\version "2.13.58"
#(set-global-staff-size 18)
\relative c' {
\appoggiatura {b16 [c16] }b4
\grace {e16 [f16] } e4
\acciaccatura {f16 [g16] }f4
\appoggiatur
On 18 April 2011 23:59, Neil Puttock wrote:
>
> \override Stem #'no-stem-extend = ##t
>
Thanks Neil!
I looked into the Internals, even in "stem-interface", but I missed it.
And now: give me an inch and I'll take a mile! ;p
The result is bad when I use \override Stem #'no-stem-extend = ##t .
Wo
22 matches
Mail list logo
