From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro Bug!!!
Date: Wed, 18 Mar 1998 19:16:52 +0000
Organization: None
Message-ID: <lUAKhPAk2BE1EwZo@talula.demon.co.uk>
References: <01bd506d$4d3ad300$3548a5c6 AT technoid>
 <xpPfegAFpsD1EwQ5 AT talula DOT demon DOT co DOT uk> <01bd5144$56af58c0$3548a5c6 AT technoid>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 24
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Luke Bishop writes:
>Well, the file could just be truncated at 32 channels instead of failing...

But if Allegro can't handle a file properly, surely it is better to give
an error so that the user knows something needs to be adjusted, rather
than to just quietly do the wrong thing and not warn them?

>Also, I recently found a MID which works fine in windows but will not work
>AT ALL in Allegro, due to a different reason.  This file has a header of
>"RIFF", and is what appears to be a windows RIFF file with an imbedded MIDI
>inside it.

That isn't actually a proper MIDI file: it is a Microsoft invention
which basically says that you can embedd various different multimedia
formats, including standard MIDI format data, into one of their RIFF
structures. Giving this a .mid extension was IMHO a horrible idea,
because it really isn't the same format at all! But this is a part of
their standard design methodology: "why use existing standards when we
can invent new and worse ones of our own?" :-)


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
"Pigs use it for a tambourine" - Frank Zappa