Hi Christoph, > I'll first have to know what you mean with 'needing the device level' > there.
What I've been meaning with that is something I thought someone mentioned, somewhere... Pizza previously wrote a few lines regarding what the various levels could be but I can't find that e-mail presently. So am I correct by saying that these could be the various song iterator levels: Level | Example ---------------------------+--------------------------------------------- SCI MIDI | General MIDI | mt32gm MIDI-to-file | Device | adlib(emu), mt32 (device itself) OS Subsystem | Win32 MCI Program | timidity I'm sure I've missed something here. Also, if we knew for sure what MacOS X needed then that might add another level perhaps. Then of course the question is how to interface between them all and perhaps also ensure that nonsense level combinations cannot occur (e.g. using adlib at the device level with the timidity program). > Right now, song iterators (are supposed to) fully support song decoding, > including looping. No translation has been implemented yet, and neither > has serialization or de-serialization. When you say song iterators support looping, does that mean the sound servers won't have to worry about looping back themselves? That is, in effect the sound servers won't know about this, or? I haven't had time to read your draft spec yet Christoph (which may answer what I've written above), but hopefully after Saturday. Cheers! Alex.
