On Tue, Apr 19, 2011 at 9:44 PM, Graham Percival
gra...@percival-music.ca wrote:
Well, the actual message (with 2.13.57) is:
warning: no viable initial configuration found: may not find good
beam slope
Yep, what you said.
The cross-staff beams look a bit odd (the first note has a really
Updates:
Labels: -Patch-needs_work Patch-review
Comment #2 on issue 1607 by percival.music.ca: patch for mandolin freboard
diagrams
http://code.google.com/p/lilypond/issues/detail?id=1607
new location:
http://codereview.appspot.com/4370054/
On Wed, Apr 20, 2011 at 4:56 AM, Valentin Villenave
valen...@villenave.net wrote:
The cross-staff beams look a bit odd (the first note has a really
long stem).
I'm surprised that there's problems as far back as 2.13.7, since
the main beaming work was quite recent.
Indeed. I suspect the
That said, the following code still produces the same message:
\version 2.13.59
\new Staff = md \relative c' {
r4 r8 s s2
r4 r8 s s2
r4 e, r2 |
}
\new Staff = mg \relative c'' {
b8 f' c' \change Staff = md g, c f~
g c f2 \change Staff = mg |
\once \override Beam
Status: Accepted
Owner:
Labels: Type-Scripts Priority-Medium
New issue 1626 by philehol...@googlemail.com: Atriculate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Reported by Helge Hafting
Using articulate.ly and the \mark command causes
Helge Hafting helge.haft...@hist.no wrote in message
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.
Remove the \mark, and there is no
On Tue, Apr 19, 2011 at 5:56 AM, Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com wrote:
% 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' {
Status: Accepted
Owner:
Labels: Type-Collision Priority-Low
New issue 1628 by ralphbug...@gmail.com: Fingerings collide with slurs when
used in
http://code.google.com/p/lilypond/issues/detail?id=1628
Fingerings stop avoiding slurs when they are placed within a chord ... or
even a
On Wed, Apr 20, 2011 at 11:53 AM, lilyp...@googlecode.com wrote:
Status: Accepted
Owner:
Labels: Type-Collision Priority-Low
New issue 1628 by ralphbug...@gmail.com: Fingerings collide with slurs
when used in
http://code.google.com/p/lilypond/issues/detail?id=1628
Fingerings stop
In this snippet the triplet line collides with the fingering.
\version 2.13.60
\language english
Violin = \relative d'' {
\times 2/3{d4 a8-4}
}
\score {
\new Staff { \Violin }
\layout {}
}
attachment: PastedGraphic-2.png___
bug-lilypond mailing
On Wed, Apr 20, 2011 at 4:53 PM, Ralph Palmer ralphbugl...@gmail.comwrote:
In this snippet the triplet line collides with the fingering.
\version 2.13.60
\language english
Violin = \relative d'' {
\times 2/3{d4 a8-4}
}
\score {
\new Staff { \Violin }
\layout {}
}
I had trouble
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 of the first chord
are raised by one octave each time:
I changed the direction of the TupletBracket but now it collides with the slur!
Shouldn't lilypond adapt the length of the bracket and the starting point of
the slur?
\version 2.13.60
\language english
Violin = \relative d' {
\key d \major
\once \override TupletBracket #'direction = #DOWN
13 matches
Mail list logo
