Issue metadata
Sign in to add a comment
|
MIDI devices are not found unless multi-app and already in use
Reported by
ch...@w3.org,
Mar 31 2016
|
||||||||||||||||||||
Issue description
<b>Chrome Version : <Copy from: 'about:version'></b>
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Connect a MIDI device, like a keyboard
2. Check (e.g. with MIDIOX, or the control panel) that the MIDI device is found. Close MIDIOX.
3. Run the MIDI Listing 'Inputs and Outputs' from the WebMIDI spec. It finds no inputs or outputs.
What is the expected result?
It finds my keyboards, etc
What happens instead of that?
It only finds them if
a) they use vendor-supplied drivers, not the Microsoft one, and
b) MIDI-OX or some other application is already running and has opened the MIDI devices first
Please provide any additional information below. Attach a screenshot if
possible.
The Microsoft MIDI driver is single-application only, so it always fails with Chrome. Vendor drivers are often multi-application, so if another app starts up the MIDI devices first, Chrome can then find them with WebMIDI.
It should be possible for WebMIDI in chrome to find the devices without relying on a more capable app to start them up first.
,
Apr 2 2016
Thanks for the response. I am not sure if that behaviour is mandated by spec, so I opened https://github.com/WebAudio/web-midi-api/issues/160
,
Apr 5 2016
Let me merge this to the existing bug. Unfortunately, usage isn't so high for polishing platform dependent minor edges. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by brajkumar@chromium.org
, Apr 1 2016