You didn't include the actual .ly file, or maybe it was removed
by the mailing list server. Please paste into the mail body
and send it to the mailing list (or put it on a web page somewhere).
In general, I trust LilyPond's bar checking mechanism more than
I trust my own manual proof reading of a
Inclusion of underscore character _ with a duration in \lyricmode
causes right alignment rather than center alignment of previous lyric
text.
BEGIN ALIGNMENT BUG SNIPPET %%
\score {
<<
\new Staff {
c'4 c'4 c'4 c'4
}
\new Lyrics \lyricmode {
Graham Percival wrote:
Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
Actually, I'm not sure what the status of this issue is. Technically,
architecture independent stuff should go into /u
Trevor Baca wrote:
Inclusion of underscore character _ with a duration in \lyricmode
causes right alignment rather than center alignment of previous lyric
text.
It's a feature, not a bug. This is intended as a way to easily enter
melismata. Use \skip if you want to skip things.
--
Han-We
Mats Bengtsson wrote:
You didn't include the actual .ly file, or maybe it was removed
by the mailing list server. Please paste into the mail body
and send it to the mailing list (or put it on a web page somewhere).
In general, I trust LilyPond's bar checking mechanism more than
I trust my own
Ben wrote:
The strange thing happens from m.9-10... the tie that goes from one
system to the next. The log file is filled with:
programming error: infinity or NaN encountered while converting Real number
continuing, cross fingers
programming error: setting to zero
continuing, cross fingers
Also,
Hi,
in the following example, in the first tied chord the B is not tied, or
the tie is just over the staff line (?).
Besides this, the other tied chords in the example are ok, but look
somewhat strange to me. In the second tied chord, the tie for the E looks
strange under the dot, and in
The following example gives the following error several times in the log:
programming error: infinity or NaN encountered while converting Real number
continuing, cross fingers
programming error: setting to zero
continuing, cross fingers
if there's no \break then there's no error. Note that ther
Hi,
I saw that the part-combine-mm-rest-after-solo regression test is broken. This
bug can get a low priority, because I have mysteriously fixed it in my thesis
fork.
--
Erik Sandberg
Maintainer of the Lilypond bug CVS archive,
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/
h
Sorry, the example is for version 2.7.7, not 2.7.6 as stated in the ly file
The following example gives the following error several times in the log:
programming error: infinity or NaN encountered while converting Real
number
continuing, cross fingers
programming error: setting to zero
conti
On Tue, 23 Aug 2005 21:31:18 +0200, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
Please run
lilypond --verbose --png test.ly
to get a more informative error message and send it to the mailing list.
ouch! I should have done this before asking. Sorry.
The problem seems to be that I have the Cent
The following code works in 2.4.6 on cygwin and 2.6.3 on Windows
native, but produces wrong output with 2.7.7 Windows native (see
attached "ties277.pdf").
Thomas
--
\version "2.7.6"
#(ly:set-option 'point-and-click #f)
\header {}
staffClassicalGuitar = \new Staff {
\set Staff.extraNatu
On 25-Aug-05, at 9:15 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
Actually, I'm not sure what the status of this issue is. Technically,
VSD wrote:
The following example gives the following error several times in the log:
programming error: infinity or NaN encountered while converting Real number
continuing, cross fingers
programming error: setting to zero
continuing, cross fingers
Thanks, fixed in CVS.
--
Han-Wen Nienhuys
Ferenc Wagner wrote:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
results for the Tie rewrite are at
http://localhost/lilypond/doc/v2.7/Documentation/topdocs/out-www/NEWS.html
Zooming into the PDF version reveals a stem-beam alignment
issue in the break-overshoot example.
fixed.
--
Han
\version "2.7.7"
\layout { raggedright = ##t }
{
\mark \markup {\box X} g'1 \break
\mark \markup {\box X} g'1
}
%%% end %%%
The first rehearsal mark collides with the treble clef with 2.7.7.
There's no collision with 2.7.4, but the two marks are aligned
differently in relation to the
16 matches
Mail list logo
