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

RE: tvapi-ACTION-24: use of Media Capture to realize recording requirements

From: Paul Higgs <paul.higgs@ericsson.com>
Date: Thu, 19 Feb 2015 22:34:28 +0000
To: "public-tvapi@w3.org" <public-tvapi@w3.org>
Message-ID: <9681F60D17697C41A146FC70CD4B48D61DFD8001@eusaamb103.ericsson.se>
Following the "chain-of-specifications" a little further, it seems that the File API [5] specification can only construct a file from a single Blob (the blob is the output from the MediaStream Recording API).
It would be beneficial for our purposes if the File API included an "append( blob )" methods, then the first blob received from the recording could be used to create the file which subsequent blobs could be appended to.

It would probably be unrealistic to expect an single in-memory blob to contain an HD recording of an hour or more (given that would be 4+ GB of HD content)

Paul

[5] http://www.w3.org/TR/2013/WD-FileAPI-20130912/

From: Paul Higgs [mailto:paul.higgs@ericsson.com]
Sent: Thursday, February 19, 2015 3:38 PM
To: public-tvapi@w3.org
Subject: tvapi-ACTION-24: use of Media Capture to realize recording requirements

Hi

During the February 17 TV Control API conference call, I took an action [1] to review the MediaStream Recording API [2] for its relevance and use in fulfilling the requirements around recording [3]

It is possible to see that an TVTuner defined in the TV Control API can "output" via a MediaStream which can then me recorded through the MediaRecorder API. In order to do this, the MediaRecorder constructor requires the mime type of the TVTuner output, so a "readonly attribute DOMString  mimeType" attribute should be added to the TVTuner interface.

At a period denoted by the timeSlice property, the ondataavailable event handler is trigger, an argument to which is the recorded data. The application implementing this handler would then need to write the capture stream data to a file (perhaps via the File API [4]). The MediaStream Recording API also has the ability to throw a "MediaRecorderErrorEvent" with name=OutOfMemory

What this means is that there is no native recording functionality in the device implementing TVManager.  Instead one of the applications running on the terminal is the "recording scheduler" (how that application gets and manages data is probably application specific). Note that this requires the UA support some form of "background application".

In essence, the requirement mapping table should, for each of the [recording.*] requirements, state "not supported, realized through the webapp and MediaStream Recording API"


[1] http://www.w3.org/community/tvapi/track/actions/24
[2] http://www.w3.org/TR/mediastream-recording/
[3] https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement#Program_Recording_Requirements
[4] http://www.w3.org/TR/FileAPI/


[Description: Description: Ericsson]<http://www.ericsson.com/>
PAUL HIGGS
Technical Solutions Manager
Ericsson Inc

Ericsson
6 Concourse Parkway, suite 400
Atlanta, GA 30328, United States of America
Phone +1 (650) 580-1731
paul.higgs@ericsson.com
www.ericsson.com


[Description: Description: http://www.ericsson.com/current_campaign]<http://www.ericsson.com/current_campaign>

Legal entity: Ericsson AB, registered office in Kista, Sweden. This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>

image001.gif
(image/gif attachment: image001.gif)

image002.gif
(image/gif attachment: image002.gif)

Received on Thursday, 19 February 2015 22:35:06 UTC

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