W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 19803] "Fingerprint" is unclear

From: <bugzilla@jessica.w3.org>
Date: Fri, 07 Dec 2012 23:13:39 +0000
To: public-audio@w3.org
Message-ID: <bug-19803-5429-0yJJZbcnOs@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19803

--- Comment #11 from Chris Wilson <cwilso@gmail.com> ---
(In reply to comment #9)
> Actually, I just made an assumption that I'm not sure is valid with all
> platform MIDI APIs: if you unplug device at index 0 while the application is
> running, your reference to a device that was in index 1 still works. I can't
> test this right now, I only have 1 MIDI device home at the moment, does
> anyone know better?

I know in Windows MIDI, once you've grabbed a reference to the device (via
MidiInOpen/MidiInGetID/etc), you have an HMIDIIN or HMIDIOUT handle, which
doesn't change (should continue to work) - but of course, if you enumerated the
devices in a list via midiInGetNumDevs(), called midiInGetDevCaps() to get the
name/etc. BUT NOT A HMIDIIN, THEN disconnected, the list indices are going to
be off.

I think it's similar in CoreMIDI - it all depends when you call
MIDIGetDevice().

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 7 December 2012 23:13:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:03 UTC