Re: \tempo does not work

[Ed Baskerville]

This has been documented before, right here:

http://lists.gnu.org/archive/html/bug-lilypond/2004-02/msg00346.html

There's been a debate as to whether it's LilyPond's fault or  
QuickTime's fault. Whoever's fault it really is, I suspect it's far  
easier to get this kind of thing to be fixed in LilyPond than in  
QuickTime.

I'm particularly struck by this comment from Nigel Warner about some  
LilyPond MIDI output:

> This is not good MIDI. In a format 1 file, a file containing multiple
> tracks, Tempo changes should only appear in the Conductor track,  
> track 0,
> which should only contain System Common messages. Quicktime, and other
> MIDI file players, are within their rights to ignore tempo changes,  
> key
> signatures and time signatures which appear in tracks other than 0  
> which
> should only contain Channel Mode messages and Meta Events.

I imagine putting tempo changes in other tracks is because,  
theoretically, a piece might have different tracks in different  
tempi? If that's the case, can data also be added to track 0 so that  
players like QuickTime at least work for *most* LilyPond MIDI output,  
if not all?

A temporary workaround is to use another program, such as Mighty  
MIDI, which you can find on VersionTracker.

--Ed

On Feb 7, 2006, at 5:21 PM, Marius Amado Alves wrote:

> \tempo does not seem to be working
>  for at least two users with configuration
>  Mac OS X 10.3, LilyPond 2.6.5,
>  QuickTime Player 7.0.4.
>  It does not have an effect on the MIDI output.
>
>
>
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-lilypond