Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!texbell!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.mail.multi-media Subject: Re: Musical information coding Message-ID: <6417@ficc.uu.net> Date: 4 Oct 89 17:09:37 GMT References: <3830@vtt.vtt.fi> <2236@randvax.UUCP> Organization: Xenix Support, FICC Lines: 18 In article <2236@randvax.UUCP>, salzman@randvax.UUCP (Isaac Salzman) writes: > there exists a standard "MIDI File" format. It has the notion of tracks > and sequences for transferring song data. it also handles non-MIDI events > and MIDI system exclusive events, so you can store comments and synthesizer > specific information (synth patches, etc.). Not only that, but the Midi File Format is a subset of the Electronic Arts/ Commodore Interchange File Format. A trivial translation (adding a 12-byte chunk to the beginning of the file, and padding odd-sized chunks to an even byte boundary) and it's compatible with the existing IFF standards for digitized sound, images, animations, formatted text, and so on. This lets you create a single file that includes not only the music but the instruments, notation, animations, and other elements of a multimedia document. -- Peter da Silva, *NIX support guy @ Ferranti International Controls Corporation. Biz: peter@ficc.uu.net, +1 713 274 5180. Fun: peter@sugar.hackercorp.com. `-_-' ``I feel that any [environment] with users in it is "adverse".'' 'U` -- Eric Peterson