midi output bug?

2006-02-06 Thread c.m.bryan
Hello everyone, I've been trying to use lilypond to render midi files which I can then retune with a program called scala (http://www.xs4all.nl/~huygensf/scala/). The midi file which lilypond gives me seems ok, and is playable by timidity, but scala chokes on it and gives me an error. I talking

Re: midi output bug?

2006-02-06 Thread Johannes Schindelin
Hi, On Mon, 6 Feb 2006, c.m.bryan wrote: It turns out Scala is right, your midi file is wrong. There's an unexpected running status inside. So you may have to report a bug for Lilypond. It appears that your midi has this as start of the second track: 4d 54 72 6b // = MTrk 00 00 00 40 // =

Re: midi output bug?

2006-02-06 Thread c.m.bryan
4d 54 72 6b // = MTrk 00 00 00 40 // = chunk length (64) 00 0f f5 80 43 e8 02 12 08 // = probably fscked up time signature A midi time signature would look like 00 ff 58 04 04 02 18 08 Well, if you suspect that it might be an old version, how about telling us which one you use? And if

Re: midi output bug?

2006-02-06 Thread Johannes Schindelin
Hi, On Mon, 6 Feb 2006, c.m.bryan wrote: The strangest part is that I've had success with this procedure before, so something has changed, maybe in a lilypond upgrade? Any help would be appreciated! Me again. Something jumped into my eye: the number 0x3e8. It is exactly 1000 in decimal.

Re: midi output bug?

2006-02-06 Thread c.m.bryan
P.S.: I fixed the two instances of the time signature in your midi file, and since it is so small attached it. That did it!! No more 1000/4 for me ;) Sorry for not suspecting that before, but I don't know a lot about midi files, and I wasn't aware that they contained meter information.

Re: midi output bug?

2006-02-06 Thread Johannes Schindelin
Hi, On Tue, 7 Feb 2006, c.m.bryan wrote: I did a crazy-long time sig because I couldn't remember the cadenza command, and it was just a quick sketch. Maybe that's the problem... Exactly. A midi file can represent only up to 255 beats per measure. Ciao, Dscho