This document defines a recording API for use with MediaStreams as defined in [[!GETUSERMEDIA]]
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document is not complete. It is subject to major changes and, while early experimentations are encouraged, it is therefore not intended for implementation. The Media Capture Task Force expects this specification to evolve significantly based on:
This document was published by the Web Real-Time Communication Working Group as an Editor's Draft. If you wish to make comments regarding this document, please send them to public-media-capture@w3.org (subscribe, archives). All feedback is welcome.
Publication as an Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures (Web Real-Time Communication Working Group, Device APIs Working Group) made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This API attempts to make basic recording very simple, while still allowing for more complex use cases. In the simplest case, the application instatiates the MediaRecorder object, calls record() and then calls stop() or waits for the MediaStream to be ended. The contents of the recording will be made available in the platform's default encoding via the dataavailable event. Functions are available to query the platform's available set of encodings, and to select the desired ones if the author wishes. The application can also choose how much data it wants to receive at one time. By default a Blob containing the entire recording is returned when the recording finishes. However the application can choose to receive smaller buffers of data at regular intervals.
This specification defines conformance criteria that apply to a single product: the user agent that implements the interfaces that it contains.
Conformance requirements phrased as algorithms or specific steps may be implemented in any manner, so long as the end result is equivalent to the behavior specified in this document.
Implementations that use ECMAScript to implement the APIs defined in this specification must implement them in a manner consistent with the ECMAScript Bindings defined in the Web IDL specification [[!WEBIDL]], as this specification uses that specification and terminology.
UnsupportedOption
Exception. If
this paramater is not specified, the UA will use a platform-specific
default format.
true
, the MediaRecorder will not record anything when the input Media
Stream is muted. If this attribute is false
, the MediaRecorder will
record silence (for audio) and black frames (for video) when the input MediaStrea
is muted. When the MediaRecorder is created, the UA must set
this attribute to false
.MediaRecorder
object’s start()
method is invoked,
the UA must queue a task, using the DOM manipulation task source,
that runs the following steps:
state
is not "inactive", raise a DOM InvalidState
error and terminate these steps. Otherwise:state
to 'recording' and wait until media
becomes available from stream
.start
event and start gathering the
data into a Blob (see [[!FILE-API]]). timeSlice
argument has been provided, then once timeSlice
milliseconds of data have been colleced, or some minimum time slice imposed
by the UA, whichever is greater, raise a dataavailable
event containing
the Blob of collected data, and start gathering a new Blob of data. Otherwise (if timeSlice
has not been provided), continue gathering data into the original Blob.stream
is ended set recording
to 'inactive' and stop gathering data. Callers SHOULD not rely on exactness of the timeSlice value, especially if the timeSlice value is small. Callers SHOULD consider timeSlice as a minimum valuedataavailable
event containing the Blob of data.stop
event.Note that stop()
,
requestData()
, and pause
also affect the recording behavior.
The UA must record the MediaStream
in such a way that the original Tracks can be retrieved at playback time. When multiple Blobs
are returned (because of timeSlice
or requestData
), the individual
Blobs need not be playable, but the combination of all the Blobs from a completed recording must
be playable. If any Track within the
MediaStream is muted at any time (i.e., if its readyState
is set to muted
), the UA
must insert black frames or silence until the Track is unmuted. If the UA is
unable to start recording or at any point is unable to contine recording, it must raise
a DOMError
event, followed by a dataavailable
event containing
the Blob it has gathered, follwed by the stop
event.
MediaRecorder
object’s stop
method is invoked,
the UA must
queue a task, using the DOM manipulation task source, that runs the following steps:
state
is "inactive", raise a DOM InvalideStateError
event and terminate these steps.
Otherwise:state
to 'inactive' and stop gathering data. dataavailable
event containing the Blob of data that has been gathered.stop
eventMediaRecorder
object’s pause()
method is invoked,
the UA must
queue a task, using the DOM manipulation task source, that runs the following steps:
state
is "inactive"
raise a DOM
InvalidState
error and terminate these steps. Otherwise: state
to "paused".pause
event MediaRecorder
object’s resume()
method is invoked,
the UA must
queue a task, using the DOM manipulation task source, that runs the following steps:
state
is "inactive"
raise a DOM InvalidState
error and terminate these steps. Otherwise: state
to "recording".resume
event.MediaRecorder
object’s requestData()
method is invoked,
the UA must
queue a task, using the DOM manipulation task source, that runs the following steps:
state
is not "recording"
raise a DOM
InvalidState
error and terminate these steps.
Otherwise:dataavailable
event containing the current Blob of saved data. (Note that this Blob
will be empty if no data has been gathered yet.)This method must return the
empty string if mimeType
is a type that the user agent knows
it cannot record; it must return
"probably" if the user agent is confident that mimeType
represents a type that it can record; and it must return
"maybe" otherwise. Implementors are encouraged to return "maybe"
unless the type can be confidently established as being supported or not.
The MediaRecorder()
constructor takes one argument which
must be of type MediaStream
(see [[!GETUSERMEDIA]]). When the constructor
is invoked, the UA must construct a new MediaRecorder
object,
set its mediaStream attribute to be the provided MediaStream, set its state attribute to 'inactive'
and return the object.
[TO DO: Provide API surface to set and read these. When that is done, this section will be removed.]
Property Name | Values | Notes |
---|---|---|
MimeType | DOMString |
The MIME type that was be selected as the container for recording. This entry includes all the parameters to the base MimeType. The UA should be able to play back any of the MIME types it supports for recording. For example, it should be able to display a video recording in the HTML <img> tag. The default value for this property is platform-specific. |
BitRate | long |
The bitrate type that was selected as for recording. The default value for this property is platform-specific. |
ignoreMutedMedia | boolean |
If this property is set to 'true', the MediaRecorder should stop recording when the MediaStream is muted. If it is false, the MediaRecorder should record silence (for audio) or black frames(for video) when the source MediaStream is muted. The default value for this property is true. |
Errors are indicated in two ways: exceptions and objects passed to
error callbacks. In the former case, a DOMException is raised (see [[!DOM4]]).
An exception must be thrown when the
error can be detected at the time that the call is made. In all other cases, an DOMError object(see [[!DOM4]]) must be provided to the failure
callback. The error name in the object provided must be picked from
the RecordingErrorName
enums. If recording has been started and not yet stopped when the error occurs, then after raising the error, the UA must
raise a dataavailable event, containing any data that it has gathered,
and then a stop event. The UA may set platform-specific
limits, such those for the minimum and maximum Blob size that it will support, or the number of
Tracks it will record at once. It must signal a fatal
error if these limits are exceeded.
MediaRecorder
is not in a state
in which the proposed operation is allowed
to be executed.message
attribute.stream
has occurred that makes it impossible to continue recording. An example would be the addition of a Track while recording is occurring.
User agents SHOULD provide as much additional information as possible in the message
attribute.message
attribute.The following additional events fire on
objects:MediaRecorder
Event name | Interface | Fired when... |
---|---|---|
start |
Event |
The UA has started recording data on the MediaStream. |
stop |
Event |
The UA has stopped recording data on the MediaStream. |
dataavailable |
BlobEvent |
The UA generates this even to return data to the application. The 'data' attribute of this event contains a Blob of recorded data. |
pause |
Event |
The UA has paused recording data on the MediaStream. |
resume |
Event |
The UA has resumed recording data on the MediaStream. |
DOMError |
DOMError |
A fatal error has occurred and the UA has stopped recording. More detailed error information is available in the 'message' attribute. |