Hi, I would like to report a bug regarding instrument names when using
Lilypond 2.7.36 for Windows XP. In the pdf file, the instrument names are
not vertically aligned even though both use the center-align command in
markup for instrument names. This is despite I left the second line blank
for
Hi, I'm using Lilypond 2.7.27 for Windows 98. There seems to be a problem
regarding the Mark_engraver property. Apparently, when Mark_engraver is
used, it seems to disregard the
\set Score.rehearsalMarkAlignSymbol property. Here is an example:
\version "2.7.27"
align = \set Score.rehearsalMarkAl
Hi, I've tried your method on either staff but it doesn't solve the problem.
I've figured out a great workaround though. Just insert a key signature for
the second staff which is the same as the first staff, and then use
\override Staff.KeySignature #'transparent = ##t to make it invisible. By
Hi, I am using Lilypond 2.7.27 for Windows 98. I've found something peculiar
about the horizontal placement of multi measure rests in the presence or
absence of time signatures. Here is an example:
\version "2.7.27"
\score{
\new StaffGroup <<
\new Staff { \key a \major R1 \break R1 }
\new Staf
Surprisingly, both 2.7.28 and 2.7.29 work with no problems in Windows XP. I
guess this must be something to do with some incompatibility with Windows
98.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-l
Hi, I would like to report that Lilypond 2.7.29 installed in Windows 98 does
not produce pdf file, only the PostScript and text file are produced. The
text file generated following error message:
%%[ Error: typecheck; OffendingCommand: pdfmark; ErrorInfo: Border
--nostringval-- ]%%
Stack:
/ANN
Hi, I have just installed Lilypond 2.7.28 for Windows 98 and I'm afraid to
report that there is something wrong with it which prevents it from
generating pdf files. When executing the .ly file, everything went fine
until it stopped at the PostScript file generation stage. Also, when I
double cl
Does this mean that there is no way we can predict when Lilypond makes the
tremolo marks slope and when it doesn't?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
But doesn't this look of tremolo marks clashing with notebeams kind of
untidy? Is there a way to move the vertical position (either upwards or
downwards) of the tremolo mark so that it doesn't come too close to the
notebeam or too central relative to the note stem?
_
Hi, I'm using Lilypond 2.7.27 for Windows 98. When I compiled the following:
\version "2.7.27"
\relative
{ c8:16 e: g: c: }
the output shows that the tremolo marks are placed differently on the 4
notestems, from being too central (1st note) to almost touching the notebeam
(4th note). Is this a
Hi, I've managed to isolate the problem. When I compile this:
\version "2.7.18"
\relative c'
{
\clef treble
\key f \major
\time 4/4 \autoBeamOff
g'4 r4 c2\melisma \break
bes16[ c bes a] bes[ f' e f] e[ f g f] e }
\addlyrics { me, " " __ }
The results are shown in extracta.pdf. But when I add
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:
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?
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
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?
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
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, yes I would love to contribute. The only problem is I don't have a
credit card as I'm still a student. Are there any other forms of payment for
the purpose of sponsorship?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/
Hi, I've managed to isolate the problem. When I compile this:
\version "2.7.18"
\relative c'
{
\clef treble
\key f \major
\time 4/4 \autoBeamOff
g'4 r4 c2\melisma \break
bes16[ c bes a] bes[ f' e f] e[ f g f] e }
\addlyrics { me, " " __ }
The results are shown in extracta.pdf. But when I add
Hi, yes. In fact, with sponsorship, the MIDI feature will be rewritten. Look
for "MIDI rewrite" in here:
http://lilypond-design.com/sponsor/open-features.html
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/
Hi, after viewing some printed scores, I now understand why. Normally, music
notes higher than the middle line of a staff have downward stems. However,
in polyphony, the upper voice has upward stems. I think the reason the stem
lengths are shorter is to prevent clashes or overlaps with noteheads
Hi, I think I'll accept that explanation. Still, it looks kind of strange.
Can I still manually elongate the stems to override this?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi, I still don't get it. Different stem lengths of different voices and
that is standard notation? How come? Do you mean that even in printed
scores, the stem length of the upper voice will be shortened if the notehead
is above the middle line of the staff?
Hi, I'm afraid I don't understand your question. If its not an optical
illusion, the upper voice's stem length is shorter than the lower voice's.
Surely both should have the same lengths.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://li
Hi, in the following file:
\version "2.7.18"
\relative c''
{ << { d8 d d d } \\ { d d d d } >> }
the stem length of the upper voices seems too short if compared with the
stem lengths of the lower voice. Is this a known bug?
test.pdf
Description: Adobe PDF document
__
Hi, I tested this on 2.6.3 and 2.7.18. Seems that nothing has been done to
fix this although I would think MIDI generation is not the main priority for
a music engraving program like Lilypond.
By the way, how does Lilypond generate MIDI based on ASCII (text-based)
input?
___
Hi, I've tried all your suggestions and they don't seem to work either. I've
attached a GIF file which is the output of extract.ps generated by
GhostScript 8.15 (I saved the image using Paint). The raggedright and
\lyricsto do not seem to have no effect. Surprisingly, I haven't been able
to dup
Hi, I discovered that sometimes grace notes aren't interpreted incorrectly
in MIDI generated by Lilypond. Here is an extract from the file:
\version "2.7.18"
global = { \key b \minor
\time 3/4 }
\score {
\relative
\new StaffGroup <<
<< \new Staff {
\set Staff.midiInstrument = "flute"
\global d'
To Erik Sandberg,
Hi, the lyric extender line problem still exists on version 2.7.19 (see
attached file). The file was generated by a Mac computer since 2.7.19 for
Windows hasn't been released yet. What is going on? Why can't the CVS detect
this?
extract.pdf
Description: Adobe PDF document
To Erik Sandberg,
Hi, Lilypond 2.7.19 fixed the double extender line problem. But take a
look at the file. The extender lines are not perfectly aligned vertically
even though the width of both figures are the same. In a way, it is similar
to the previous problem with the of vertical misalignme
Hi, I have discovered that the horizontal misalignment of two or more
extender lines extending from the same figure is not only caused by the
addition of an accidental to the right of the figure, but it also happens
when one of the figures has double digits. Consider the following example:
\ve
Hi, thank you very much for adding this to the bug repository. But by doing
this will there be a solution or a way to fix this bug?
Thanks.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
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 rare tie wit
Hi, it still appeared in version 2.7.18. I have to stress that this happened
for the Windows 98 and Mac versions of Lilypond. Can I send a pdf file for
you to see?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/list
Hi, I'm able to isolate the problems to a couple of bars. Here is what the
double extender lines is supposed to look like:
\version "2.7.17"
\relative {
<< \context Voice {
\clef bass
c,8 c c c c c c c c c c c }
\context FiguredBass \figuremode { \set useBassFigureExtenders = ##t
\set figure
Hi, I am typing a work for soprano by Mozart and I encountered into a
problem with the lyrics extender lines. I'm using Lilypond 2.7.17 for
Windows. Here is an extract of the complete file:
\version "2.7.17"
\relative c'
{
\clef treble
\key f \major
\time 4/4 \autoBeamOff
g'4 r4 c2\melisma
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
Hi, I've been using Lilypond 2.7.17 for Windows to take advantage of its
support for figured bass. However, I discovered several problems and bugs
which I hope can be fixed.
Here is the file for your reference:\version "2.7.17"
\header {
}
<<
\relative {
\set Staff.instrument =\markup {
\c
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 \override Score.RehearsalMark #'pa
42 matches
Mail list logo
