http://lilypond.org/bug-reports.html
--
Karlin High
Missouri, USA
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Dr. Juan F. Escamilla Castillo
jescami...@cimacien.org.gt
URL: www.cimacien.org.gt
Tel. (502)66465072
iphone: 50008182
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Trevor Daniels wrote Saturday, January 02, 2010 6:11 PM
Carl Sorensen wrote Saturday, January 02, 2010 4:31 PM
On 1/2/10 6:57 AM, "Federico Bruni" wrote:
The tied note head in TabStaff is white instead of transparent..
Actually, I suspect that the head is transparent, but it's also
go
Carl Sorensen wrote Saturday, January 02, 2010 4:31 PM
On 1/2/10 6:57 AM, "Federico Bruni" wrote:
Is this a bug of 2.13.10?
I assume it is.
It is
The tied note head in TabStaff is white instead of transparent..
Actually, I suspect that the head is transparent, but it's also
got a w
On 1/2/10 6:57 AM, "Federico Bruni" wrote:
> Is this a bug of 2.13.10?
I assume it is.
> The tied note head in TabStaff is white instead of transparent..
Actually, I suspect that the head is transparent, but it's also got a white
outline, and you're seeing the white outline.
>
> \version
Thanks, entered as
http://code.google.com/p/lilypond/issues/detail?id=375
Cheers,
- Graham
Wilbert Berendsen wrote:
I'm not top posting.
%{
The middle tie in the second bar is too long and sticks
out at both the left and right ends. This gets disturb-
ing when there are many ties and linebrea
> I'm not top posting.
%{
The middle tie in the second bar is too long and sticks
out at both the left and right ends. This gets disturb-
ing when there are many ties and linebreaks as can be
seen in
http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00198.html
%}
\version "2.11.26"
\pape
Erlend Aasland escreveu:
> Hi
>
> On 1/18/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>>
>> Can you run the test procedure ... and
>> report whether it shows any unexpected problems?
>
>
> Ok, there a few (two or three) cases with chords that look worse. I'll have
> another look at the code
Hi
On 1/18/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Can you run the test procedure ... and
report whether it shows any unexpected problems?
Ok, there a few (two or three) cases with chords that look worse. I'll have
another look at the code in a few days.
Erlend
--
Han-Wen Nienhu
Hi
On 1/18/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Can you run the test procedure ... and
report whether it shows any unexpected problems?
Shure, I'll do it tomorrow.
Erlend
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code
Erlend Aasland escreveu:
> Hi,
>
> With 2.11.12, ties on notes between the two upper staff lines are too
> close to the staff lines (see attached bad.png). The attached patch will
> fix this (see attached good.png) but I haven't tested it much so it
> might not be the correct way to fix this.
>
Hi,
With 2.11.12, ties on notes between the two upper staff lines are too close
to the staff lines (see attached bad.png). The attached patch will fix this
(see attached good.png) but I haven't tested it much so it might not be the
correct way to fix this.
Regards,
Erlend
good.png
Descriptio
Hi,
Always this bug with version 2.10.0-2
{
\relative c' { c4 f2 g4 }
\addlyrics { o la~oo ah }
}
Unfortunately it works fine on OSX.
Youpi :-)
Can anybody with a windows machine
verify this report?
I have verified at my work (win2k),
the process is blocked by the lyrics tie "~"...
Martial wrote:
The same bug with version 2.10.0
Lyrics tie "~" block LilyPond (winXP)
<<
\relative c' { c4 f2 g4 }
\addlyrics { o la~oo ah }
>>
Unfortunately it works fine on OSX. Can anybody with a windows machine
verify this report?
Cheers,
- Graham
_
hello
The same bug with version 2.10.0
Lyrics tie "~" block LilyPond (winXP)
<<
\relative c' { c4 f2 g4 }
\addlyrics { o la~oo ah }
>>
(no essential)
Regards !
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/li
> the pdf output is good with this
><<
> \relative c' { c4 f2 g4 }
> \addlyrics { é lé~àï îèù }
> >>
oops eratum :
the pdf output is good with this
<<
\relative c' { c4 f2 g4 }
\addlyrics { é lé-àï îèù }
>>
___
bug-lilypond mailing l
see this screen copy of unlocker
http://cathemline.org/lily/screen_copy.jpg
with this example
\version "2.9.29"
<<
\relative c' { c4 f2 g4 }
\addlyrics { o la~oo ah }
>>
and
http://cathemline.org/lily/good_output.jpg
<<
\relative c' { c4 f2 g4 }
\addlyrics {ah a_oo lo }
\addlyr
this example block Lilypond
<<
\relative c' { c4 f2 g4 }
\addlyrics { é lé~àï îèù }
>>
the pdf output is good with this
<<
\relative c' { c4 f2 g4 }
\addlyrics { é lé~àï îèù }
>>
I not use this "~" juste simple test.
Sorry !
Regards !
verbose with bad output
C:\Do
Graham Percival escreveu:
Martial wrote:
This examples is fine with all versions on my winXP:
<<
\relative c' { c4 f2 g4 }
\addlyrics {o la-oo ah }
\addlyrics {o la_oo ah }
>>
Hmm, maybe it's a problem with utf-8 fonts... can you make some lyrics
with accented characters?
Th
Martial wrote:
This examples is fine with all versions on my winXP:
<<
\relative c' { c4 f2 g4 }
\addlyrics {o la-oo ah }
\addlyrics {o la_oo ah }
>>
Hmm, maybe it's a problem with utf-8 fonts... can you make some lyrics
with accented characters?
- Graham
__
This examples is fine with all versions on my winXP:
<<
\relative c' { c4 f2 g4 }
\addlyrics {o la-oo ah }
\addlyrics {o la_oo ah }
>>
Hmm, does lilypond work on your system with even simpler music? This
example works fine on OSX.
- Graham
Martial wrote:
winXP
with version
Hmm, does lilypond work on your system with even simpler music? This
example works fine on OSX.
- Graham
Martial wrote:
winXP
with version
2.9.29.2
2.9.29.1
2.9.28.1
the lyrics tie crash or blocked LilyPond
<<
\relative c' { c4 f2 g4 }
\addlyrics {o la~oo ah }
>>
%--- begin verbos
winXP
with version
2.9.29.2
2.9.29.1
2.9.28.1
the lyrics tie crash or blocked LilyPond
<<
\relative c' { c4 f2 g4 }
\addlyrics {o la~oo ah }
>>
%--- begin verbose output
C:\Documents and Settings\MARTIAL\Bureau>set LILYPOND_VERBOSE=1
C:\Documents and Settings\MARTIAL\Bureau>lily
Hi, thanks again. I guess that is the ultimate aim in this development
series. Looks like we'll have to wait for the tie problem to improve. By the
way, how much does it cost to sponsor this?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http:
liang seng wrote:
Thanks. I will look into this. By the way, you mentioned that there is
an ongoing improvement on the tie reformatting. Does this mean that the
tie feature will get better and the bugs fixed in later versions and
will be on par with the stable 2.6 version, if not better?
the
Yes, I agree with you. Regarding to your question about what consitutes a
good tie, I think if we take a look at some editions of scores, the pdf
generated by 2.6.3 certainly looks a lot like the editions than the pdf
generated by 2.7.23. Again, I understand that the tie reformatting has to be
Thanks. I will look into this. By the way, you mentioned that there is an
ongoing improvement on the tie reformatting. Does this mean that the tie
feature will get better and the bugs fixed in later versions and will be on
par with the stable 2.6 version, if not better?
On Wednesday 21 December 2005 14.07, liang seng wrote:
> Hi, here is the source file again:
> \version "2.7.23"
> \relative c' {
> 1 < d g,> ~
> 4 8. 16 4
> 1~~ r2 2 r2
> \bar ".|." }
>
> Yes, I do agree that it looks good. However, the problem is they look good
> only in polyphony. In my case,
Hi, ok. But is there a way to sponsor this without using a credit card?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi, here is the source file again:
\version "2.7.23"
\relative c' {
1 < d g,> ~
4 8. 16 4
1~~ r2 2 r2
\bar ".|." }
Yes, I do agree that it looks good. However, the problem is they look good
only in polyphony. In my case, I cannot change the polyphony or break notes
into two voices since I ha
Hi, after installing version 2.7.23 for Windows, I have to say that the tie
reformatting feature is still not satisfactory. I've attached 2 files for
your reference.
Testa.pdf is generated by version 2.6.3 for Windows (the source file content
is at the start of this thread) while Testb.pdf is ge
liang seng wrote:
note is inside a chord or as the outermost notes of a chord. I'm not a
computer expert, but is there a way to tell Lilypond this? I hope I'm
making myself clear as this is beginning to annoy me.
At this point Steve Doonan is sponsoring me in monthly installments, so
the nex
On Wednesday 21 December 2005 13.21, liang seng wrote:
> Hi, after installing version 2.7.23 for Windows, I have to say that the tie
> reformatting feature is still not satisfactory. I've attached 2 files for
> your reference.
> Testa.pdf is generated by version 2.6.3 for Windows (the source file
>
Hmm, I see. It's just that the tie problem I highlighted in my example does
not appear in 2.6.x, so I assume that this is not such a big problem in the
stable series. By the way, Mr. Erik Sandberg mentioned that this should be
fixed once and for all in 2.7.19. Is this true?
liang seng wrote:
in the first place when there is nothing wrong with the tie format 2.6.x
which generates good ties?
Many people, including me, disagree. See eg.
http://lilypond.org/bugs/v2.6/
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_
Hi, I see. But I'm curious to know that how can you be certain that the tie
problem will be fixed once and for all in the upcoming stable series 2.8.x?
Reitering my previous question, I would like to know why the tie formatting
is being rewritten in 2.7.x which causes all these problems in the fi
On Friday 16 December 2005 15.45, liang seng wrote:
> Hi, it seems that the tie problem is still not solved in version 2.7.18
> (Windows 98 version).
As Han-Wen said, the problem should be fixed in v2.7.19 and later.
BTW, if the bugs in the unstable 2.7.x series disturb you, it might be a good
i
Hi, it seems that the tie problem is still not solved in version 2.7.18
(Windows 98 version).
Here is an extract of the file:
\version "2.7.18"
\relative c' {
1 < d g,> ~
4 8. 16 4
1~~ r2 2 r2
\bar ".|." }
If you generate this file using 2.7.18 for Windows ( 98 ), you will find
that the lowe
Hi, I've already reduced the file to the smallest size that shows the
figured bass bugs. The thread is here:
http://lists.gnu.org/archive/html/bug-lilypond/2005-11/msg00155.html
Also, it seems that version 2.7.18 has almost fixed the tie bug. I say
almost because there is always a rar
liang seng wrote:
The same goes with the extender line problem in the figured bass bugs.
If I type that problematic bar only, there is no problem.
You should start with a faulty example, and remove .ly code until the
bare minimum that is necessary for it to break.
I suggest that you invest a
Hi, I would like to apologize for sending such a large file. The thing is,
if I just type those particular bars alone (eg bar 43-44) with the ties, or
the example that you gave, the problem does not surface. The ties come out
normal.
The same goes with the extender line problem in the figured ba
Graham Percival wrote:
Hi, I'm using Lilypond 2.7.17 for Windows and I find that the tie bug
where the vertical position of ties are still not resolved. Here is
the file:
Thanks for the bug reports, but in the future please include an example
which is as small as possible -- ie
{
c
On 22-Nov-05, at 3:19 AM, liang seng wrote:
Hi, I'm using Lilypond 2.7.17 for Windows and I find that the tie bug
where the vertical position of ties are still not resolved. Here is
the file:
Thanks for the bug reports, but in the future please include an example
which is as sma
Hi, I'm using Lilypond 2.7.17 for Windows and I find that the tie bug where
the vertical position of ties are still not resolved. Here is the file:
\version "2.7.17"
\header {
}
\relative {
\set Staff.instrument ="Violin I"
\key a \major
\time 3/4
\clef treble \ove
Thomas Scharkowski wrote:
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").
Hi,
this seems to be fixed in the current release.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all
> Hi,
>
> your attachment was stripped. I've just removed attachment stripping
> for
> [EMAIL PROTECTED] Could you resend it?
>
> --
> Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
Yes,
here it is.
Thomas
Der folgende Teil dieser Nachricht enthält einen Anhang im
sog
Thomas Scharkowski wrote:
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").
Hi,
your attachment was stripped. I've just removed attachment stripping for
[EMAIL PROTECTED] Could you resen
Hi,
I have noticed a few things, possibly bugs, in a score I recently
typeset using 2.7.8 that didn't exist in a pdf I previous typeset
with Lilypond (not sure which version, sorry!). Here are some
examples - all examples are 2.7.8 vs. a previous version:
vs
As you can see, the tie is
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
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,
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
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
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, the barcheck
Ok, I created a not-so-copyrighted fragment. See the problem with the
last tied chord.
The problem is closely related to the staff-space size I think, because
if I remember well, it only happened in staves that have a different
staff-space.
\version "2.6.0"
#(set-global-staff-size 16)
\inc
On Sunday 03 July 2005 23.53, Bertalan Fodor wrote:
> Ties get curved in wrong direction in some situations. Workaround:
> change y-offset to 0.4
>
> See attached image.
>
> I couldn't make a small fragment that reproduces this. But it seems to
> happen quite often in smaller sizes.
No file is att
Ties get curved in wrong direction in some situations. Workaround:
change y-offset to 0.4
See attached image.
I couldn't make a small fragment that reproduces this. But it seems to
happen quite often in smaller sizes.
Bert
___
bug-lilypond mailing
[EMAIL PROTECTED] writes:
> Mats Bengtsson encouraged me to send the following example:
>
> \score{
>\notes{
> \key a \major
> \partial 8 g8 ~ | g2 ~ g8 fis4. |
> }
>
> This produces a natural on the last g which should not be there!?
Sorry for the delay; this is fixed in C
Mats Bengtsson encouraged me to send the following example:
\score{
\notes{
\key a \major
\partial 8 g8 ~ | g2 ~ g8 fis4. |
}
This produces a natural on the last g which should not be there!?
Thank you
Thomas
___
Bug-lil
[EMAIL PROTECTED] writes:
> Hi,
>
> The following example:
> \score {\notes {\key c\major \time 4/4 bes1~ | b }}
> produces the same output as:
> \score {\notes {\key c\major \time 4/4 bes1~ | bes }}
>
> without complaining.
> But should not the first example remove the tie, just as in "bes1~ | c
Hi,
The following example:
\score {\notes {\key c\major \time 4/4 bes1~ | b }}
produces the same output as:
\score {\notes {\key c\major \time 4/4 bes1~ | bes }}
without complaining.
But should not the first example remove the tie, just as in "bes1~ | c" ? And
shouldn't a warning be issued for t
60 matches
Mail list logo
