Graham Percival wrote:
Brett Duncan wrote:
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Sorry, I can't duplicate on my machine -- which is also 2.11.18,
10.4.8... on a Macbook
> "Graham" == Graham Percival <[EMAIL PROTECTED]> writes:
Graham> Laura Conrad wrote:
>> This is two bugs, but the file is pretty simple. If you really want
>> two different files, I'll split it.
Graham> Are those exhaustive lists of things that convert-ly should do?
It's an
Laura Conrad wrote:
>> This is two bugs, but the file is pretty simple. If you really want
>> two different files, I'll split it.
Graham> Are those exhaustive lists of things that convert-ly should do?
It's an exhaustive list of what should be happening for my Dowland
files and isn
Issue 298: ties, polyphonic, articulation collision
http://code.google.com/p/lilypond/issues/detail?id=298
New issue report by gpermus:
Steve D posted a long email that pertains to ties between single and
multiple voice sections of notation of polyphonic instruments:
http://lists.gnu.org/archive/h
Laura Conrad wrote:
This is two bugs, but the file is pretty simple. If you really want
two different files, I'll split it.
Are those exhaustive lists of things that convert-ly should do? And do
you know when exactly the changes occured? If you can tell me those
things, I could fix it myse
Nancho Alvarez wrote:
The ligature bracket right-end is affected by other voices.
In this example, the first ligature is printed correctly, but not the second
because there is other voice doing quarters.
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=297
I have also two
Issue 297: Ligature bracket affected by other voices
http://code.google.com/p/lilypond/issues/detail?id=297
New issue report by gpermus:
%{
The ligature bracket right-end is affected by other voices.
In this example, the first ligature is printed correctly, but not the second
because there is othe
Thanks, entered as
http://code.google.com/p/lilypond/issues/detail?id=296
Cheers,
- Graham
Dominic Neumann wrote:
I tried to reduce the sample file, but I couldn´t get it smaller than it is
right now. When trying to compile that file under Windows XP with lilypond
version 2.10.16, lilypond cras
Issue 296: bus error, lyrics not in spanner?
http://code.google.com/p/lilypond/issues/detail?id=296
New issue report by gpermus:
Output: (might be related to the crash, might not be)
foo.ly:7:55: warning: programming error: Spanner `LyricExtender' is not
fully contained in parent spanner `Verti
On Wed, Feb 14, 2007 at 01:53:12PM -0800, Graham Percival wrote:
> Mats Bengtsson wrote:
> >Please read the documentation of these flags that you
> >can obtain by
> >lilypond -dhelp
>
> That only works in Lily > 2.11.18, I'm afraid. :(
lilypond -dhelp in 2.10.16 shows
log-file (#f)
Thanks for the report. This is part of
http://code.google.com/p/lilypond/issues/detail?id=34
so I don't think we need to add this as a separate issue.
Cheers,
- Graham
Jay Anderson wrote:
It seems when a piece starts with a grace in a partial measure the
autobeaming for the rest of the piece
Brett Duncan wrote:
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Sorry, I can't duplicate on my machine -- which is also 2.11.18,
10.4.8... on a Macbook instead of Macbook pro,
Issue 295: non-horizontal beam-slope for stretched stems.
http://code.google.com/p/lilypond/issues/detail?id=295
New issue report by gpermus:
%{ Rune:
If beams are force-stretched to the middle staff-line I think they should
be horizontal. In all cases current behaviour, where the 2nd beam starts
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=295
Cheers,
- Graham
Rune Zedeler wrote:
> (not topposting)
If beams are force-stretched to the middle staff-line I think they
should be horizontal. In all cases current behaviour, where the 2nd beam
starts below the 1st be
> (not topposting)
If beams are force-stretched to the middle staff-line I think they
should be horizontal. In all cases current behaviour, where the 2nd beam
starts below the 1st beam even though the pitches are higher, must be wrong.
\version "2.11.18"
{
\relative c''' { c8 d e f g a b4 }
Mats Bengtsson wrote:
Please read the documentation of these flags that you
can obtain by
lilypond -dhelp
That only works in Lily > 2.11.18, I'm afraid. :(
Cameron Horsburgh wrote:
When I try to compile a file foo.ly the -dlog-file switch fails. There
are two modes of failure.
$ lilypo
Please read the documentation of these flags that you
can obtain by
lilypond -dhelp
As far as I can understand, the idea is that if you use
lilypond -dlog-file foo.ly
(which is equivalent to lilypond -dlog-file=#t foo.ly )
then LilyPond should produce a file foo.log.
However, as you have noticed
When I try to compile a file foo.ly the -dlog-file switch fails. There
are two modes of failure.
$ lilypond -dlog-file=log foo.ly
compiles cleanly but no log file is produced.
If I change the name of the log file to foo.log an error is produced:
$ lilypond -dlog-file=foo.log foo.ly
Hi,
I tried to reduce the sample file, but I couldn´t get it smaller than it is
right now. When trying to compile that file under Windows XP with lilypond
version 2.10.16, lilypond crashes with the typical Windows window that says that
there´s a problem with lilypond and it has to be closed.
Than
In making some changes to a file I had created with LP 2.8, it
unexpectedly broke under 2.10.14.
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Here's a small example of what doesn
20 matches
Mail list logo
