Author |
Topic: midioutGetNumDevs (6.5.1.346) (Read 2117 times) |
|
mmckenzie
New Member

 MIDI-OX Rules!
Posts: 3
|
 |
midioutGetNumDevs (6.5.1.346)
« on: Apr 19th, 2003, 7:02am » |
Quote Modify
|
Jamie, 1. midioutGetNumDevs On my Dell 8100 notebook with Windows XP and Steinberg Midiex3 USB midi adapter (and, similar effects noted on other machines running 2000) the call to midioutGetNumDevs returns some outrageously high number of midi devices (currently 73 on my notebook). I've not discovered why Windows reports such a number but, it is at least the MAXIMUM valid ID for a midi port. In my software, I iterate through the possible ports 0 to midioutGetNumDevs-1 with a call to MidiOutDevCaps ignoring those ports that return a MMSYSERR_BADDEVICEID error to get the list of valid ports. I only say this, as MIDI-OX 6.5.1.346 complains about 73 ports and then proceeds to generate several error messages as it tries to access the myriad invalid port ids and then won't support the Midiex3 adapter, as it happens to be on port id 69 (this week)! All the best, Matt McKenzie
|
« Last Edit: Apr 19th, 2003, 7:05am by mmckenzie » |
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: midioutGetNumDevs (6.5.1.346)
« Reply #1 on: Apr 19th, 2003, 11:59am » |
Quote Modify
|
Thanks for the report. The only time we've seen anything remotely like this happen is after the hardware for a (badly written) MIDI USB device driver is removed from the system, but the driver is left installed, and the system is then restarted.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
|