Re: [spec-reviews] Audio Output Devices API (#91)

I've looked this over today.

## Audio Output Devices API
Reviewed: https://w3c.github.io/mediacapture-output/ (25 November 2015)

**My takeaway**: The design and concepts are simple and integrate well with other Web RTC concepts (e.g., the `enumerateDevices()` API). While I don't really like the name (`sinkId`; more below), otherwise, the integration points are fine. I note (as also noted above), that we don't yet have a fundamental concept of an audio/multimedia engine that would provide the substrate for features like this, though to be fair, this feature is only related to such an engine on the output edge (not tied to primitive operations--though it does describe starting/stopping audio).

Specific feedback:
* `sinkId` is only for Audio? The name seems a bit ambiguous when applied to `HTMLMediaElement` (audio + video). In the context of a video element, `sinkId` could be confusing.
* `id-communications` -- is the issue resolved with how to deal with headsets?
* `id-communications` - what happens when this value is assigned, yet no comm device is available? The processing model needs to include specifics on handling these special values.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/91#issuecomment-164919172