Thanks for the analysis.
I haven't contributed with many lines of code to LilyPond, but I'm
afraid I might be the culprit for this problem. I just found a copy
of a patch I submitted in summer 1999 where I removed the tempo setting
in track 0.
The reason was that I introduced support for tempo cha
Dear All,
After running a check I believe that the problems people
are having with MIDI and Tempo are because Lilypond does
not do "the right thing".
Picking apart the MIDI output for a simple file:
panfluteAA = \notes {
\time 3/4
See also
http://mail.gnu.org/archive/html/lilypond-user/2003-09/msg00228.html
and the other messages of the same thread.
/Mats
Christian Hitz wrote:
Am Mittwoch, 15.10.03 um 21:11 Uhr schrieb Will Oram:
After reading the history of this list, I'm aware that Mac OS X
doesn't much care for MID
Ah, but midi files not created by lilypond plays fine, so it can't be
only a QuickTime problem. I haven't really needed the midi function a
lot, but I'll experiment a bit with it and see if I can find a pattern.
Timidity++ is also available for OS X btw, even if it means wading
through japanes
Am Mittwoch, 15.10.03 um 21:11 Uhr schrieb Will Oram:
After reading the history of this list, I'm aware that Mac OS X
doesn't much care for MIDI tempi set in \midi { }. All pieces are set
to a universal tempo, either 4 = 120 or around that.
The problem is QuickTime. Look on versiontracker.com fo
After reading the history of this list, I'm aware that Mac OS X doesn't
much care for MIDI tempi set in \midi { }. All pieces are set to a
universal tempo, either 4 = 120 or around that.
So I shrugged that off and submitted my finished .ly files to Mutopia
Project, hoping the administrator's Wi
