MIOS32 USB MIDI workaround for Windows: new attempt

[TK.]

I'm asking for a confirmation from experienced MIDIboxers who are working under Windows:

 

In the past, a MIOS Studio Query and .hex upload didn't work for applications which applied more than one USB MIDI port. We found out, that data transfers were working again if the Query button was pushed multiple times. The reason why this helps is still unknown (only Microsoft could help us to find the answer... no hope ;-).

 

The proposed workaround was to install the GM5 MIDI driver, or to force MIOS32 to use a single USB MIDI port, but this resulted into unwanted quirks and limitations.

 

Meanwhile I think that it's better to add workarounds into MIOS32 so that at least the communication with MIOS Studio is working properly under all circumstances, so that newbies (who don't know the details) don't need to be aware of this special knowledge.

 

Therefore I added a workaround into MIOS32, which sends 256 dummy "Runtime Status" events during a Query. They are not displayed by MIOS Studio, so that nobody should notice it - but a Query should always work during startup - no need to push the button multiple times anymore!

 

Could you please check one of following applications at your side without the GM5 driver, and without "single_usb" configured in the MIOS32 bootloader:

http://www.ucapps.de/mios32/midibox_ng_v1_029_pre1.zip

http://www.ucapps.de/mios32/midibox_seq_v4_081_pre1.zip

http://www.ucapps.de/mios32/midio128_v3_018_pre1.zip

 

After the installation, MIOS Studio should

- always detect the core after power-cycle

- each Query should work

- application upload should always work

 

if not, please let me know!

 

Best Regards, Thorsten.