On Monday 03 February 2003 1:43 pm, Joe Hartley wrote: > On Mon, 3 Feb 2003 09:52:06 +0200 > > Jaakko Prättälä <Jaakko.Prattala@xxxxxxxxxxx> wrote: > > It might be that there should be a SysEx start message and a > > manufacturer ID before the data and a SysEx end message after. > > > > For Antares these would be > > 0xF0 0x00 0x01 0x26 [data here...] 0xF7 > > According to the manual, the SysEx header stuff is in place, but > od -xc shows me something else - the first 32 bytes are: > > 0000000 544d 6468 0000 0600 0000 0100 6000 544d > M T h d \0 \0 \0 006 \0 \0 \0 001 \0 ` M T > 0000020 6b72 0000 760d f000 729a 0100 1126 0007 > r k \0 \0 \r v \0 ð 232 r \0 001 & 021 \a \0 Maybe it's some kind of header in the midi file? > Here's a naive assumption on my part: since the MIDI Out on the > Delta panel is lighting up, there's data going out on the port. > > I'll start looking more closely at the SysEx header stuff and the actual > file format now - thanks for the help! Are you using cat or playmidi to play the file? The cat method will dump the data to the midi port, but it could be in the wrong format. A really handy way to find out what sysex data is in a midifile are the utilities mf2t and t2mf, which convert midi files into human-readable text files and vice verssa. I believe they are included in the latest version of scala from http://www.xs4all.nl/~huygensf/scala/downloads.html
