I'm not top posting.
Things look much better after issuing \override Beam #'concaveness = #0
(or some mild value near zero - I use it \once). So the problem is gone.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Please read at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Compiling-a-file#Compiling-a-file
if you have not already done so.
/Mats
Joseph M. Krush wrote:
Hello, LilyPond Staff:
I'm writing a book on music (the title is my e-mail address), so I
desparately need
The next time you send follow-ups to emails on the mailing list, please
keep the same
subject line. It takes some effort to figure out what problem you refer to.
Great that you have figured out the solution yourself and thanks for
sharing it to
others on the mailing list.
/Mats
Alex Shanin
Issue 655: \remove should emit warning for unknown engravers
http://code.google.com/p/lilypond/issues/detail?id=655
New issue report by lemzwerg:
\version 2.11.55
\header { texidoc =
@code{\remove} should emit a warning if its argument is an
undefined engraver.
Here is a counterexample.
}
Issue 655: \remove should emit warning for unknown engravers
http://code.google.com/p/lilypond/issues/detail?id=655
Comment #1 by n.puttock:
Hi Werner,
This appears to be specific to \with; if you have an unknown engraver in
\layout, it
correctly produces an error, `unknown translator'.
Issue 655: \remove should emit warning for unknown engravers
http://code.google.com/p/lilypond/issues/detail?id=655
Comment #2 by lemzwerg:
Yes, I've seen the corresponding warning code in lilypond. However, I don't
understand what's going on there, so I can't fix it by myself.
--
You
2008/8/4 Francisco Vila [EMAIL PROTECTED]:
so \lyrics alone without \lyricsto or explicit \set associatedVoice
never works, even in this case durations are needed, I'd not recommend
to use \lyrics, it seems to be a bit useless.
(taking a deep breath)
... I think I got lost somewhere in
2008/8/5 Mats Bengtsson [EMAIL PROTECTED]:
I would perhaps not classify this as a pure bug, but definitely as a
limitation that deserves a feature request in the bug database.
As far as I can see, the same vertical position is used the for the left end
of the part of the glissando before the
Issue 656: -dclip-systems error when 'header:title is defined
http://code.google.com/p/lilypond/issues/detail?id=656
New issue report by v.villenave:
% The following code produces an empty .ps file and a scm error in
% framework-ps.scm, line 630: Wrong type (expecting pair): ()
#(ly:set-option
2008/8/8 Mats Bengtsson [EMAIL PROTECTED]:
The problem remains in the latest 2.11.x version. The
*-from-1.0.1-to-2.0.1-clip.{pdf,eps}
files are created correctly, but the *.{.ps,pdf} files are empty when the
title is present.
Derek Poon wrote:
%% An error occurs when making clips when
Issue 656: -dclip-systems error when 'header:title is defined
http://code.google.com/p/lilypond/issues/detail?id=656
Comment #1 by v.villenave:
I should have mentioned that defining clip-regions doesn't prevent the bug
from
happening.
It has been tested with both 2.10.33 and 2.11.55
--
2008/8/9 Alex Shanin [EMAIL PROTECTED]:
% Upper beam gets sloped ok, lower doesn't at all.
Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=657
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Issue 657: Weird cross-staff beams damping when stems are down
http://code.google.com/p/lilypond/issues/detail?id=657
New issue report by v.villenave:
% In the following example, the beams are completely horizontal
% (whereas they should have a nice slope). If you turn the stems up,
% they're
Issue 658: Inconsistency when moving a Script in different situations
http://code.google.com/p/lilypond/issues/detail?id=658
New issue report by v.villenave:
% In the following example, the Y-offset override produces
% a different result each time it is used.
\version 2.11.55
\relative c' {
2008/8/11 Marco Caliari [EMAIL PROTECTED]:
the \override Script produces inconsistent results (the last one quite bad).
Finally, I found that I have to override the padding property: still, I think
there is something wrong with #'Y-offset.
Yes indeed; I added it as
2008/8/14 Valentin Villenave [EMAIL PROTECTED]:
2008/8/4 Francisco Vila [EMAIL PROTECTED]:
so \lyrics alone without \lyricsto or explicit \set associatedVoice
never works, even in this case durations are needed, I'd not recommend
to use \lyrics, it seems to be a bit useless.
(taking a deep
16 matches
Mail list logo
