On Sunday 13 June 2004 12.31, Alex Klein wrote:
Hi guys,
first of all, great job on lilypond. I first tried it about two months
ago and now I'm using it for pretty much all of my notation stuff. I'm
currently using 2.0.3 which came with the recent Suse 9.1, but there are
some improvements in
On Sunday 13 June 2004 12.38, Alex Klein wrote:
Hi guys,
small thing, but quite annoying. If I use for example
a-.( c-.)
the slur starts almost at the position where the staccato dot is, thus
it is hard to tell if the note has actually a staccato dot or not. I
guess the slur end point
On Saturday 12 June 2004 19.45, Bertalan Fodor wrote:
Hello,
I have a score where an instrument and singer are answering each other.
I thought it would be natural to use
\context Voice = instrument { ... }
\context Voice = singer { ... }
\context Voice = instrument { ... }
\context Voice =
On Tuesday 08 June 2004 00.54, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
[EMAIL PROTECTED] writes:
Does this sound sensible?
I'll think about it. The problem is that you have have to interpret
the music completely before you can decide whether or not to print an
error
Hi,
I added this to the bug cvs:
%important
[EMAIL PROTECTED]
\header { texidoc =
In the following example, no staff lines and no beams are printed.
No warning message is given.
}
\version 2.2.2
\header {title = x }
\score {
\context Staff = A \notes r1
\context Staff = B \new
Hi,
I have a feeling that voice-warning might be considered pretty close to
not-a-bug right now. So I'd like to state that this is not the case: There
are situations where the voice-warning bug is very annoying.
I'm working on a vocal piece which is composed of a number of different
sections,
On Sunday 06 June 2004 23.23, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Hi,
I have a feeling that voice-warning might be considered pretty close to
not-a-bug right now. So I'd like to state that this is not the case:
There are situations where the voice-warning bug is very
On Sunday 06 June 2004 23.20, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
I just ran this with v2.3.3.hwn1:
thanks for your report. I fixed this in CVS (I hope... )
For your information:
When bugs are fixed quickly, like in this case, I don't bother adding them to
the repository. It
On Friday 04 June 2004 10.59, Mats Bengtsson wrote:
\acciaccatura { af,16[ af'] } af c gf'8\arpeggio buried the af' in
the bar. I'm assuming it had something to do with the chord which
followed. It is certainly an advantage that Lilypond allows adjustments!
Yes, but in this case it's
On Thursday 03 June 2004 18.58, Mats Bengtsson wrote:
There's at least one serious bug left in 2.2.2, namely that
lilypond-book doesn't work correctly on LaTeX documents when
run in Cygwin.
What happens is that lilypond-book copies the header of the LaTeX file
and adds a small dummy body
On Tuesday 01 June 2004 00.36, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
On Monday 31 May 2004 20.48, you wrote:
[EMAIL PROTECTED] writes:
rest-collision:
The code gives a warning in 2.3 cvs, but it still gives incorrect
output. Is
What output do you expect?
I
On Monday 31 May 2004 16.47, Han-Wen Nienhuys wrote:
LilyPond 2.2.2 is out. It has a number of small bugfixes, so upgrade
if any of these errors concern you.
Good work! However, this one doesn't seem to be fixed. It is fixed in 2.3 cvs
though.
* lily/accidental-engraver.cc
hi,
The file
bugs/progerror-round-filled-box.ly
compiles with 2.2, but gives syntax error with 2.3.2. convert-ly doesn't do
anything about it.
Seems that in
\paper { \context { \LyricsContext ... } }
\LyricsContext has been renamed.
Erik
___
On Monday 31 May 2004 18.57, Erik Sandberg wrote:
On Monday 31 May 2004 16.47, Han-Wen Nienhuys wrote:
LilyPond 2.2.2 is out. It has a number of small bugfixes, so upgrade
if any of these errors concern you.
After looking through the bugs again, lily is now almost BugFree:
The only
On Monday 24 May 2004 12.09, johannes schöpfer wrote:
hello together,
first of all i want to thank you for your great work.
please excuse my very bad school-english.
i'm a jazz-student from stuttgart, germany
i think i have found a few bugs. i'm using lilypond 2.2.0 since a few
weeks and
On Monday 24 May 2004 23.28, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Hi,
added this to the bug database as crash-bar-number:
Did I miss something? It doesn't show up in my bugs directory.
Sorry, I forgot to commit. Try again now.
Erik
Hi,
added this to the bug database as crash-bar-number:
%crash critical
[EMAIL PROTECTED]
\header {texidoc =
Lilypond crashes with signal 11.
}
\version 2.2.1
\score {
\new Staff \with { \consists Bar_number_engraver } { }
\midi { }
}
And, using latest cvs:
Traceback (most recent call
hi,
I added this to the bug CVS.
The bugfix for the crash was apparently not good enough. Though lily doesn't
crash anymore, she still doesn't give correct output. Happens both in 2.2.1
and 2.3.2.
%important
[EMAIL PROTECTED]
\header {texidoc =
When a rest from voiceOne collides with one
Hi,
I added the following bug to the database, as custom-key-signatures. I marked
it 'critical' because it breaks a regression test.
%critical
[EMAIL PROTECTED]
\header { texidoc =
When a custom key signature is used, and the octave is set, then
the accidental has no effect on the music.
The
Hi,
I added this bug, as progerror-lyrics-staff.
%important
[EMAIL PROTECTED]
\header { texidoc =
This code results in a 'programming error'.
In the first example, two empty bars are added also.
In the second example, the two :s belong to the same
Staff context, but are typeset as different
Hi,
I added this as surviving-staff to the repository. Thanks to Ferenc.
Erik
%
[EMAIL PROTECTED]
\header { texidoc =
The upper staff is extended with an empty bar.
The score is weird in the sense that the Lyrics context is
created within a Staff context. But if this is not allowed, then
it
hi,
I added this to the bug repository:
%warning
[EMAIL PROTECTED]
\header { texidoc =
Each lyric produces a warning:
programming error: round filled box vertical extent smaller than blot;
decreasing blot
However, the output looks fine.
}
\version 2.2.1
\paper {
\context {
I added the bug to repository, as figured_bass.txt
Erik
On Friday 07 May 2004 11.39, Mats Bengtsson wrote:
You have clearly found a bug. The problem is that the figured bass is
processed by an extra function in scm/bass-figure.scm that determines
the typesetting and overrides the settings of
hi,
I added slur-bugs to the bug repository. Contains a bunch of cases where lily
doesn't handle slurs well. These bugs will not be fixed within the nearest
future. This might be extended with more test examples in the future.
% future
[EMAIL PROTECTED]
\header { texidoc =
Slurs collide with
On Sunday 02 May 2004 23.00, Han-Wen Nienhuys wrote:
Couldn't we just have the entire collection rendered just like
input/test in the tips tricks? Putting binary blobs, which are also
compiler output (by lilypond), into a source version control system
isn't the way to go I.M.O.
I see the
On Tuesday 04 May 2004 22.09, Stan Sanderson wrote:
Lilypond v2.2.1
I am transcribing a piano piece which, in the upper measure has
twenty-four 32nd notes ( the piece is in 3/4 time). The bass line is
six 8th notes.
Apparently this is a bug. I added it to the bug repository, as midi-grace.
On Monday 03 May 2004 08.58, Han-Wen Nienhuys wrote:
2.2.1 is out. It has a number of backports of 2.3 bugfixes.
The following bugs have been fixed:
grand-staff-piano-accidental
voice-align
The following CRITICAL bug has been fixed in 2.2.1 (but is enough fixed in 2.3
to be non-critical):
On Sunday 02 May 2004 16.16, Werner LEMBERG wrote:
BTW, the same goes for multivoice-rest-position2. It's not 100%
obvious (to me at least) that it really is a bug; I can imagine that
the coders could be more motivated to fix the problem if you've done
some research that shows that your
On Sunday 02 May 2004 07.34, Werner LEMBERG wrote:
I wrote:
I ask for yet another refinement: Do a zoom at the problematic spot
and crop the image around the buggy detail [...]
A good example is grace-accidental-spacing.ly: The current image (as
of Apr. 28th) doesn't really show the
On Sunday 02 May 2004 10.36, Erik Sandberg wrote:
On Sunday 02 May 2004 07.34, Werner LEMBERG wrote:
beam-accidental-collision.ly
broken-small-slur.ly
multivoice-rest-position.ly
multivoice-rest-position2.ly
Thanks! I marked multivoice-rest-position as important
Thanks for your report.
The bug has been added to our bug database (as grand-staff-piano-accidental).
You will be notified when it's fixed.
Erik
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
On Saturday 01 May 2004 18.46, Stef Epardaud wrote:
Hello,
I have here a quite large guitar tab file with 9 guitars, which used to
output to paper fine using lilypond 2.1.17, but not anymore with 2.3.1
Now when I process it, it prints the first page correctly, and all the
other pages have
On Monday 26 April 2004 07.43, Werner LEMBERG wrote:
It would be great if you can store JPG images also which show the
problem!
I use .png instead.
Yes, of course. A typo of mine.
I use the convention that if I submit something as clef-change.ly,
I upload clef-change.png
Hi,
I added this to CVS as misplaced-octaviation:
%
\header { texidoc = When octaviation ends on a rests, the octaviation bracket
is misplaced, to the left of the score. This should either be fixed,
or it should give a warning. }
\version 2.3.1
\score {
\new Staff \notes { #(set-octavation 1)
Hi,
I added this to the bug cvs as 'clef-change'.
%
% [EMAIL PROTECTED]
\header { texidoc =
The clef change in bar 1 is too far to the right (it should be
placed below the notes of the first staff), and in bar 2 it is
too far to the right (it should be next to the left of the next
note) }
Hi,
This problem was reported some time ago. Added it to the bug database
(volta-bracket-chords):
Volta brackets are placed below chord names, they should always be placed
above them.
Like:
_ __
|1. |2.
c c c c
==|=
=:|
% important
\header { texidoc =
On Tuesday 20 April 2004 19.21, Jan Nieuwenhuizen wrote:
Erik Sandberg writes:
I have refined Thomas Scharlowski's report.
Thanks! Fixed in 2.3 CVS.
The other problem (incorrect warnings) in tremolo-repeat still exists though.
(I haven't thought about this, but you may want to keep bugs
On Tuesday 20 April 2004 10.28, Thomas Scharkowski wrote:
Hello list,
example 1 works as expected:
% begin example 1
\version 2.2.0
\score {
\notes {
\key g \major
\time 2/4
\clef F
g8 g g g |
\repeat tremolo 4 g8 |
}
}
\paper {}
% end example 1
example 2 produces a warning:
%
Hi,
I have refined Thomas Scharlowski's report. The following:
\version 2.2.0
\score {
\new Staff \notes {\repeat tremolo 4 g8 r8 }
\paper {}
}
causes lily 2.2.0 to crash:
Calculating line breaks... [2]
lilypond-bin: /usr/local/src/lilypond/flower/include/drul-array.hh:27: Real
On Monday 19 April 2004 08.51, Richard Froese wrote:
Hello,
In the following fragment the last tied A flat in the top voice
is played by midi. It works fine if I leave out the bottom voice, or
take away the first bar. It also worked under 2.0. (I just upgraded to
2.2.) Can anyone help me
On Wednesday 14 April 2004 18.54, Roland Goretzki wrote:
Hi,
lilypond-version is 2.2.0.
If there are two areas of repeats in a piano-piece directly one after
another, lilypond creates automatically a correct double-repeat-barline
(:|:).
Unfortunately, in one piece this
Hi,
Incorrect midi barcheck warnings are happening again. This time I was unable
to isolate what causes it; random unrelated changes seem to affect it. I
couldn't get it much smaller than this:
%Lilypond produces correct output, but during midi output, it produces a
%barcheck warning for the
hi,
In lyrics mode, e.g. 'gö' is written 'g\o' using 2.2. However, in v1.6, this
was written 'g\\\o'. convert-ly does not take care of this difference.
Does anyone know in which version (approximately) this change happened?
Erik
___
Bug-lilypond
.. with the following output:
~/lily/lilypond$ make all
[...]
make[2]: Leaving directory `/home/erik/lily/lilypond/flower/include'
make[1]: Leaving directory `/home/erik/lily/lilypond/flower'
make[1]: Entering directory `/home/erik/lily/lilypond/lily'
rm -f ./out/context.dep;
On Tuesday 13 April 2004 13.26, Jan Nieuwenhuizen wrote:
Erik Sandberg writes:
.. with the following output:
~/lily/lilypond$ make all
Try make clean first (the automatic dependencies are always off when
source files have been removed).
Thanks!
I still get errors though. Here
Hi,
In the following score, the text pizzicato collides with the beam.
This problem has been around for quite a while ( it's easy to do a
workaround).
Are you planning to fix this kind of issues for 3.0? In that case, i could
start sending you more similar examples, if you like.
\version
Hi,
I've bundled a couple of old non-important bugs I found in pre-2.2, which have
not been fixed yet. Plus some new ones.
1. ly/declarations-init.ly starts with #(ly:set-option 'old-relative). This
should be removed, right?
2. Top of manual says:
This is the user manual for GNU LilyPond
On Wednesday 31 March 2004 10.42, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
c-part-combining.html#Automatic% 20part%20combining
In the first example, the stems of the two voices are merged.
According to the documentation they shouldn't be.
Why?
What exactly happens if
On Wednesday 31 March 2004 12.11, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
hi!
I've been able to isolate the partcombine brokenness. Here's a score
demonstrating it:
can you verify that this is fixed in CVS?
yes, it works now. thanks!
Erik
The second bar of the first staff is identical to the first bar of the second
staff, yet they are typeset differently. The first staff switches between
chord and polyphony notation too often.
\score {
\new Staff \notes {
\partcombine
\relative c'' {r1 e8 f ~ f d}
\relative c' {c4 c c c e8
hi,
I have a copyrighted score that demonstrates a few problems with \partcombine
in v2.1.35.
1. Weird autobeaming sometimes during Solo II.
2. The text Solo II is repeated each bar even though voice one is silent
(using \skip)
3. Voice two disappears after 14 bars of 22.
4. Look at
On Tuesday 30 March 2004 13.23, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
4. Look at
http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Automati
c-part-combining.html#Automatic% 20part%20combining
In the first example, the stems of the two voices are merged. According
Hi,
The following code produces five warnings
warning: cannot find Voice: A
but the paper output is perfect.
\version 2.1.34
\score {
\new Staff \notes { a4 a a a \context Voice=A {a a a a}}
\lyricsto A \new Lyrics \lyrics { a a a a }
}
The following code gives the same output without
hi,
I made a slur collide with some lyrics, see attached png (hope it isn't
filtered away). The .ly is copyrighted, so tell me if you want the source.
I have:
\context {\StaffContext minimumVerticalExtent = #'(-0.5 . 0.5) }
\context {\LyricsContext minimumVerticalExtent = #'(-0.5 . 0.5) }
On Sunday 28 March 2004 19.24, Erik Sandberg wrote:
hi,
I made a slur collide with some lyrics, see attached png (hope it isn't
filtered away).
It was filtered away. Get it here:
http://peg.it.uu.se/~erik/slur.png
The .ly is copyrighted, so tell me if you want the source.
I have
hi,
I just got a whole bunch of new programming errors. This fairly short snippet
produces:
1. A couple of these:
programming error: minimise_least_squares (): Nothing to minimise
(Continuing; crossing fingers)
2. The following warning:
/tmp/bee/progerror/piano.ly:5:10: warning: Programming
On Friday 26 March 2004 01.49, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
the following:
\version 1.8.0
\score {
\notes \grace {\property Voice.Stem \set #'stroke-style = #'() c4}
}
is converted to:
\version 1.9.0
\score {
\notes \grace {\property Voice.Stem \set
On Friday 26 March 2004 01.47, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
It might be too much to demand that convert-ly should upgrade
#'(italic Simile)
to
\markup {\italic { Simile }}
, but the movement of a parenthesis movement is IMHO a clear bug, as
opposed to a
the following:
\version 1.8.0
\score {
\notes \grace {\property Voice.Stem \set #'stroke-style = #'() c4}
}
is converted to:
\version 1.9.0
\score {
\notes \grace {\property Voice.Stem \set #'stroke-style = #'( c4)}
}
(after fixing this error manually, the file is converted correctly to
The chord-naming scheme is consistent with Ignatzek's book. If you
prefer another system, you're welcome to code support for it.
Han-Wen
(Getting very tired of yet another chord name request)
I'm just curious: Does this book say that \chords c^3 and \chords c should be
typeset identically?
On Sunday 21 March 2004 01.57, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
1. The piece header is written in smallcaps. I can't recall that I got
any answer of why it should, so perhaps it is a bug after all.
Example:
\score {\notes b \header {piece=Allegro} }
fixed.
Not quite..
hi,
\new ChordNames \chords c^3
gives me a plain C. Shouldn't there be something more? like C-3 or
something?
(I know almost nothing about notation standards when it comes to chord names;
however I know that this particular chord should have _something_ more)
Erik
hi,
It seems that any syllables after a slurred syllable are not output to midi.
\version 2.1.33
\score {
\context Voice=A \notes {a16( a) b c d e f }
\lyricsto A \context Lyrics \lyrics { a b c d e f }
\paper {}
\midi {\tempo 4=100}
}
output: a midi file with an 'a' as its only
hi,
the following code results in the below warning, incorrect output.
\version 2.1.32
\score {
\notes \relative c'' { {\grace e8 d2} \\ g2. }
}
/tmp/2-mand1.ly:4:43: warning: Too many clashing notecolumns. Ignoring them.:
\notes \relative c'' { {\grace e8 d2} \\
hi,
Under Changing defaults, there are two subtopics Fonts and Font size.
Under Fonts there is a topic Selecting font sizes:
# Fonts
* Selecting font sizes
* Font selection
# Text markup
* Overview of text markup commands
# Global layout
* Vertical spacing
* Horizontal
hi,
What is the intended future of \addlyrics? Will it remain there as an
undocumented feature until someone writes a huge convert-ly converter to
\lyricsto, or will it be abruptly removed in v2.4 or something?
And in any case: Wouldn't it be reasonable if anyone who tries to use
\addlyrics
The roadmap for the coming weeks is as follows: my plan is to finish
rewriting the manual chapter on Changing Defaults and release
version 2.2 after that (ETA: about one week).
Does this mean that you now basically have frozen the syntax for 2.2? (in that
case I'll perhaps start
Hi,
There is one thing that I miss in the autobeaming: It seems that if a beam
starting point has been found, but the Voice suddenly ends abruptly, without
having reached a natural beam ending point, then no beam is created. IMHO,
the beam should instead be finished at the last note of the
Repeat barlines are engraved to the left of the key signature in .27:
\version 2.1.27
\score { \notes {\key f\major a1 \break \repeat volta 2 {a1} }}
Erik
attachment: foo-page1.png___
Bug-lilypond mailing list
[EMAIL PROTECTED]
2.1.27 reprorts:
programming error: Multi_measure_rest::get_rods (): I am not spanned!
(Continuing; crossing fingers)
Should I isolate an example?
Erik
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
On Wednesday 25 February 2004 01.57, Ruven Gottlieb wrote:
Hi,
I'm using Lilypond on a CCRMA Fedora dist. I updated Lilypond to 2.1.26
from your site.
I can't get tied notes to play properly through MIDI in either the
2.1.25 or 2.1.26 versions. Tied notes just play like seperate notes.
Hi,
\override Staff.autoBeamSettings is not converted to
override-auto-beam-setting by convert-ly.
Erik
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
On Monday 23 February 2004 09.11, Jan Nieuwenhuizen wrote:
Erik Sandberg writes:
2.
./autogen does not report when guile 1.6 header files are missing.
huh? Are you sure?
autogen runs configure, so it will complain as much as configure.
Yes, but configure doesn't complain
On Monday 23 February 2004 12.38, Han-Wen Nienhuys wrote:
Hi guys,
Lilypond 2.1.26 is released. This release fixes a nasty memory
corruption error, which I finally found with Valgrind. I've also
patched GUILE so that similar bugs are easier to catch in the future.
However, it still crashes
Hi,
Sometimes I can't play lily's midi output. Changing something irrelevant can
fix the problem.
I'm using timidity for midi output. Attached are the midi files I get.
\version 2.1.26
\score { % this produces playable output ...
\notes { \notes c2 }
\midi {\tempo 4=140}
}
\score { % ...
hi,
when there's no \paper block but a \midi block in my \score, I get these angry
messages, though everything works fine (apart from the other bugs I reported,
of course :) )
lilypond: warning: no LilyPond output found for `foo'
Running latex...
Running dvips...lilypond: error: `dvips' failed
On Monday 23 February 2004 00.32, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Hi,
While compiling from sources, I found these minor issues:
1.
./autogen says
See INSTALL.txt for more information on how to build LilyPond
...but INSTALL.txt doesn't exist.
2.
./autogen does
There are layout problems when there are multiple staves, of which one ends in
a \bar ||.
I am not sure exactly how it should look, but the current output looks a bit
strange:
\version 2.1.25
\score {
\new StaffGroup \notes
\new Staff {c4 c c c | c c c c \bar || c c c c}
\new Staff {c4
Look at:
out-www/lilypond/Automatic-part-combining.html
The two examples are in different octaves, for no apparent reason.
(this is from my local lilypond-doc 2.1.25; the images are broken in the web
version)
Erik
___
Bug-lilypond mailing list
Hi,
While compiling from sources, I found these minor issues:
1.
./autogen says
See INSTALL.txt for more information on how to build LilyPond
...but INSTALL.txt doesn't exist.
2.
./autogen does not report when guile 1.6 header files are missing.
Erik
On Tuesday 17 February 2004 22.36, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
The file Documentation/user/out-www/lilypond.html, have links on the form
Documentation/user/lilypond-internals/StaffSymbol.html
which should be
hi,
I'm still using .23, fearing the .24 sig 11 crash. I get the following
partcombine crash, please tell me if I should minimise an example.
~/musik/savor/Bive il rey David$ lilypond --verbose score
lilypond (GNU LilyPond) 2.1.23
Opening pipe `/usr/bin/lilypond-bin --version '
Opening pipe
2.1.23 seems to ignore ties when producing midi (this also affects lyricsto).
Erik
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
The file Documentation/user/out-www/lilypond.html, have links on the form
Documentation/user/lilypond-internals/StaffSymbol.html
which should be
Documentation/user/out-www/lilypond-internals/StaffSymbol.html
Erik
___
Bug-lilypond mailing list
[EMAIL
Hi,
fontSize seems to be broken for lyrics. Using it has no effect for me
(2.1.23). And font-size doesn't scale lyric hyphens.
Erik
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
On Wednesday 11 February 2004 11.59, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
On Monday 09 February 2004 13.42, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
I have caused the following 2.1.19 crash, during \partcombine. If you
need an example of a .ly causing it, tell
On Monday 09 February 2004 13.42, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
I have caused the following 2.1.19 crash, during \partcombine. If you
need an example of a .ly causing it, tell me (though I don't have the
time right now)
But it is something like \partcombine {8 bars
On Tuesday 10 February 2004 00.26, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
NEWS
* Melismata in lyrics are also properly handled in the MIDI output.
There are still examples where I get lyrics barcheck warnings during MIDI
output but none during paper output. Is this a
This score, which seems correct to me, gives a couple of warning: Cannot find
Voice: A warnings (one for each c16). The output looks as expected, and
there seems to be no reason for this warning to be displayed.
\version 2.1.19
\score {
\new Staff \context Voice = A \notes f1
\lyricsto A
hi,
There seems to be an input related bug.
When running lilypond - foo.ly in the same directory as the attached file,
using Pedro's 2.1.19 package, I get the following error during midi output.
It goes away if I e.g. remove one of the commented lines.
/tmp$ lilypond - foo.ly
lilypond (GNU
lilypond -h
says, among other things:
--no-psdo not generate PostScript outpug
That should be output, right?
Erik
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
Hi,
I know this feature has been requested flamed before, but.. I think it would
be useful with a --no-midi option. The reason raised the previous request,
was that --no-midi would be time saving, which I agree isn't a very strong
reason by itself. But I have 3 more reasons:
1) It feels
With 2.1.18 there are still the same problems with __ . When playing around
with the extender example at The-Lyrics-context.html, I got to this another
example. Removing the explicit \time 4/4, that overrides the default \time
4/4, *does* change the apperance of the extender in this case, *and*
Hi,
The following produces an incorrect barcheck warning during MIDI output. Very
small random changes in the \notes section will spoil the warning, e.g.
replacing a4.~a4 a8 by a4. a.
Using 2.1.16, Pedro's package.
/erik
\version 2.1.16
\score {
\addlyrics
\notes {
\time 6/8 a8
On Monday 02 February 2004 12.46, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
never could spot a semantical difference between using Lyrics and
LyricsVoice, I have used both randomly). Removing Lyrics, or making the
distinction between Lyrics and LyricsVoice more clear in the docu,
New bug found: The following code
\version 2.1.16
\score {
\context Voice=A \notes { c }
\lyricsto A \new Thread \lyrics { a }
}
can't duplicate.
I was still using 2.1.16, Pedro's deb package
erik
___
Bug-lilypond
Here are 2 new examples of bugs in the extender:
\version 2.1.17
\score {
% the extender is not output at all
\context Voice=A \notes { \times 2/3 {a8( a a a a a} a4) r | a16 }
\lyricsto A \context LyricsVoice \lyrics { a __ a }
}
\score {
% the extender is too long
\context Voice=A
Hi,
Using debian testing pedro's 2.1.16 package, I made lilypond crash.
This was while trying to isolate a bug that I first found:
In a piece whose score contained:
\context Voice=A { \songA \songB }
\lyricsto A \context Lyrics {\lyrA }
lyricsto didn't put any syllables under songB's first 2
I just installed the debian package. Something seems broken, no beams are ever
engraved:
\score {
\notes { a8 a a a }
}
attachment: foo-page1.png___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
On Friday 09 January 2004 01.47, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
One rule could be to not print the barcheck failure at a/b warning in a
bar, if a barcheck failure at a/b with the same a and b occured on the
last | of the same staff. But probably there also exist even more
501 - 600 of 622 matches
Mail list logo
