ect Bug Tracker before making this, and
the most similar issues I could find were 1324 and 1702, but I don't believe
this is fully redundant.
Since I'm neither a programmer nor closely involved with this project, I
thought the best thing to do would be to post this example and hope that
% Bug: Whole notes shouldn't get stems when stemlets are enabled.
\version "2.11.43" % (Tested with 2.11.43-2 on Windows XP)
\paper{ ragged-right=##t }
\relative c' {
\override Stem #'stemlet-length = #0.5
c'1
}
___
bug-lilypond mailing list
bug-li
On 3/28/2008 5:38 AM, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Again, I can confirm the crash with version 2.10.33 in Linux.
> Version 2.11 works well also with this example.
> Time to upgrade?
Evidently 2.11.43-2 does the trick. (2.11.43-1, on Windows XP, crashed
after complaining about Pango
This one is weird. Apparently some combinations of polyphony, manual
beams, and a dotted rest followed by a note, trigger a "Wrong type"
error (Windows XP here). Many variations I've tried still trigger the
error, while other variations don't. You can experiment for yourself.
Unlike the stemlets-o
\version "2.10.33"
\paper{ ragged-right=##t }
{
% Lilypond (lilypond-windows.exe under Windows XP) crashes
% unless either one of the next two lines is commented out:
\override Stem #'stemlet-length = #0.5
r8[ r]
r8 r
r8[ c' r] }
% (The last two lines don't cause any problems.)
___
This might be too late for the 2.10 release, but it should be fixed sooner
or later.
I couldn't find anything on hairpins in
http://code.google.com/p/lilypond/
, so I assume this bug persists in 2.9.28.
% This hairpin should not be left open, but should end at the barline:
\version "2.9.26"
\
\column {
\line {Enough}
\line {vertical space?}
}}
a a a
} >>
}
\layout { indent = #0 }
%%% end revised example %%%
Marcus Macauley wrote:
Sometimes Lilypond creates vertical space between staves to avoid a
collision between, f
Kieren MacMillan wrote:
Hi, Marcus:
Until the bug is fixed, perhaps you can use #'rotation as a workaround
option...?
Hi Kieren,
Thanks for the suggestion! I hadn't thought of that. Unfortunately, it
looks like it would be a bit of a pain to tweak the second two arguments
of the #'rot
I see that this issue was unresolved on the lilypond-user list, Panteck
and Graham Percival posting (06 Sep 2006). And I ran into it myself today.
So here's a bug report.
Let me know if I've misunderstood how it's supposed work.
Marcus
\version "2.9.26"
% Bug report for LaissezVibrerTie:
%
Is it just me, or have the braces on PianoStaff and GrandStaff suddently
become shorter in 2.9.26?
I know LilypondTool (for jEdit) can sometimes display PDF files a little
bit differently (braces shifted, dashed lines with longer dashes), but the
following file gives me shortened (i.e. not
Joe Neeman wrote:
On Sat, 2006-10-14 at 01:46 -0400, Marcus Macauley wrote:
Han-Wen Nienhuys wrote:
> Marcus Macauley schreef:
>
>> So, Joe, whatever it is that you fixed, there still seems to be a
>> problem [with vertical spacing] in 2.9.22.
>> I can try to send
According to the documentation --
http://lilypond.org/doc/v2.9/Documentation/user/lilypond-internals/Beam.html
http://lilypond.org/doc/v2.9/Documentation/user/lilypond-internals/beam_002dinterface.html
-- the following setting should produce "horizontal beams":
\override Beam #'damping = #1
As the following example demonstrates, beams which begin or end on a rest
are normally drawn beautifully (with respect to angle and positioning),
but when stemlets are enabled, these beam angles/positioning are messed up:
\version "2.9.23"
\relative c' {
c8[ r] e[ r] r[ g] r[ c]
Han-Wen Nienhuys wrote:
Marcus Macauley schreef:
So, Joe, whatever it is that you fixed, there still seems to be a
problem [with vertical spacing] in 2.9.22.
I can try to send an example if necessary.
I think this went in for 2.9.23
Actually, now in 2.9.23-1, it seems to be even worse
I wrote:
When I upgraded from 2.9.17 to 2.9.22, the page layout of one of my
scores got messed up. That's only my opinion, of course, but it changed
pretty drastically from five systems per page, spaced adequately, to
three systems per page, with lots of blank space.
Joe Neeman <[EMAIL PRO
Sometimes Lilypond creates vertical space between staves to avoid a
collision between, for example, a text markup in one staff and a beam in
the other staff, when these two things happen in different measures and
wouldn't actually collide.
On the other hand, in cases where they do collide a
I see that Mats Bengtsson has already pointed out that rehearsal marks
(\mark) are aligned over the right edge of double barlines, repeat
barlines, etc., rather than over their center.
http://code.google.com/p/lilypond/issues/detail?id=97
But I've noticed something worse. When there's a new
Joe Neeman <[EMAIL PROTECTED]> wrote:
On Sun, 2006-10-08 at 10:27 +, Arvid Grøtting wrote:
Arvid Grøtting gmail.com> writes:
> For some reasons, 2.9.21 has three systems per page on all pages,
> while 2.8.1 has three on the first page and four thereafter, but I
> don't know if that's a sy
I just upgraded to 2.9.22 (for Linux), and this bug persists.
So here it is again (below) with the proper version number.
Marcus
\version "2.9.22"
% When lilypond is run on this file, it generates a segmentation fault.
% Apparently \addquote can't handle the \new Voice.
%
% The documentation
I haven't upgraded to Lilypond 2.9.22 yet, but the following file
generates a segmentation fault for me on Lilypond 2.9.17 (Linux).
Hopefully someone can run it on 2.9.22 to confirm that the bug still
exists, or I'll repost once I've upgraded.
Marcus
\version "2.9.17"
% When lilypond is
I wrote:
...
\override TupletBracket #'connect-to-neighbor = #'(#f #f)
...
Mats wrote:
To produce a pair of values in Scheme, you should write
\override TupletBracket #'connect-to-neighbor = #'(#f . #f)
(another option is the following:)
\override TupletBracket #'connect-to-neighbor = #(cons #
As far as I understand, the following four overrides:
\override TupletBracket #'connect-to-neighbor = #'(#f #f)
\override TupletBracket #'connect-to-neighbor = #'(#f #t)
\override TupletBracket #'connect-to-neighbor = #'(#t #f)
\override TupletBracket #'connect-to-neighbor = #'(#t #t)
documented
Not to nag, but is this planned to be fixed for the 2.8 release?
I ask because it persists in 2.7.39, and I don't know if it's a new bug (I
first noticed it while using 2.7.38) or an old one.
Marcus
On Thu, 16 Mar 2006 05:24:22 -0800, Marcus Macauley <[EMAIL PROTECTED]>
This is probably related to the "Release-critical accidentals spacing bug"
(http://lists.gnu.org/archive/html/bug-lilypond/2006-03/msg00039.html),
but here's a telling example:
\version "2.7.38"
\layout {ragged-right = ##t}
{
2~ ~ | ~ cis'' gis'>
}
It seems that when a chord with accidental
On Mon, 13 Mar 2006 21:40:01 -0800, Trevor Bača"" <[EMAIL PROTECTED]>
wrote:
Hi Marcus,
Yeah, unfortunately I don't have an answer for this one and [your]
examples look like a valid report.
I know Erik likes to keep bug examples as small as possible, so maybe
we could extract two particularly g
On Mon, 13 Mar 2006 05:43:32 -0800, Trevor Bača"" <[EMAIL PROTECTED]>
wrote:
Hi Marcus,
Bug #1 can be fixed by turning on uniform-stretching in the
SpacingSpanner:
\new Score \with {
\override SpacingSpanner #'uniform-stretching = ##t
}
<<
\staffPianoI
On Mon, 13 Mar 2006 06:23:22 -0800, Erik Sandberg
<[EMAIL PROTECTED]> wrote:
On Monday 13 March 2006 09.40, Marcus Macauley wrote:
2. The staves are spaced unevenly.
This is intentional.
All staves, except those inside PianoStaff contexts, are spaced
individually.
The space betwe
is differently, please advise me.
Anyway, the score in Lilypond markup follows below.
Regards,
Marcus
\version "2.7.28"
\header {
title = "fort(r)etude"
subtitle = "version for 2 players"
composer = "Marcus Macauley"
}
\includ
f font being used for the time signature. I thought 2.5.14 would
fix it, but apparently not.
I installed mftrace 1.1.5, and subsequently ec-fonts-mftraced-1.0.9-1 (I
hope these don't conflict), before either Lilypond install.
Marcus Macauley
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
else, I would have
expected to find a link in the lilypond INSTALL.html file.
Thanks in advance for any help/advice,
Marcus Macauley
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ometimes you
want to make exceptions). As an alternative to the latter, the ability
to move individual rests up/down relative to their position after
beaming (or relative to their default position on the staff) without
affecting beam adjustments (see 1).
Thanks a lot,
Marcus Macauley
P.S. Two example fil
2.5.0, though I
expect the behavior is common to all versions, or at least all recent
versions.
If anyone knows of a workaround, please let me know.
Thanks,
Marcus Macauley
%---start dotsbug.ly---
\header { texidoc = "
The first and third Gs should have augmentation dots above and below the
rmats the music correctly, but not the
page.
Please let me know if there is a workaround or if I'm just doing the wrong
thing; otherwise, I'll assume it's a bug which needs to be fixed.
Thanks,
Marcus Macauley
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
33 matches
Mail list logo
