Issue 525: repeat tremolo can't force stem downs
http://code.google.com/p/lilypond/issues/detail?id=525
Comment #1 by v.villenave:
Hi, I just wanted to add that this un-stemDown-able tremolo can produce
very ugly
collisions:
\relative {
<< { r4 f'2. } \\
{\stemDown
\repeat tremolo 16 {d,
2007/12/7, Graham Percival <[EMAIL PROTECTED]>:
> [1] We now have 170 open bugs. Don't assume that yours is more
> important than others.
I don't, and I hope you know that.
Clearly, there are two different bugs here: the \stemDown that doesn't
work, and the collision. I just assumed the former
Issue 526: multiple engravers produce multiple output
http://code.google.com/p/lilypond/issues/detail?id=526
Comment #1 by [EMAIL PROTECTED]:
Between 2.10.33 and 2.11.35 :-)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred thi
Ok, I've added it here.
http://code.google.com/p/lilypond/issues/detail?id=526
Han-Wen can decide which case is the bug.
Cheers,
- Graham
Rune Zedeler wrote:
Graham Percival skrev:
Actually, I'd consider this a new feature, not a regression -- if you
add an engraver multiple times, I'd expect
Issue 526: multiple engravers produce multiple output
http://code.google.com/p/lilypond/issues/detail?id=526
New issue report by gpermus:
Between 2.11.33 and 2.11.35, we started producing output for multiple
(identical) engravers.
- if this was accidental, then it should obviously be fixed.
- if
Graham Percival skrev:
Actually, I'd consider this a new feature, not a regression -- if you
add an engraver multiple times, I'd expect lilypond to draw the feature
multiple times.
Okay.
In this case somebody should go through engraver-init.ly to ensure that
no engravers are added twice anywh
Han-Wen Nienhuys wrote:
2007/12/6, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Issue 519: PDF filesize has increased between 1.9.8 and 2.10
http://code.google.com/p/lilypond/issues/detail?id=519
Comment #3 by gpermus:
Shouldn't the PDFs be independent of OS? Presumably on windows we
include the fon
Actually, I'd consider this a new feature, not a regression -- if you
add an engraver multiple times, I'd expect lilypond to draw the feature
multiple times. Doesn't Voice contain an Ottava_spanner_engraver by
default?
Han-Wen?
Cheers,
- Graham
Rune Zedeler wrote:
\version "2.10.25"
\pape
2007/12/6, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Issue 519: PDF filesize has increased between 1.9.8 and 2.10
> http://code.google.com/p/lilypond/issues/detail?id=519
>
> Comment #3 by gpermus:
> Shouldn't the PDFs be independent of OS? Presumably on windows we
> include the font
> so that the
\version "2.10.25"
\paper{ ragged-right=##t }
\new Voice \with { \consists Ottava_spanner_engraver \consists
Ottava_spanner_engraver }
{
b b b #(set-octavation 1) b b b b b b b #(set-octavation 0) b b b
}
<><>___
bug-lilypond mailing list
bug-lilyp
Hans Aberg wrote:
When I made the first report, I had no idea what was causing it. All I
knew was that replacing the quadruplet with a rest made it problem
disappear, so it looked to me as though that was the problem. You, with
your broader knowledge of LilyPond bugs,
I wish that people would
On 7 Dec 2007, at 01:25, Graham Percival wrote:
Hans, thank you for the bug reports, but please learn how to
produce minimal examples -- these allow people to understand the
bugs much more easily, which in turn lets the programmers fix it
sooner.
Added as
http://code.google.com/p/lilypond
Valentin Villenave wrote:
2007/12/6, Mats Bengtsson <[EMAIL PROTECTED]>:
Far from minimal!
\relative {
\stemUp
\repeat tremolo 16 {d32 a'32 }
\stemDown
\repeat tremolo 16 {d,32 a'32 }
\stemUp
\repeat tremolo 8 {d,32 a'32 }
\stemDown
\repeat tremolo 8 {d,32 a'32 }
}
Issue 525: repeat tremolo can't force stem downs
http://code.google.com/p/lilypond/issues/detail?id=525
New issue report by gpermus:
%{ console message:
foo.ly:8:22: warning: weird stem size, check for narrow beams
\repeat tremolo 16 {
d,32 a'32 }
foo.ly:8:27: warning: weird
Hans, thank you for the bug reports, but please learn how to produce
minimal examples -- these allow people to understand the bugs much more
easily, which in turn lets the programmers fix it sooner.
Added as
http://code.google.com/p/lilypond/issues/detail?id=524
but let me show you the actual
Issue 524: pitched trill loses accidental
http://code.google.com/p/lilypond/issues/detail?id=524
New issue report by gpermus:
% we should display a flat on the ges
\version "2.11.35"
\paper{ ragged-right = ##t}
\relative c'' {
g4 f \pitchedTrill f \startTrillSpan ges f\stopTrillSpan
}
Attach
2007/12/6, Mats Bengtsson <[EMAIL PROTECTED]>:
> Far from minimal!
> \relative {
>\stemUp
> \repeat tremolo 16 {d32 a'32 }
>\stemDown
> \repeat tremolo 16 {d,32 a'32 }
>\stemUp
> \repeat tremolo 8 {d,32 a'32 }
>\stemDown
> \repeat tremolo 8 {d,32 a'32 }
> }
Yes, but
Far from minimal!
\relative {
\stemUp
\repeat tremolo 16 {d32 a'32 }
\stemDown
\repeat tremolo 16 {d,32 a'32 }
\stemUp
\repeat tremolo 8 {d,32 a'32 }
\stemDown
\repeat tremolo 8 {d,32 a'32 }
}
However, you might want to extend the example to illustrate that
\stemUp/-Down
On 6 Dec 2007, at 08:03, Graham Percival wrote:
Please create a minimal example.
In particular, I cannot believe that you need an esoteric beam
grouping for this.
Well, it is not esoteric - the meter is in fact very popular. :-)
I also can't imagine that the #'script-priority affects anyth
%{
This was previously a comment to issue 318:
http://code.google.com/p/lilypond/issues/detail?id=318#c3
Here's a minimal example that clearly demonstrates the bug:
in the following snippet the tremolo should be printed below the whole
notes, instead of above (thus colliding with the first voice).
2007/12/6, Graham Percival <[EMAIL PROTECTED]>:
> Minimal example, please. It took me thirty seconds to find two lines I
> could remove. I also don't see why you need three lines of score here,
> as well as so many time signatures.
OMG. I have just mixed up X and Y axis. Indeed setting the Y ext
21 matches
Mail list logo
