For MS Smartphone 2003 platform, it is really not an easy thing to deal with MIDI playback. Here are several solutions, but every way has its own problems.
1. Use SDK raw API. Refer to http://homepages.inspire.net.nz /~ Gambit/MIDI/problem:-rough playback quality. it is only a prototype. when I tested with that source code, the playback quality is so rough. I spent some time to modify that source code and failed to fix the problem. BTW: the problem of B in that article is due to the Code: wavehdr. lpdata = (lpstr) & midimessage; // If changed to (lpstr) midimessage, dynamic memory allocation shocould work. as we know, for array, & midimessage is equal tomidimessage, but for pointer it is different.2.port open MIDI source projects to smartphone platform I 've found two open MIDI source projects which are very good. one is timidity and the other is wildmidi. famous famous games such as quake and duke3d uses timdity to play MIDI sound. problems:-it will take some time. -It will add much more footprint to your application installation package due to its usage of Gus patches. 3.buy MIDI codec currently it seems some company sells MIDI codec for MS Windows Mobile platform. problems:-it will take some money. usually those companies want a lot of money. so it is the least recommended.4.use existing library api I spent some time to analysis the Midi issue of the default player within dopod565 itself. I found that the player uses a dll library ---- midilib2.dll which is in/Windows directory. the export information of midilib2.dll is attached later. midi_getduration
Midi_getextensioninfo
Midi_getinfo
Midi_getposition
Midi_getstatus
Midi_getvendorid
Midi_getvolume
Midi_getwaveout
Midi_load
Midi_pause
Midi_play
Midi_resume
Midi_setvolume
Midi_stop
Midi_unload
Fp_midi_getduration
Fp_midi_getextensioninfo
Fp_midi_getinfo
Fp_midi_getposition
Fp_midi_getstatus
Fp_midi_getvendorid
Fp_midi_getvolume
Fp_midi_getwaveout
Fp_midi_load
Fp_midi_pause
Fp_midi_play
Fp_midi_resume
Fp_midi_setvolume
Fp_midi_stop
Fp_midi_unload
The DLL file is not open to public for use. for DLL files, we cocould only get function name information, and we couldn't find function declarations including parameters and return type. I think the best way to handle MIDI playback problem is to ask for handset provider 'stechnical support and ask them to open MIDI API (for dopod565, the API of midilib2.dll ).