W3C home > Mailing lists > Public > public-tvapi@w3.org > June 2015

Comments on Media Capture and Streams Specification

From: HU, BIN <bh526r@att.com>
Date: Thu, 11 Jun 2015 20:53:11 +0000
To: "public-media-capture@w3.org" <public-media-capture@w3.org>
CC: "Chris Needham (chris.needham@bbc.co.uk)" <chris.needham@bbc.co.uk>, "Paul Higgs (paul.higgs@ericsson.com)" <paul.higgs@ericsson.com>, "Sean Lin (selin@mozilla.com)" <selin@mozilla.com>, "ashimura@w3.org" <ashimura@w3.org>, Dan Burnett <dburnett@voxeo.com>, "public-tvapi@w3.org" <public-tvapi@w3.org>
Message-ID: <179FD336116F754C876A9347238FE29A03FC7EC2@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Hello folks,

How are you? I am Bin Hu, Chair of TV Control API Community Group. Sean Lin is our Editor, and Chris Needham and Paul Higgs are our active contributors and SMEs in our group.

We are working on an API to integrate broadcast TV into HTML, allowing playback of video and audio streams from a TV tuner, channel selection, program information, and so on.

In our draft specification [1] we've currently used MediaStream as the way to attach the TV tuner source to an HTMLMediaElement, using the srcObject attibute.

One of our requirements is buffering of the video and audio streams, which is needed to support use cases such as pausing and resuming of the media, seeking within the buffered region after pausing, and returning to the current 'live' position.

In [2] we've compiled a detailed list of the areas we've found in MediaStream that we'd want to change to adapt it for our use cases. In other respects MediaStream looks suitable for use with TV streams, such as the changes to the HTMLMediaElement's resource loading algorithm, and the support via the srcObject attibute.

We realise that we've passed the deadline for comments on the Media Capture and Streams spec, but we wanted to let you know about our work, and invite feedback on how to proceed, for example, would our requirements might be considered in a future version of Media Capture and Streams, should we propose an extension specification, or produce our own stand-alone specification?

Please let us know, and your guidance and feedback is greatly appreciated.

With warmest regards

Bin Hu

Chair, TV Control API Community Group

[1] https://w3c.github.io/tvapi/spec/

[2] https://lists.w3.org/Archives/Public/public-tvapi/2015Jun/0000.html
Received on Thursday, 11 June 2015 20:54:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:45:14 UTC