Hi Pizza, > > I've been trying to work out what the bytes are before song position 33. I > > thought they might be the MTrk or MThd headers but they aren't. > > (I don't heve the exact stuff now, so bear me out) > > 0) Standard SCI resource header > 1) track polyphony > 2) play code (ie what channels a device should play) > 3) ?? (can't remember) [snip]
Like Christoph said, it's described in the on-line docs. They are bytes for initialising the channels. 16 channels * 2 bytes = 32, + 1 byte for the number of channels code. > > Secondly, I've written a little procedure to dump out a song's data but I'm not > > sure if it's correct. Attached is an example. You'll notice that some of the > > midi commands aren't in the 0x80 to 0xFF range, so what are they? > > Dare I ask why you're reinventing the wheel? We already have code to > create MIDI0 files from SCI0 sound resources. I'm not trying to create MIDI0 files here, I'm outputting the values to the screen in human readable form so I can better understand the source and implement this somewhat different sound server er... implementation. I want to see exactly how a song's data appears to the sound server. By the way I can't find either the sci_dump.c file or the dump_midi_0 function. It's probably not relevant though because I want this in human readable form. > Anyhow. I can answer more questions, but I'll need the source in front > of me. Perhaps later today on IRC.. Sorry I'm too busy right now / this week for IRC! Alex. > > - Pizza > -- > Solomon Peachy pizzaATfucktheusers.org > I ain't broke, but I'm badly bent. ICQ# 1318344 > Patience comes to those who wait. > ...It's not "Beanbag Love", it's a "Transanimate Relationship"... > > -- Attached file included as plaintext by Listar -- > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE7yuPcysXuytMhc5ERAkz+AJ9K2/XMs91hx4dBKRnj3fPXzcjyqwCdEUj9 > GQhGTc2bE4qbzVx25Ol098o= > =2B/J > -----END PGP SIGNATURE----- > > >
