Well the problem occurs, when compiling the MIDI.bmx example, closing it pressing escape key, then one minute or 2 latter, recompiling it, it reports than midi.exe or midi.debug.exe is currently in use (so not closed properly although the exe doesn't appear in task manager anymore). It does it but not *always*, I tried a delay before closing bmx program (similar to the one after sysex_initialize), but it still happens "randomly".
My test system is WinXP pro, with a MAudio midisport Uno USB (input 1, output 4 in my setup) and a doepfer pocketdial (I have a Kaoss pad II, and a pocketfader as well but not wired currently).
I want to support Midi controllers principally (on the 3 platforms, from there comes my interest for portmidi), but some of them require midi feedback/ouput (to update a display or a motorized fader for example).
With Blitz3d I did a midichannel based dll (not based on devices), reading/writing midi messages only (the 3 nibbles).
My test system is WinXP pro, with a MAudio midisport Uno USB (input 1, output 4 in my setup) and a doepfer pocketdial (I have a Kaoss pad II, and a pocketfader as well but not wired currently).
I want to support Midi controllers principally (on the 3 platforms, from there comes my interest for portmidi), but some of them require midi feedback/ouput (to update a display or a motorized fader for example).
With Blitz3d I did a midichannel based dll (not based on devices), reading/writing midi messages only (the 3 nibbles).