The working group maintains a list of all bug reports that the editors have not yet tried to address; there may also be open bugs in the previous bug tracker. This draft highlights some of the pending issues that are still to be discussed in the working group. No decision has been taken on the outcome of these issues including whether they are valid.
Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should join the mailing list mentioned below and take part in the discussions.
For this specification to exit the Candidate Recommendation stage, two independent implementations as detailed in the CR Exit Criteria (Public Permissive version 3) document will be required to pass each test in the MSE test suite to be developed by the HTML Media Extensions WG.
If you wish to make comments or file bugs regarding this document in a manner that is tracked by the editors, please submit them via our public bug database.
This specification allows JavaScript to dynamically construct media streams for <audio> and <video>. It defines a MediaSource object that can serve as a source of media data for an HTMLMediaElement. MediaSource objects have one or more SourceBuffer objects. Applications append data segments to the SourceBuffer objects, and can adapt the quality of appended data based on system performance and other factors. Data from the SourceBuffer objects is managed as track buffers for audio, video and text data that is decoded and played. Byte stream specifications used with these extensions are available in the byte stream format registry [[MSE-REGISTRY]].
This specification was designed with the following goals in mind:
This specification defines:
The that provide for the , the , and the or . All these tracks are associated with SourceBuffer objects in the list.
A range used to filter out while appending. The append window represents a single continuous time range with a single start time and end time. Coded frames with within this range are allowed to be appended to the SourceBuffer while coded frames outside this range are filtered out. The append window start and end times are controlled by the and attributes respectively.
The duration of a . For video and text, the duration indicates how long the video frame or text SHOULD be displayed. For audio, the duration represents the sum of all the samples contained within the coded frame. For example, if an audio frame contained 441 samples @44100Hz the frame duration would be 10 milliseconds.
The sum of a and its . It represents the that immediately follows the coded frame.
A group of that are adjacent and have monotonically increasing without any gaps. Discontinuities detected by the and calls trigger the start of a new coded frame group.
The decode timestamp indicates the latest time at which the frame needs to be decoded assuming instantaneous decoding and rendering of this and any dependant frames (this is equal to the of the earliest frame, in , that is dependant on this frame). If frames can be decoded out of , then the decode timestamp MUST be present in or derivable from the byte stream. The user agent MUST run the if this is not the case. If frames cannot be decoded out of and a decode timestamp is not present in the byte stream, then the decode timestamp is equal to the .
A sequence of bytes that contain all of the initialization information required to decode a sequence of . This includes codec initialization data, mappings for multiplexed segments, and timestamp offsets (e.g., edit lists).
The in the byte stream format registry [[MSE-REGISTRY]] contain format specific examples.
A sequence of bytes that contain packetized & timestamped media data for a portion of the . Media segments are always associated with the most recently appended .
The in the byte stream format registry [[MSE-REGISTRY]] contain format specific examples.
A MediaSource object URL is a unique [[!FILE-API]] created by . It is used to attach a MediaSource object to an HTMLMediaElement.
These URLs are the same as a , except that anything in the definition of that feature that refers to and objects is hereby extended to also apply to MediaSource objects.
The origin of the MediaSource object URL is the of this
during the call to .
For example, the of the MediaSource object URL affects the way that the media element is consumed by canvas.
The parent media source of a SourceBuffer object is the MediaSource object that created it.
The presentation start time is the earliest time point in the presentation and specifies the initial playback position and earliest possible position. All presentations created using this specification have a presentation start time of 0.
For the purposes of determining if contains a that includes the current playback position, implementations MAY choose to allow a current playback position at or after and before the first to play the first if that starts within a reasonably short time, like 1 second, after . This allowance accommodates the reality that muxed streams commonly do not begin all tracks precisely at . Implementations MUST report the actual buffered range, regardless of this allowance.
The presentation interval of a is the time interval from its to the plus the . For example, if a coded frame has a presentation timestamp of 10 seconds and a of 100 milliseconds, then the presentation interval would be [10-10.1). Note that the start of the range is inclusive, but the end of the range is exclusive.
The order that are rendered in the presentation. The presentation order is achieved by ordering in monotonically increasing order by their .
A reference to a specific time in the presentation. The presentation timestamp in a indicates when the frame SHOULD be rendered.
A position in a where decoding and continuous playback can begin without relying on any previous data in the segment. For video this tends to be the location of I-frames. In the case of audio, most audio frames can be treated as a random access point. Since video tracks tend to have a more sparse distribution of random access points, the location of these points are usually considered the random access points for multiplexed streams.
The specific that describes the format of the byte stream accepted by a SourceBuffer instance. The , for a SourceBuffer object, is selected based on the type passed to the call that created the object.
A specific set of tracks distributed across one or more SourceBuffer objects owned by a single MediaSource instance.
Implementations MUST support at least 1 MediaSource object with the following configurations:
MediaSource objects MUST support each of the configurations above, but they are only required to support one configuration at a time. Supporting multiple configurations at once or additional configurations is a quality of implementation issue.
A byte stream format specific structure that provides the , codec configuration, and other metadata for a single track. Each track description inside a single has a unique . The user agent MUST run the if the is not unique within the .
A Track ID is a byte stream format specific identifier that marks sections of the byte stream as being part of a specific track. The Track ID in a identifies which sections of a belong to that track.
The MediaSource object represents a source of media data for an HTMLMediaElement. It keeps track of the for this source as well as a list of SourceBuffer objects that can be used to add media data to the presentation. MediaSource objects are created by the web application and then attached to an HTMLMediaElement. The application uses the SourceBuffer objects in to add media data to this source. The HTMLMediaElement fetches this media data from the MediaSource object when it is needed during playback.
Each MediaSource object has a live seekable range variable that stores a . This variable is initialized to an empty object when the MediaSource object is created, is maintained by and , and is used in HTMLMediaElement Extensions to modify behavior.
enum ReadyState { "closed", "open", "ended" };
Enumeration description | |
---|---|
closed | Indicates the source is not currently attached to a media element. |
open | The source has been opened by a media element and is ready for data to be appended to the SourceBuffer objects in . |
ended | The source is still attached to a media element, but has been called. |
enum EndOfStreamError { "network", "decode" };
Enumeration description | |
---|---|
network |
Terminates playback and signals that a network error has occured. JavaScript applications SHOULD use this status code to terminate playback with a network error. For example, if a network error occurs while fetching media data. |
decode |
Terminates playback and signals that a decoding error has occured. JavaScript applications SHOULD use this status code to terminate playback with a decode error. For example, if a parsing error occurs while processing out-of-band media data. |
[Constructor] interface MediaSource : EventTarget { readonly attribute SourceBufferList sourceBuffers; readonly attribute SourceBufferList activeSourceBuffers; readonly attribute ReadyState readyState; attribute unrestricted double duration; attribute EventHandler onsourceopen; attribute EventHandler onsourceended; attribute EventHandler onsourceclose; SourceBuffer addSourceBuffer (DOMString type); void removeSourceBuffer (SourceBuffer sourceBuffer); void endOfStream (optional EndOfStreamError error); void setLiveSeekableRange (double start, double end); void clearLiveSeekableRange (); static boolean isTypeSupported (DOMString type); };
sourceBuffers
of type SourceBufferList, readonly activeSourceBuffers
of type SourceBufferList, readonly Contains the subset of that are providing the selected video track, the enabled audio track(s), and the or text track(s).
SourceBuffer objects in this list MUST appear in the same order as they appear in the attribute; e.g., if only sourceBuffers[0] and sourceBuffers[3] are in , then activeSourceBuffers[0] MUST equal sourceBuffers[0] and activeSourceBuffers[1] MUST equal sourceBuffers[3].
The Changes to selected/enabled track state section describes how this attribute gets updated.
readyState
of type ReadyState, readonly Indicates the current state of the MediaSource object. When the MediaSource is created MUST be set to .
duration
of type unrestricted doubleAllows the web application to set the presentation duration. The duration is initially set to NaN when the MediaSource object is created.
On getting, run the following steps:
On setting, run the following steps:
The will adjust new duration higher if there is any currently buffered coded frame with a higher end time.
onsourceopen
of type EventHandleronsourceended
of type EventHandleronsourceclose
of type EventHandleraddSourceBuffer
Adds a new SourceBuffer to .
For example, a user agent MAY throw a exception if the media element has reached the readyState. This can occur if the user agent's media engine does not support adding more tracks during playback.
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
type | DOMString | ✘ | ✘ |
removeSourceBuffer
Removes a SourceBuffer from .
This should trigger [[HTML51]] logic to the object, at the HTMLMediaElement audioTracks list. If the attribute on the object was true at the beginning of this removal step, then this should also trigger [[HTML51]] logic to at the HTMLMediaElement audioTracks list
This should trigger [[HTML51]] logic to the object, at the SourceBuffer audioTracks list. If the attribute on the object was true at the beginning of this removal step, then this should also trigger [[HTML51]] logic to at the SourceBuffer audioTracks list
This should trigger [[HTML51]] logic to the object, at the HTMLMediaElement videoTracks list. If the attribute on the object was true at the beginning of this removal step, then this should also trigger [[HTML51]] logic to at the HTMLMediaElement videoTracks list
This should trigger [[HTML51]] logic to the object, at the SourceBuffer videoTracks list. If the attribute on the object was true at the beginning of this removal step, then this should also trigger [[HTML51]] logic to at the SourceBuffer videoTracks list
This should trigger [[HTML51]] logic to the object, at the HTMLMediaElement textTracks list. If the attribute on the object was or at the beginning of this removal step, then this should also trigger [[HTML51]] logic to at the HTMLMediaElement textTracks list.
This should trigger [[HTML51]] logic to the object, at the SourceBuffer textTracks list. If the attribute on the object was or at the beginning of this removal step, then this should also trigger [[HTML51]] logic to at the SourceBuffer textTracks list.
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
sourceBuffer | SourceBuffer | ✘ | ✘ |
endOfStream
Signals the end of the stream.
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
error | EndOfStreamError | ✘ | ✔ |
setLiveSeekableRange
Updates the variable used in HTMLMediaElement Extensions to modify behavior.
clearLiveSeekableRange
Updates the variable used in HTMLMediaElement Extensions to modify behavior.
isTypeSupported
, staticCheck to see whether the MediaSource is capable of creating SourceBuffer objects for the specified MIME type.
If true is returned from this method, it only indicates that the MediaSource implementation is capable of creating SourceBuffer objects for the specified MIME type. An call SHOULD still fail if sufficient resources are not available to support the addition of a new SourceBuffer.
This method returning true implies that HTMLMediaElement.canPlayType() will return "maybe" or "probably" since it does not make sense for a MediaSource to support a type the HTMLMediaElement knows it cannot play.
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
type | DOMString | ✘ | ✘ |
boolean
Event name | Interface | Dispatched when... |
---|---|---|
sourceopen | Event |
transitions from to or from to . |
sourceended | Event |
transitions from to . |
sourceclose | Event |
transitions from to or to . |
A MediaSource object can be attached to a media element by assigning a to the media element attribute or the src attribute of a <source> inside a media element. A is created by passing a MediaSource object to .
If the was invoked with a media provider object that is a MediaSource object or a URL record whose object is a MediaSource object, then let mode be local, skip the first step in the (which may otherwise set mode to remote) and add the steps and clarifications below to the section of the .
The 's first step is expected to eventually align with selecting local mode for URL records whose objects are media provider objects. The intent is that if the HTMLMediaElement's src
attribute or selected child <source>
's src
attribute is a blob:
URL matching a when the respective src
attribute was last changed, then that MediaSource object is used as the media provider object and current media resource in the local mode logic in the . This also means that the remote mode logic that includes observance of any preload attribute is skipped when a MediaSource object is attached. Even with that eventual change to [[HTML51]], the execution of the following steps at the beginning of the local mode logic is still required when the current media resource is a MediaSource object.
Relative to the action which triggered the media element's resource selection algorithm, these steps are asynchronous. The resource fetch algorithm is run after the task that invoked the resource selection algorithm is allowed to continue and a stable state is reached. Implementations may delay the steps in the "Otherwise" clause, below, until the MediaSource object is ready for use.
An attached MediaSource does not use the remote mode steps in the , so the media element will not fire "suspend" events. Though future versions of this specification will likely remove "progress" and "stalled" events from a media element with an attached MediaSource, user agents conforming to this version of the specification may still fire these two events as these [[HTML51]] references changed after implementations of this specification stabilized.
The following steps are run in any case where the media element is going to transition to NETWORK_EMPTY and emptied at the media element. These steps SHOULD be run right before the transition.
Going forward, this algorithm is intended to be externally called and run in any case where the attached MediaSource, if any, must be detached from the media element. It MAY be called on HTMLMediaElement [[HTML51]] operations like load() and resource fetch algorithm failures in addition to, or in place of, when the media element transitions to NETWORK_EMPTY. Resource fetch algorithm failures are those which abort either the resource fetch algorithm or the resource selection algorithm, with the exception that the "Final step" [[HTML51]] is not considered a failure that triggers detachment.
Run the following steps as part of the "Wait until the user agent has established whether or not the media data for the new playback position is available, and, if it is, until it has decoded enough data to play back that position" step of the :
The media element looks for containing the new playback position in each SourceBuffer object in . Any position within a in the current value of the attribute has all necessary media segments buffered for that position.
Per [[HTML51]] logic, changes may trigger events on the HTMLMediaElement.
The web application can use and to determine what the media element needs to resume playback.
If the attribute is and the new playback position is within a currently in , then the seek operation must continue to completion here even if one or more currently selected or enabled track buffers has a less than new playback position. This condition should only occur due to logic in when is .
The following steps are periodically run during playback to make sure that all of the SourceBuffer objects in have . Changes to also cause these steps to run because they affect the conditions that trigger state transitions.
Having enough data to ensure uninterrupted playback is an implementation specific condition where the user agent determines that it currently has enough data to play the presentation without stalling for a meaningful period of time. This condition is constantly evaluated to determine when to transition the media element into and out of the ready state. These transitions indicate when the user agent believes it has enough data buffered or it needs more data respectively.
An implementation MAY choose to use bytes buffered, time buffered, the append rate, or any other metric it sees fit to determine when it has enough data. The metrics used MAY change during playback so web applications SHOULD only rely on the value of to determine whether more data is needed or not.
When the media element needs more data, the user agent SHOULD transition it from to early enough for a web application to be able to respond without causing an interruption in playback. For example, transitioning when the current playback position is 500ms before the end of the buffered data gives the application roughly 500ms to append more data before playback stalls.
During playback needs to be updated if the selected video track, the enabled audio track(s), or a text track mode changes. When one or more of these changes occur the following steps need to be followed.
Follow these steps when needs to change to a new duration.
Duration reductions that would truncate currently buffered media are disallowed. When truncation is necessary, use to reduce the buffered range before updating .
This algorithm gets called when the application signals the end of stream via an call or an algorithm needs to signal a decode error. This algorithm takes an error parameter that indicates whether an error will be signalled.
This allows the duration to properly reflect the end of the appended media segments. For example, if the duration was explicitly set to 10 seconds and only media segments for 0 to 5 seconds were appended before endOfStream() was called, then the duration will get updated to 5 seconds.
enum AppendMode { "segments", "sequence" };
interface SourceBuffer : EventTarget { attribute AppendMode mode; readonly attribute boolean updating; readonly attribute TimeRanges buffered; attribute double timestampOffset; readonly attribute AudioTrackList audioTracks; readonly attribute VideoTrackList videoTracks; readonly attribute TextTrackList textTracks; attribute double appendWindowStart; attribute unrestricted double appendWindowEnd; attribute EventHandler onupdatestart; attribute EventHandler onupdate; attribute EventHandler onupdateend; attribute EventHandler onerror; attribute EventHandler onabort; void appendBuffer (BufferSource data); void abort (); void remove (double start, unrestricted double end); };
mode
of type AppendModeControls how a sequence of are handled. This attribute is initially set by after the object is created.
On getting, Return the initial value or the last value that was successfully set.
On setting, run the following steps:
If the attribute of the is in the state then run the following steps:
updating
of type boolean, readonly Indicates whether the asynchronous continuation of an or operation is still being processed. This attribute is initially set to false when the object is created.
buffered
of type TimeRanges, readonly Indicates what are buffered in the SourceBuffer. This attribute is initially set to an empty object when the object is created.
When the attribute is read the following steps MUST occur:
Text track-buffers are included in the calculation of highest end time, above, but excluded from the buffered range calculation here. They are not necessarily continuous, nor should any discontinuity within them trigger playback stall when the other media tracks are continuous over the same time range.
timestampOffset
of type doubleControls the offset applied to timestamps inside subsequent that are appended to this SourceBuffer. The is initially set to 0 which indicates that no offset is being applied.
On getting, Return the initial value or the last value that was successfully set.
On setting, run the following steps:
If the attribute of the is in the state then run the following steps:
audioTracks
of type AudioTrackList, readonly videoTracks
of type VideoTrackList, readonly textTracks
of type TextTrackList, readonly appendWindowStart
of type doubleThe for the start of the . This attribute is initially set to the .
On getting, Return the initial value or the last value that was successfully set.
On setting, run the following steps:
appendWindowEnd
of type unrestricted doubleThe for the end of the . This attribute is initially set to positive Infinity.
On getting, Return the initial value or the last value that was successfully set.
On setting, run the following steps:
onupdatestart
of type EventHandleronupdate
of type EventHandleronupdateend
of type EventHandleronerror
of type EventHandleronabort
of type EventHandlerappendBuffer
Appends the segment data in an BufferSource[[!WEBIDL]] to the source buffer.
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
data | BufferSource | ✘ | ✘ |
abort
Aborts the current segment and resets the segment parser.
remove
Removes media for a specific time range.
If the attribute of the is in the state then run the following steps:
A track buffer stores the and for an individual track. The track buffer is updated as and are appended to the SourceBuffer.
Each has a last decode timestamp variable that stores the decode timestamp of the last appended in the current . The variable is initially unset to indicate that no have been appended yet.
Each has a last frame duration variable that stores the of the last appended in the current . The variable is initially unset to indicate that no have been appended yet.
Each has a highest end timestamp variable that stores the highest across all in the current that were appended to this track buffer. The variable is initially unset to indicate that no have been appended yet.
Each has a need random access point flag variable that keeps track of whether the track buffer is waiting for a . The variable is initially set to true to indicate that is needed before anything can be added to the .
Each has a track buffer ranges variable that represents the presentation time ranges occupied by the currently stored in the track buffer.
For track buffer ranges, these presentation time ranges are based on presentation timestamps, frame durations, and potentially coded frame group start times for coded frame groups across track buffers in a muxed SourceBuffer.
For specification purposes, this information is treated as if it were stored in a . Intersected are used to report , and MUST therefore support uninterrupted playback within each range of .
These coded frame group start times differ slightly from those mentioned in the in that they are the earliest across all track buffers following a discontinuity. Discontinuities can occur within the or result from the , regardless of . The threshold for determining disjointness of is implementation-specific. For example, to reduce unexpected playback stalls, implementations MAY approximate the 's discontinuity detection logic by coalescing adjacent ranges separated by a gap smaller than 2 times the maximum frame duration buffered so far in this . Implementations MAY also use coded frame group start times as range start times across track buffers in a muxed SourceBuffer to further reduce unexpected playback stalls.
Event name | Interface | Dispatched when... |
---|---|---|
updatestart | Event |
transitions from false to true. |
update | Event |
The append or remove has successfully completed. transitions from true to false. |
updateend | Event |
The append or remove has ended. |
error | Event |
An error occurred during the append. transitions from true to false. |
abort | Event |
The append or remove was aborted by an call. transitions from true to false. |
All SourceBuffer objects have an internal append state variable that keeps track of the high-level segment parsing state. It is initially set to and can transition to the following states as data is appended.
Append state name | Description |
---|---|
WAITING_FOR_SEGMENT | Waiting for the start of an or to be appended. |
PARSING_INIT_SEGMENT | Currently parsing an . |
PARSING_MEDIA_SEGMENT | Currently parsing a . |
The input buffer is a byte buffer that is used to hold unparsed bytes across calls. The buffer is empty when the SourceBuffer object is created.
The buffer full flag keeps track of whether is allowed to accept more bytes. It is set to false when the SourceBuffer object is created and gets updated as data is appended and removed.
The group start timestamp variable keeps track of the starting timestamp for a new in the mode. It is unset when the SourceBuffer object is created and gets updated when the attribute equals and the attribute is set, or the runs.
The group end timestamp variable stores the highest across all in the current . It is set to 0 when the SourceBuffer object is created and gets updated by the .
The stores the highest across all in a SourceBuffer. Therefore, care should be taken in setting the attribute when appending multiplexed segments in which the timestamps are not aligned across tracks.
The generate timestamps flag is a boolean variable that keeps track of whether timestamps need to be generated for the passed to the . This flag is set by when the SourceBuffer object is created.
When the segment parser loop algorithm is invoked, run the following steps:
If the equals , then run the following steps:
The frequency at which the coded frame processing algorithm is run is implementation-specific. The coded frame processing algorithm MAY be called when the input buffer contains the complete media segment or it MAY be called multiple times as complete coded frames are added to the input buffer.
When the parser state needs to be reset, run the following steps:
This algorithm is called when an error occurs during an append. This algorithm takes a decode error parameter that indicates whether should be called.
When an append operation begins, the follow steps are run to validate and prepare the SourceBuffer.
If the attribute of the is in the state then run the following steps:
If the equals true, then throw a exception and abort these step.
This is the signal that the implementation was unable to evict enough data to accommodate the append or the append is too big. The web application SHOULD use to explicitly free up space and/or reduce the size of the append.
When is called, the following steps are run to process the appended data.
Follow these steps when a caller needs to initiate a JavaScript visible range removal operation that blocks other SourceBuffer updates:
The following steps are run when the successfully parses a complete :
Each SourceBuffer object has an internal first initialization segment received flag that tracks whether the first has been appended and received by this algorithm. This flag is set to false when the SourceBuffer is created and updated by the algorithm below.
If the is false, then run the following steps:
User agents MAY consider codecs, that would otherwise be supported, as "not supported" here if the codecs were not
specified in the type parameter passed to .
For example, MediaSource.isTypeSupported('video/webm;codecs="vp8,vorbis"') may return true, but if
was called with 'video/webm;codecs="vp8"' and a Vorbis track appears in the
, then the user agent MAY use this step to trigger a decode error.
For each audio track in the , run following steps:
This should trigger [[HTML51]] logic to new audio track, at the object referenced by the attribute on this SourceBuffer object.
This should trigger [[HTML51]] logic to new audio track, at the object referenced by the attribute on the HTMLMediaElement.
For each video track in the , run following steps:
This should trigger [[HTML51]] logic to new video track, at the object referenced by the attribute on this SourceBuffer object.
This should trigger [[HTML51]] logic to new video track, at the object referenced by the attribute on the HTMLMediaElement.
For each text track in the , run following steps:
This should trigger [[HTML51]] logic to new text track, at the object referenced by the attribute on this SourceBuffer object.
This should trigger [[HTML51]] logic to new text track, at the object referenced by the attribute on the HTMLMediaElement.
Per [[HTML51]] logic, changes may trigger events on the HTMLMediaElement.
When complete have been parsed by the then the following steps are run:
For each in the run the following steps:
Special processing may be needed to determine the presentation and decode timestamps for timed text frames since this information may not be explicitly present in the underlying format or may be dependent on the order of the frames. Some metadata text tracks, like MPEG2-TS PSI data, may only have implied timestamps. Format specific rules for these situations SHOULD be in the or in separate extension specifications.
Implementations don't have to internally store timestamps in a double precision floating point representation. This representation is used here because it is the represention for timestamps in the HTML spec. The intention here is to make the behavior clear without adding unnecessary complexity to the algorithm to deal with the fact that adding a timestampOffset may cause a timestamp rollover in the underlying timestamp representation used by the byte stream format. Implementations can use any internal timestamp representation they wish, but the addition of timestampOffset SHOULD behave in a similar manner to what would happen if a double precision floating point representation was used.
Some implementations MAY choose to collect some of these coded frames with presentation timestamp less than and use them to generate a splice at the first coded frame that has a greater than or equal to even if that frame is not a . Supporting this requires multiple decoders or faster than real-time decoding so for now this behavior will not be a normative requirement.
Some implementations MAY choose to collect coded frames with presentation timestamp less than and frame end timestamp greater than and use them to generate a splice across the portion of the collected coded frames within the append window at time of collection, and the beginning portion of later processed frames which only partially overlap the end of the collected coded frames. Supporting this requires multiple decoders or faster than real-time decoding so for now this behavior will not be a normative requirement. In conjunction with collecting coded frames that span , implementations MAY thus support gapless audio splicing.
This is to compensate for minor errors in frame timestamp computations that can appear when converting back and forth between double precision floating point numbers and rationals. This tolerance allows a frame to replace an existing one as long as it is within 1 microsecond of the existing frame's start time. Frames that come slightly before an existing frame are handled by the removal step below.
Removing all until the next is a conservative estimate of the decoding dependencies since it assumes all frames between the removed frames and the next random access point depended on the frames that were removed.
The greater than check is needed because bidirectional prediction between coded frames can cause presentation timestamp to not be monotonically increasing even though the decode timestamps are monotonically increasing.
If the attribute is and the new cause to have a for the current playback position, then set the attribute to .
Per [[HTML51]] logic, changes may trigger events on the HTMLMediaElement.
If the attribute is and the new cause to have a that includes the current playback position and some time beyond the current playback position, then set the attribute to .
Per [[HTML51]] logic, changes may trigger events on the HTMLMediaElement.
If the attribute is and the new cause to have a that includes the current playback position and , then set the attribute to .
Per [[HTML51]] logic, changes may trigger events on the HTMLMediaElement.
Follow these steps when for a specific time range need to be removed from the SourceBuffer:
For each in this source buffer, run the following steps:
If this has a timestamp that is greater than or equal to end, then update remove end timestamp to that random access point timestamp.
Random access point timestamps can be different across tracks because the dependencies between within a track are usually different than the dependencies in another track.
For each removed frame, if the frame has a equal to the for the frame's track, run the following steps:
Removing all until the next is a conservative estimate of the decoding dependencies since it assumes all frames between the removed frames and the next random access point depended on the frames that were removed.
If this object is in , the is greater than or equal to start and less than the remove end timestamp, and is greater than , then set the attribute to and stall playback.
Per [[HTML51]] logic, changes may trigger events on the HTMLMediaElement.
This transition occurs because media data for the current position has been removed. Playback cannot progress until media for the is appended or the selected/enabled tracks change.
This algorithm is run to free up space in this source buffer when new data is appended.
Implementations MAY use different methods for selecting removal ranges so web applications SHOULD NOT depend on a specific behavior. The web application can use the attribute to observe whether portions of the buffered data have been evicted.
Follow these steps when the needs to generate a splice frame for two overlapping audio :
floor(x * sample_rate + 0.5) / sample_rate
).
For example, given the following values:
presentation timestamp and decode timestamp are updated to 10.0125 since 10.01255 is closer to 10 + 100/8000 (10.0125) than 10 + 101/8000 (10.012625)
Some implementations MAY apply fades to/from silence to coded frames on either side of the inserted silence to make the transition less jarring.
This is intended to allow new coded frame to be added to the track buffer as if overlapped frame had not been in the track buffer to begin with.
If the new coded frame is less than 5 milliseconds in duration, then coded frames that are appended after the new coded frame will be needed to properly render the splice.
The following steps are run when a spliced frame, generated by the , needs to be rendered by the media element:
Here is a graphical representation of this algorithm.
Follow these steps when the needs to generate a splice frame for two overlapping timed text :
This is intended to allow new coded frame to be added to the track buffer as if it hadn't overlapped any frames in track buffer to begin with.
SourceBufferList is a simple container object for SourceBuffer objects. It provides read-only array access and fires events when the list is modified.
interface SourceBufferList : EventTarget { readonly attribute unsigned long length; attribute EventHandler onaddsourcebuffer; attribute EventHandler onremovesourcebuffer; getter SourceBuffer (unsigned long index); };
length
of type unsigned long, readonly Indicates the number of SourceBuffer objects in the list.
onaddsourcebuffer
of type EventHandleronremovesourcebuffer
of type EventHandlergetter
Allows the SourceBuffer objects in the list to be accessed with an array operator (i.e., []).
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
index | unsigned long |
✘ | ✘ |
SourceBuffer
Event name | Interface | Dispatched when... |
---|---|---|
addsourcebuffer | Event |
When a SourceBuffer is added to the list. |
removesourcebuffer | Event |
When a SourceBuffer is removed from the list. |
This section specifies extensions to the [[!FILE-API]] object definition.
[Exposed=Window,DedicatedWorker,SharedWorker] partial interface URL { static DOMString createObjectURL (MediaSource mediaSource); };
createObjectURL
, staticCreates URLs for MediaSource objects.
This algorithm is intended to mirror the behavior of the [[!FILE-API]] method, which does not auto-revoke the created URL. Web authors are encouraged to use [[!FILE-API]] for any that is no longer needed for attachment to a media element.
Parameter | Type | Nullable | Optional | Description |
---|---|---|---|---|
mediaSource | MediaSource | ✘ | ✘ |
DOMString
This section specifies what existing attributes on the MUST return when a MediaSource is attached to the element.
The attribute returns a new static created based on the following steps:
The attribute returns a static based on the following steps.
This section specifies extensions to the HTML definition.
partial interface AudioTrack { readonly attribute SourceBuffer? sourceBuffer; };
sourceBuffer
of type SourceBuffer, readonly , nullableReturns the SourceBuffer that created this track. Returns null if this track was not created by a SourceBuffer or the SourceBuffer has been removed from the attribute of its .
This section specifies extensions to the HTML definition.
partial interface VideoTrack { readonly attribute SourceBuffer? sourceBuffer; };
sourceBuffer
of type SourceBuffer, readonly , nullableReturns the SourceBuffer that created this track. Returns null if this track was not created by a SourceBuffer or the SourceBuffer has been removed from the attribute of its .
This section specifies extensions to the HTML definition.
partial interface TextTrack { readonly attribute SourceBuffer? sourceBuffer; };
sourceBuffer
of type SourceBuffer, readonly , nullableReturns the SourceBuffer that created this track. Returns null if this track was not created by a SourceBuffer or the SourceBuffer has been removed from the attribute of its .
The bytes provided through for a SourceBuffer form a logical byte stream. The format and semantics of these byte streams are defined in byte stream format specifications. The byte stream format registry [[MSE-REGISTRY]] provides mappings between a MIME type that may be passed to or and the byte stream format expected by a SourceBuffer created with that MIME type. Implementations are encouraged to register mappings for byte stream formats they support to facilitate interoperability. The byte stream format registry [[MSE-REGISTRY]] is the authoritative source for these mappings. If an implementation claims to support a MIME type listed in the registry, its SourceBuffer implementation MUST conform to the listed in the registry entry.
The byte stream format specifications in the registry are not intended to define new storage formats. They simply outline the subset of existing storage format structures that implementations of this specification will accept.
Byte stream format parsing and validation is implemented in the algorithm.
This section provides general requirements for all byte stream format specifications:
If the byte stream format covers a format similar to one covered in the in-band tracks spec [[INBANDTRACKS]], then it SHOULD try to use the same attribute mappings so that Media Source Extensions playback and non-Media Source Extensions playback provide the same track information.
The number and type of tracks are not consistent.
For example, if the first has 2 audio tracks and 1 video track, then all that follow it in the byte stream MUST describe 2 audio tracks and 1 video track.
For example, a byte stream that starts with an that specifies a single AAC track and later contains an that specifies a single AMR-WB track is not allowed. Support for multiple codecs is handled with multiple SourceBuffer objects.
Video frame size changes. The user agent MUST support seamless playback.
This will cause the <video> display region to change size if the web application does not use CSS or HTML attributes (width/height) to constrain the element size.
Audio channel count changes. The user agent MAY support this seamlessly and could trigger downmixing.
This is a quality of implementation issue because changing the channel count may require reinitializing the audio device, resamplers, and channel mixers which tends to be audible.
This is intended to simplify switching between audio streams where the frame boundaries don't always line up across encodings (e.g., Vorbis).
For example, if I1 is associated with M1, M2, M3 then the above MUST hold for all the combinations I1+M1, I1+M2, I1+M1+M2, I1+M2+M3, etc.
Byte stream specifications MUST at a minimum define constraints which ensure that the above requirements hold. Additional constraints MAY be defined, for example to simplify implementation.
Example use of the Media Source Extensions
<script> function onSourceOpen(videoTag, e) { var mediaSource = e.target; if (mediaSource.sourceBuffers.length > 0) return; var sourceBuffer = mediaSource.addSourceBuffer('video/webm; codecs="vorbis,vp8"'); videoTag.addEventListener('seeking', onSeeking.bind(videoTag, mediaSource)); videoTag.addEventListener('progress', onProgress.bind(videoTag, mediaSource)); var initSegment = GetInitializationSegment(); if (initSegment == null) { // Error fetching the initialization segment. Signal end of stream with an error. mediaSource.endOfStream("network"); return; } // Append the initialization segment. var firstAppendHandler = function(e) { var sourceBuffer = e.target; sourceBuffer.removeEventListener('updateend', firstAppendHandler); // Append some initial media data. appendNextMediaSegment(mediaSource); }; sourceBuffer.addEventListener('updateend', firstAppendHandler); sourceBuffer.appendBuffer(initSegment); } function appendNextMediaSegment(mediaSource) { if (mediaSource.readyState == "closed") return; // If we have run out of stream data, then signal end of stream. if (!HaveMoreMediaSegments()) { mediaSource.endOfStream(); return; } // Make sure the previous append is not still pending. if (mediaSource.sourceBuffers[0].updating) return; var mediaSegment = GetNextMediaSegment(); if (!mediaSegment) { // Error fetching the next media segment. mediaSource.endOfStream("network"); return; } // NOTE: If mediaSource.readyState == “ended”, this appendBuffer() call will // cause mediaSource.readyState to transition to "open". The web application // should be prepared to handle multiple “sourceopen” events. mediaSource.sourceBuffers[0].appendBuffer(mediaSegment); } function onSeeking(mediaSource, e) { var video = e.target; if (mediaSource.readyState == "open") { // Abort current segment append. mediaSource.sourceBuffers[0].abort(); } // Notify the media segment loading code to start fetching data at the // new playback position. SeekToMediaSegmentAt(video.currentTime); // Append a media segment from the new playback position. appendNextMediaSegment(mediaSource); } function onProgress(mediaSource, e) { appendNextMediaSegment(mediaSource); } </script> <video id="v" autoplay> </video> <script> var video = document.getElementById('v'); var mediaSource = new MediaSource(); mediaSource.addEventListener('sourceopen', onSourceOpen.bind(this, video)); video.src = window.URL.createObjectURL(mediaSource); </script>
VideoPlaybackQuality
object and the extension method getVideoPlaybackQuality()
described in those previous revisions.