- From: Chris Needham <chris.needham@bbc.co.uk>
- Date: Thu, 27 Oct 2016 16:29:29 +0000
- To: "public-tvcontrol@w3.org" <public-tvcontrol@w3.org>
Hi all, On the last phone call [1], we talked about routing of media to different zones in an in-car entertainment system, or between devices in the home. The Audio Output Devices API [2, 3] adds a setSinkId method to HTMLMediaElement, where sinks are output devices defined by WebRTC - see the enumerateDevices method in the MediaDevices interface [4]. As we discussed, I don't think such media routing is in scope for our WG, but I'm wondering whether the Audio Output Devices API, together with the TV Control API, would help with this use case? Or if not, where are the gaps/issues? Chris (WG Chair) [1] https://www.w3.org/2016/10/18-tvapi-minutes.html#item03 [2] https://www.w3.org/TR/2016/WD-audio-output-20161014/ [3] https://lists.w3.org/Archives/Public/public-review-announce/2016Oct/0007.html [4] https://dev.w3.org/2011/webrtc/editor/archives/20140619/getusermedia.html#dom-mediadevices-enumeratedevices
Received on Thursday, 27 October 2016 16:30:43 UTC