Hi Alex, > This is looking good, I just have a few questions for now since the document > is not yet finished.
Sorry about that. I will try to see if I can finish it this weekend. > 1. It looks like the track player can either use a track block > (set_track_block()) or song iterator (set_song_it()) to get song data from. > Is this correct? Yes, exactly. > 2. If so, presumably the song iterator type would be the one that can > provide extra mapping, etc.? That's right, too. > 3. Is it correct that make_track_block() can make blocks from either a track > block or song iterator type? The way it's currently defined is that it is used iff a block-style access is used. In this case, the block referenced by 'src' will usually have been generated by a song iterator. This function is optional, too. It's intended to allow MIDI player implementations to add padding and similar stuff (the documentation should point out that it will only be used for one single MIDI command). > 4. Would something like mt32gm mapping occur by using another song iterator > that alters data that would normally go to an mt32? That is, a song iterator > on top of a song iterator? Yes. > Thanks, You're welcome! llap, Christoph
