[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: incompatible stem (type = 16)

From: Mats Bengtsson
Subject: Re: incompatible stem (type = 16)
Date: Thu, 15 Mar 2007 17:42:49 +0100
User-agent: Thunderbird (X11/20070221)

As far as I know, this warning message should only appear if you have
several simultaneous notes, such as
\relative c' \new Voice <<
 {c16 d e f g2. }

but in your example it seems that you only have a single voice and
no simultaneous notes, so I have no idea what is going on. It might
be related to the next warning message, though:

programming error: moving backwards in time

I don't have version 2.10 available here, so I cannot look at the
output and see what LilyPond does. As you have noticed, version
2.11.20 seems to hang (the process takes most of the processor load).

In noticed that if you remove the outer of the nested tuplets, then the
file processes quickly and you don't get these warnings.


karim haddad wrote:
Hello list

In this .ly file (very unconventional) i have a problem with :

/Users/hyperion/Desktop/lilbug/6.ly:72:0: warning: adding note head to incompatible stem (type = 16)


although c'1 is a whole note and should has no stem

Even weirder, this works with the 2.10 version which  reports the error,
but in the latest version 2.11.20-1 i have the error and lilypond just hangs...

Any ideas ?

Another thing but this is no bug i presume . when i call lilypond fron my terminal i get

hyperion$ lilypond
Rebuilding font cache
This may take a few minutes.GNU LilyPond 2.10.20

and this when i try version from version.

I tried to look for this variable, but didn't find it
I defined it in my .bash but no way?




bug-lilypond mailing list

        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe

reply via email to

[Prev in Thread] Current Thread [Next in Thread]