2.4.1 Attaching to a media element

A MediaSource object can be attached to a media element by assigning a MediaSource object URL to the media element src attribute or the src attribute of a <source> inside a media element. A MediaSource object URL is created by passing a MediaSource object to createObjectURL().

If the resource fetch algorithm absolute URL matches the MediaSource object URL, run the following steps right before the "Perform a potentially CORS-enabled fetch" step in the resource fetch algorithm.

If readyState is NOT set to "closed"

Run the "If the media data cannot be fetched at all, due to network errors, causing the user agent to give up trying to fetch the resource" steps of the resource fetch algorithm.

Otherwise

1. Set the readyState attribute to "open".
2. Queue a task to fire a simple event named sourceopen at the MediaSource.
3. Continue the resource fetch algorithm by running the "Perform a potentially CORS-enabled fetch" step. Text in the resource fetch algorithm that refers to "the download" or "bytes received" refer to data passed in via appendBuffer() and appendStream(). References to HTTP in the resource fetch algorithm do not apply because the HTMLMediaElement does not fetch media data via HTTP when a MediaSource is attached.

2.4.2 Detaching from a media element

The following steps are run in any case where the media element is going to transition to NETWORK_EMPTY and queue a task to fire a simple event named emptied at the media element. These steps must be run right before the transition.

1. Set the readyState attribute to "closed".
2. Set the duration attribute to NaN.
3. Remove all the SourceBuffer objects from activeSourceBuffers.
4. Queue a task to fire a simple event named removesourcebuffer at activeSourceBuffers.
5. Remove all the SourceBuffer objects from sourceBuffers.
6. Queue a task to fire a simple event named removesourcebuffer at sourceBuffers.
7. Queue a task to fire a simple event named sourceclose at the MediaSource.

2.4.3 Seeking

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 seek algorithm:

1. The media element looks for media segments containing the new playback position in each SourceBuffer object in activeSourceBuffers.

   If one or more of the objects in activeSourceBuffers is missing media segments for the new playback position

   1. Set the HTMLMediaElement.readyState attribute to HAVE_METADATA.
   2. The media element waits until an appendBuffer() or an appendStream() call causes the coded frame processing algorithm to set the HTMLMediaElement.readyState attribute to a value greater than HAVE_METADATA.
      Note

      The web application can use buffered to determine what the media element needs to resume playback.

   Otherwise

   Continue

2. The media element resets all decoders and initializes each one with data from the appropriate initialization segment.
3. The media element feeds coded frames from the active track buffers into the decoders starting with the closest random access point before the new playback position.
4. Resume the seek algorithm at the "Await a stable state" step.

2.4.4 SourceBuffer Monitoring

The following steps are periodically run during playback to make sure that all of the SourceBuffer objects in activeSourceBuffers have enough data to ensure uninterrupted playback. Appending new segments and changes to activeSourceBuffers 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 HAVE_ENOUGH_DATA ready state. These transitions indicate when the user agent believes it has enough data buffered or it needs more data respectively.

If HTMLMediaElement.buffered does not contain a TimeRange for the current playback position:

1. Set the HTMLMediaElement.readyState attribute to HAVE_METADATA.
2. If this is the first transition to HAVE_METADATA, then queue a task to fire a simple event named loadedmetadata at the media element.
3. Abort these steps.

If HTMLMediaElement.buffered contains a TimeRange that includes the current playback position and enough data to ensure uninterrupted playback:

1. Set the HTMLMediaElement.readyState attribute to HAVE_ENOUGH_DATA.
2. Queue a task to fire a simple event named canplaythrough at the media element.
3. Playback may resume at this point if it was previously suspended by a transition to HAVE_CURRENT_DATA.
4. Abort these steps.

If HTMLMediaElement.buffered contains a TimeRange that includes the current playback position and some time beyond the current playback position, then run the following steps:

1. Set the HTMLMediaElement.readyState attribute to HAVE_FUTURE_DATA.
2. If the previous value of HTMLMediaElement.readyState was less than HAVE_FUTURE_DATA, then queue a task to fire a simple event named canplay at the media element.
3. Playback may resume at this point if it was previously suspended by a transition to HAVE_CURRENT_DATA.
4. Abort these steps.

If HTMLMediaElement.buffered contains a TimeRange that ends at the current playback position and does not have a range covering the time immediately after the current position:

1. Set the HTMLMediaElement.readyState attribute to HAVE_CURRENT_DATA.
2. If this is the first transition to HAVE_CURRENT_DATA, then queue a task to fire a simple event named loadeddata at the media element.
3. Playback is suspended at this point since the media element doesn't have enough data to advance the media timeline.
4. Abort these steps.

2.4.5 Changes to selected/enabled track state

During playback activeSourceBuffers 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.

If the selected video track changes, then run the following steps:

1. If the SourceBuffer associated with the previously selected video track is not associated with any other enabled tracks, run the following steps:
   1. Remove the SourceBuffer from activeSourceBuffers.
   2. Queue a task to fire a simple event named removesourcebuffer at activeSourceBuffers
2. If the SourceBuffer associated with the newly selected video track is not already in activeSourceBuffers, run the following steps:
   1. Add the SourceBuffer to activeSourceBuffers.
   2. Queue a task to fire a simple event named addsourcebuffer at activeSourceBuffers

If an audio track becomes disabled and the SourceBuffer associated with this track is not associated with any other enabled or selected track, then run the following steps:

1. Remove the SourceBuffer associated with the audio track from activeSourceBuffers
2. Queue a task to fire a simple event named removesourcebuffer at activeSourceBuffers

If an audio track becomes enabled and the SourceBuffer associated with this track is not already in activeSourceBuffers, then run the following steps:

1. Add the SourceBuffer associated with the audio track to activeSourceBuffers
2. Queue a task to fire a simple event named addsourcebuffer at activeSourceBuffers

If a text track mode becomes "disabled" and the SourceBuffer associated with this track is not associated with any other enabled or selected track, then run the following steps:

1. Remove the SourceBuffer associated with the text track from activeSourceBuffers
2. Queue a task to fire a simple event named removesourcebuffer at activeSourceBuffers

If a text track mode becomes "showing" or "hidden" and the SourceBuffer associated with this track is not already in activeSourceBuffers, then run the following steps:

1. Add the SourceBuffer associated with the text track to activeSourceBuffers
2. Queue a task to fire a simple event named addsourcebuffer at activeSourceBuffers

2.4.6 Duration change

Follow these steps when duration needs to change to a new duration.

1. If the current value of duration is equal to new duration, then return.
2. Set old duration to the current value of duration.
3. Update duration to new duration.
4. If the new duration is less than old duration, then run the range removal algorithm with new duration and old duration as the start and end of the removal range.
Note

This preserves audio frames and text cues that start before and end after the duration.

5. If a user agent is unable to partially render audio frames or text cues that start before and end after the duration, then run the following steps:
   1. Update new duration to the highest end time reported by the buffered attribute across all SourceBuffer objects in sourceBuffers.
   2. Update duration to new duration.
6. Update the media controller duration to new duration and run the HTMLMediaElement duration change algorithm.

2.4.7 End of stream algorithm

This algorithm gets called when the application signals the end of stream via an endOfStream() call or an algorithm needs to signal a decode error. This algorithm takes an error parameter that indicates whether an error will be signalled.

1. Change the readyState attribute value to "ended".
2. Queue a task to fire a simple event named sourceended at the MediaSource.

3. If error is not set

   1. Run the duration change algorithm with new duration set to the highest end time reported by the buffered attribute across all SourceBuffer objects in sourceBuffers.
      
      Note

      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.

   2. Notify the media element that it now has all of the media data.

   If error is set to "network"

   If the HTMLMediaElement.readyState attribute equals HAVE_NOTHING

   Run the "If the media data cannot be fetched at all, due to network errors, causing the user agent to give up trying to fetch the resource" steps of the resource fetch algorithm.

   If the HTMLMediaElement.readyState attribute is greater than HAVE_NOTHING

   Run the "If the connection is interrupted after some media data has been received, causing the user agent to give up trying to fetch the resource" steps of the resource fetch algorithm.

   If error is set to "decode"

   1. If updating equals true, then run the append error algorithm.

   2. If the HTMLMediaElement.readyState attribute equals HAVE_NOTHING

      Run the "If the media data can be fetched but is found by inspection to be in an unsupported format, or can otherwise not be rendered at all" steps of the resource fetch algorithm.

      If the HTMLMediaElement.readyState attribute is greater than HAVE_NOTHING

      Run the media data is corrupted steps of the resource fetch algorithm.

3.5.1 Segment Parser Loop

All SourceBuffer objects have an internal append state variable that keeps track of the high-level segment parsing state. It is initially set to WAITING_FOR_SEGMENT and can transition to the following states as data is appended.

The input buffer is a byte buffer that is used to hold unparsed bytes across appendBuffer() and appendStream() calls. The buffer is empty when the SourceBuffer object is created.

The buffer full flag keeps track of whether appendBuffer() or appendStream() 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 coded frame group in the "sequence" mode. It is unset when the SourceBuffer object is created and gets updated when the mode attribute equals "sequence" and the timestampOffset attribute is set, or the coded frame processing algorithm runs.

The group end timestamp variable stores the highest coded frame end timestamp across all coded frames in the current coded frame group. It is set to 0 when the SourceBuffer object is created and gets updated by the coded frame processing algorithm.

The generate timestamps flag is a boolean variable that keeps track of whether timestamps need to be generated for the coded frames passed to the coded frame processing algorithm. This flag is set by addSourceBuffer() when the SourceBuffer object is created.

When the segment parser loop algorithm is invoked, run the following steps:

1. Loop Top: If the input buffer is empty, then jump to the need more data step below.
2. If the input buffer contains bytes that violate the SourceBuffer byte stream format specification, then run the end of stream algorithm with the error parameter set to "decode" and abort this algorithm.
3. Remove any bytes that the byte stream format specifications say must be ignored from the start of the input buffer.

4. If the append state equals WAITING_FOR_SEGMENT, then run the following steps:

   1. If the beginning of the input buffer indicates the start of an initialization segment, set the append state to PARSING_INIT_SEGMENT.
   2. If the beginning of the input buffer indicates the start of a media segment, set append state to PARSING_MEDIA_SEGMENT.
   3. Jump to the loop top step above.

5. If the append state equals PARSING_INIT_SEGMENT, then run the following steps:

   1. If the input buffer does not contain a complete initialization segment yet, then jump to the need more data step below.
   2. Run the initialization segment received algorithm.
   3. Remove the initialization segment bytes from the beginning of the input buffer.
   4. Set append state to WAITING_FOR_SEGMENT.
   5. Jump to the loop top step above.

6. If the append state equals PARSING_MEDIA_SEGMENT, then run the following steps:

   1. If the first initialization segment received flag is false, then run the end of stream algorithm with the error parameter set to "decode" and abort this algorithm.
   2. If the input buffer does not contain a complete media segment header yet, then jump to the need more data step below.
   3. If the input buffer contains one or more complete coded frames, then run the coded frame processing algorithm.
      Note

      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.

   4. If this SourceBuffer is full and cannot accept more media data, then set the buffer full flag to true.
   5. If the input buffer does not contain a complete media segment, then jump to the need more data step below.

   6. Remove the media segment bytes from the beginning of the input buffer.
   7. Set append state to WAITING_FOR_SEGMENT.
   8. Jump to the loop top step above.
7. Need more data: Return control to the calling algorithm.

3.5.2 Reset Parser State

When the parser state needs to be reset, run the following steps:

1. If the append state equals PARSING_MEDIA_SEGMENT and the input buffer contains some complete coded frames, then run the coded frame processing algorithm until all of these complete coded frames have been processed.
2. Unset the last decode timestamp on all track buffers.
3. Unset the last frame duration on all track buffers.
4. Unset the highest presentation timestamp on all track buffers.
5. Set the need random access point flag on all track buffers to true.
6. Remove all bytes from the input buffer.
7. Set append state to WAITING_FOR_SEGMENT.

3.5.3 Append Error Algorithm

When an error occurs during an append, run the following steps:

1. Run the reset parser state algorithm.
2. Set the updating attribute to false.
3. Queue a task to fire a simple event named error at this SourceBuffer object.
4. Queue a task to fire a simple event named updateend at this SourceBuffer object.

3.5.4 Prepare Append Algorithm

When an append operation begins, the follow steps are run to validate and prepare the SourceBuffer.

1. If the SourceBuffer has been removed from the sourceBuffers attribute of the parent media source then throw an InvalidStateError exception and abort these steps.
2. If the updating attribute equals true, then throw an InvalidStateError exception and abort these steps.

3. If the readyState attribute of the parent media source is in the "ended" state then run the following steps:

   1. Set the readyState attribute of the parent media source to "open"
   2. Queue a task to fire a simple event named sourceopen at the parent media source .
4. Run the coded frame eviction algorithm.

5. If the buffer full flag equals true, then throw a QuotaExceededError exception and abort these step.

   Note

   This is the signal that the implementation was unable to evict enough data to accomodate the append or the append is too big. The web application should use remove() to explicitly free up space and/or reduce the size of the append.

3.5.5 Buffer Append Algorithm

When appendBuffer() is called, the following steps are run to process the appended data.

1. Run the segment parser loop algorithm.
2. If the segment parser loop algorithm in the previous step was aborted, then abort this algorithm.
3. Set the updating attribute to false.
4. Queue a task to fire a simple event named update at this SourceBuffer object.
5. Queue a task to fire a simple event named updateend at this SourceBuffer object.

3.5.6 Stream Append Loop

When a Stream[STREAMS-API] is passed to appendStream(), the following steps are run to transfer data from the Stream to the SourceBuffer. This algorithm is initialized with the stream and maxSize parameters from the appendStream() call.

1. If maxSize is set, then let bytesLeft equal maxSize.
2. Loop Top: If maxSize is set and bytesLeft equals 0, then jump to the loop done step below.
3. If stream has been closed, then jump to the loop done step below.
4. Read data from stream into data:

   If maxSize is set:

   1. Read up to bytesLeft bytes from stream into data.
   2. Subtract the number of bytes in data from bytesLeft.

   Otherwise:

   Read all available bytes in stream into data.

5. If an error occured while reading from stream, then run the append error algorithm and abort this algorithm.
6. Run the coded frame eviction algorithm.

7. If the buffer full flag equals true, then run the append error algorithm and abort this algorithm.

   Note

   The web application should use remove() to free up space in the SourceBuffer.

8. Add data to the end of the input buffer.
9. Run the segment parser loop algorithm.
10. If the segment parser loop algorithm in the previous step was aborted, then abort this algorithm.
11. Jump to the loop top step above.
12. Loop Done: Set the updating attribute to false.
13. Queue a task to fire a simple event named update at this SourceBuffer object.
14. Queue a task to fire a simple event named updateend at this SourceBuffer object.

3.5.7 Range Removal

Follow these steps when a caller needs to initiate a JavaScript visible range removal operation that blocks other SourceBuffer updates:

1. Let start equal the starting presentation timestamp for the removal range.
2. Let end equal the end presentation timestamp for the removal range.
3. Set the updating attribute to true.
4. Queue a task to fire a simple event named updatestart at this SourceBuffer object.
5. Return control to the caller and run the rest of the steps asynchronously.
6. Run the coded frame removal algorithm with start and end as the start and end of the removal range.
7. Set the updating attribute to false.
8. Queue a task to fire a simple event named update at this SourceBuffer object.
9. Queue a task to fire a simple event named updateend at this SourceBuffer object.

3.5.8 Initialization Segment Received

The following steps are run when the segment parser loop successfully parses a complete initialization segment:

Each SourceBuffer object has an internal first initialization segment received flag that tracks whether the first initialization segment 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.

1. Update the duration attribute if it currently equals NaN:

   If the initialization segment contains a duration:

   Run the duration change algorithm with new duration set to the duration in the initialization segment.

   Otherwise:

   Run the duration change algorithm with new duration set to positive Infinity.

2. If the initialization segment has no audio, video, or text tracks, then run the end of stream algorithm with the error parameter set to "decode" and abort these steps.
3. If the first initialization segment received flag is true, then run the following steps:
   1. Verify the following properties. If any of the checks fail then run the end of stream algorithm with the error parameter set to "decode" and abort these steps.
      • The number of audio, video, and text tracks match what was in the first initialization segment.
      • The codecs for each track, match what was specified in the first initialization segment.
      • If more than one track for a single type are present (ie 2 audio tracks), then the Track IDs match the ones in the first initialization segment.
   2. Add the appropriate track descriptions from this initialization segment to each of the track buffers.
   3. Set the need random access point flag on all track buffers to true.
4. Let active track flag equal false.

5. If the first initialization segment received flag is false, then run the following steps:

   1. If the initialization segment contains tracks with codecs the user agent does not support, then run the end of stream algorithm with the error parameter set to "decode" and abort these steps.
      Note

      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 addSourceBuffer().
      For example, MediaSource.isTypeSupported('video/webm;codecs="vp8,vorbis"') may return true, but if addSourceBuffer() was called with 'video/webm;codecs="vp8"' and a Vorbis track appears in the initialization segment, then the user agent may use this step to trigger a decode error.

   2. For each audio track in the initialization segment, run following steps:

      1. Let audio byte stream track ID be the Track ID for the current track being processed.
      2. Let audio language be a BCP 47 language tag for the language specified in the initialization segment for this track or an empty string if no language info is present.
      3. If audio language equals an empty string or the 'und' BCP 47 value, then run the default track language algorithm with byteStreamTrackID set to audio byte stream track ID and type set to "audio" and assign the value returned by the algorithm to audio language.
      4. Let audio label be a label specified in the initialization segment for this track or an empty string if no label info is present.
      5. If audio label equals an empty string, then run the default track label algorithm with byteStreamTrackID set to audio byte stream track ID and type set to "audio" and assign the value returned by the algorithm to audio label.
      6. Let audio kinds be an array of kind strings specified in the initialization segment for this track or an empty array if no kind information is provided.
      7. If audio kinds equals an empty array, then run the default track kinds algorithm with byteStreamTrackID set to audio byte stream track ID and type set to "audio" and assign the value returned by the algorithm to audio kinds.
      8. For each value in audio kinds, run the following steps:
         1. Let current audio kind equal the value from audio kinds for this iteration of the loop.
         2. Let new audio track be a new AudioTrack object.
         3. Generate a unique ID and assign it to the id property on new audio track.
         4. Assign audio language to the language property on new audio track.
         5. Assign audio label to the label property on new audio track.
         6. Assign current audio kind to the kind property on new audio track.

         7. If audioTracks.length equals 0, then run the following steps:

            1. Set the enabled property on new audio track to true.
            2. Set active track flag to true.
         8. Add new audio track to the audioTracks attribute on this SourceBuffer object.
         9. Queue a task to fire a trusted event named addtrack, that does not bubble and is not cancelable, and that uses the TrackEvent interface, at the AudioTrackList object referenced by the audioTracks attribute on this SourceBuffer object.
         10. Add new audio track to the audioTracks attribute on the HTMLMediaElement.
         11. Queue a task to fire a trusted event named addtrack, that does not bubble and is not cancelable, and that uses the TrackEvent interface, at the AudioTrackList object referenced by the audioTracks attribute on the HTMLMediaElement.
      9. Create a new track buffer to store coded frames for this track.
      10. Add the track description for this track to the track buffer.

   3. For each video track in the initialization segment, run following steps:

      1. Let video byte stream track ID be the Track ID for the current track being processed.
      2. Let video language be a BCP 47 language tag for the language specified in the initialization segment for this track or an empty string if no language info is present.
      3. If video language equals an empty string or the 'und' BCP 47 value, then run the default track language algorithm with byteStreamTrackID set to video byte stream track ID and type set to "video" and assign the value returned by the algorithm to video language.
      4. Let video label be a label specified in the initialization segment for this track or an empty string if no label info is present.
      5. If video label equals an empty string, then run the default track label algorithm with byteStreamTrackID set to video byte stream track ID and type set to "video" and assign the value returned by the algorithm to video label.
      6. Let video kinds be an array of kind strings specified in the initialization segment for this track or an empty array if no kind information is provided.
      7. If video kinds equals an empty array, then run the default track kinds algorithm with byteStreamTrackID set to video byte stream track ID and type set to "video" and assign the value returned by the algorithm to video kinds.
      8. For each value in video kinds, run the following steps:
         1. Let current video kind equal the value from video kinds for this iteration of the loop.
         2. Let new video track be a new VideoTrack object.
         3. Generate a unique ID and assign it to the id property on new video track.
         4. Assign video language to the language property on new video track.
         5. Assign video label to the label property on new video track.
         6. Assign current video kind to the kind property on new video track.

         7. If videoTracks.length equals 0, then run the following steps:

            1. Set the selected property on new video track to true.
            2. Set active track flag to true.
         8. Add new video track to the videoTracks attribute on this SourceBuffer object.
         9. Queue a task to fire a trusted event named addtrack, that does not bubble and is not cancelable, and that uses the TrackEvent interface, at the VideoTrackList object referenced by the videoTracks attribute on this SourceBuffer object.
         10. Add new video track to the videoTracks attribute on the HTMLMediaElement.
         11. Queue a task to fire a trusted event named addtrack, that does not bubble and is not cancelable, and that uses the TrackEvent interface, at the VideoTrackList object referenced by the videoTracks attribute on the HTMLMediaElement.
      9. Create a new track buffer to store coded frames for this track.
      10. Add the track description for this track to the track buffer.

   4. For each text track in the initialization segment, run following steps:

      1. Let text byte stream track ID be the Track ID for the current track being processed.
      2. Let text language be a BCP 47 language tag for the language specified in the initialization segment for this track or an empty string if no language info is present.
      3. If text language equals an empty string or the 'und' BCP 47 value, then run the default track language algorithm with byteStreamTrackID set to text byte stream track ID and type set to "text" and assign the value returned by the algorithm to text language.
      4. Let text label be a label specified in the initialization segment for this track or an empty string if no label info is present.
      5. If text label equals an empty string, then run the default track label algorithm with byteStreamTrackID set to text byte stream track ID and type set to "text" and assign the value returned by the algorithm to text label.
      6. Let text kinds be an array of kind strings specified in the initialization segment for this track or an empty array if no kind information is provided.
      7. If text kinds equals an empty array, then run the default track kinds algorithm with byteStreamTrackID set to text byte stream track ID and type set to "text" and assign the value returned by the algorithm to text kinds.
      8. For each value in text kinds, run the following steps:
         1. Let current text kind equal the value from text kinds for this iteration of the loop.
         2. Let new text track be a new TextTrack object.
         3. Generate a unique ID and assign it to the id property on new text track.
         4. Assign text language to the language property on new text track.
         5. Assign text label to the label property on new text track.
         6. Assign current text kind to the kind property on new text track.
         7. Populate the remaining properties on new text track with the appropriate information from the initialization segment.
         8. If the mode property on new text track equals "showing" or "hidden", then set active track flag to true.
         9. Add new text track to the textTracks attribute on this SourceBuffer object.
         10. Queue a task to fire a trusted event named addtrack, that does not bubble and is not cancelable, and that uses the TrackEvent interface, at textTracks attribute on this SourceBuffer object.
         11. Add new text track to the textTracks attribute on the HTMLMediaElement.
         12. Queue a task to fire a trusted event named addtrack, that does not bubble and is not cancelable, and that uses the TrackEvent interface, at the TextTrackList object referenced by the textTracks attribute on the HTMLMediaElement.
      9. Create a new track buffer to store coded frames for this track.
      10. Add the track description for this track to the track buffer.
   5. If active track flag equals true, then run the following steps:
      1. Add this SourceBuffer to activeSourceBuffers.
      2. Queue a task to fire a simple event named addsourcebuffer at activeSourceBuffers
   6. Set first initialization segment received flag to true.

6. If the HTMLMediaElement.readyState attribute is HAVE_NOTHING, then run the following steps:

   1. If one or more objects in sourceBuffers have first initialization segment received flag set to false, then abort these steps.
   2. Set the HTMLMediaElement.readyState attribute to HAVE_METADATA.
   3. Queue a task to fire a simple event named loadedmetadata at the media element.
7. If the active track flag equals true and the HTMLMediaElement.readyState attribute is greater than HAVE_CURRENT_DATA, then set the HTMLMediaElement.readyState attribute to HAVE_METADATA.

3.5.9 Default track language

The following steps are run when the initialization segment received algorithm needs to determine what the default language for a new track should be. This algorithm is initialized with byteStreamTrackID and type parameters when invoked by the initialization segment received algorithm.

1. If trackDefaults contains a TrackDefault object with a type attribute equal to type and a byteStreamTrackID attribute equal to byteStreamTrackID, then return the value of the language attribute on this matching object and abort these steps.
2. If trackDefaults contains a TrackDefault object with a type attribute equal to type and a byteStreamTrackID attribute equal to an empty string, then return the value of the language attribute on this matching object and abort these steps.
3. Return an empty string to the caller.

3.5.10 Default track label

The following steps are run when the initialization segment received algorithm needs to determine what the default label for a new track should be. This algorithm is initialized with byteStreamTrackID and type parameters when invoked by the initialization segment received algorithm.

1. If trackDefaults contains a TrackDefault object with a type attribute equal to type and a byteStreamTrackID attribute equal to byteStreamTrackID, then return the value of the label attribute on this matching object and abort these steps.
2. If trackDefaults contains a TrackDefault object with a type attribute equal to type and a byteStreamTrackID attribute equal to an empty string, then return the value of the label attribute on this matching object and abort these steps.
3. Return an empty string to the caller.

3.5.11 Default track kinds

The following steps are run when the initialization segment received algorithm needs to determine what the default kinds for a new track should be. This algorithm is initialized with byteStreamTrackID and type parameters when invoked by the initialization segment received algorithm.

1. If trackDefaults contains a TrackDefault object with a type attribute equal to type and a byteStreamTrackID attribute equal to byteStreamTrackID, then return the value of the kinds attribute on this matching object and abort these steps.
2. If trackDefaults contains a TrackDefault object with a type attribute equal to type and a byteStreamTrackID attribute equal to an empty string, then return the value of the kinds attribute on this matching object and abort these steps.
3. Return an array with a single empty string element in it to the caller.

3.5.12 Coded Frame Processing

When complete coded frames have been parsed by the segment parser loop then the following steps are run:

1. For each coded frame in the media segment run the following steps:

   1. Loop Top:

      If generate timestamps flag equals true:

      1. Let presentation timestamp equal 0.
      2. Let decode timestamp equal 0.

      Otherwise:

      1. Let presentation timestamp be a double precision floating point representation of the coded frame's presentation timestamp in seconds.
         Note

         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 byte stream format specifications or in separate extension specifications.

      2. Let decode timestamp be a double precision floating point representation of the coded frame's decode timestamp in seconds.
         Note

         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.

   2. Let frame duration be a double precision floating point representation of the coded frame's duration in seconds.
   3. If mode equals "sequence" and group start timestamp is set, then run the following steps:
      1. Set timestampOffset equal to group start timestamp - presentation timestamp.
      2. Set group end timestamp equal to group start timestamp.
      3. Set the need random access point flag on all track buffers to true.
      4. Unset group start timestamp.

   4. If timestampOffset is not 0, then run the following steps:

      1. Add timestampOffset to the presentation timestamp.
      2. Add timestampOffset to the decode timestamp.
   5. Let track buffer equal the track buffer that the coded frame will be added to.

   6. If last decode timestamp for track buffer is set and decode timestamp is less than last decode timestamp:

      OR

      If last decode timestamp for track buffer is set and the difference between decode timestamp and last decode timestamp is greater than 2 times last frame duration:

      1. If mode equals "segments":

         Set group end timestamp to presentation timestamp.

         If mode equals "sequence":

         Set group start timestamp equal to the group end timestamp.

      2. Unset the last decode timestamp on all track buffers.
      3. Unset the last frame duration on all track buffers.
      4. Unset the highest presentation timestamp on all track buffers.
      5. Set the need random access point flag on all track buffers to true.
      6. Jump to the Loop Top step above to restart processing of the current coded frame.

      Otherwise:

      Continue.

   7. Let frame end timestamp equal the sum of presentation timestamp and frame duration.
   8. If presentation timestamp is less than appendWindowStart, then set the need random access point flag to true, drop the coded frame, and jump to the top of the loop to start processing the next coded frame.
      Note

      Some implementations may choose to collect some of these coded frames that are outside the append window and use them to generate a splice at the first coded frame that has a presentation timestamp greater than or equal to appendWindowStart even if that frame is not a random access point. Supporting this requires multiple decoders or faster than real-time decoding so for now this behavior will not be a normative requirement.

   9. If frame end timestamp is greater than appendWindowEnd, then set the need random access point flag to true, drop the coded frame, and jump to the top of the loop to start processing the next coded frame.
   10. If the decode timestamp is less than the presentation start time, then run the end of stream algorithm with the error parameter set to "decode", and abort these steps.
   11. If the need random access point flag on track buffer equals true, then run the following steps:
       1. If the coded frame is not a random access point, then drop the coded frame and jump to the top of the loop to start processing the next coded frame.
       2. Set the need random access point flag on track buffer to false.
   12. Let spliced audio frame be an unset variable for holding audio splice information
   13. Let spliced timed text frame be an unset variable for holding timed text splice information
   14. If last decode timestamp for track buffer is unset and presentation timestamp falls within the presentation interval of a coded frame in track buffer,then run the following steps:
       1. Let overlapped frame be the coded frame in track buffer that matches the condition above.

       2. If track buffer contains audio coded frames:

          Run the audio splice frame algorithm and if a splice frame is returned, assign it to spliced audio frame.

          If track buffer contains video coded frames:

          1. Let overlapped frame presentation timestamp equal the presentation timestamp of overlapped frame.
          2. Let remove window timestamp equal overlapped frame presentation timestamp plus 1 microsecond.
          3. If the presentation timestamp is less than the remove window timestamp, then remove overlapped frame and any coded frames that depend on it from track buffer.
             Note

             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.

          If track buffer contains timed text coded frames:

          Run the text splice frame algorithm and if a splice frame is returned, assign it to spliced timed text frame.

   15. Remove existing coded frames in track buffer:

       If highest presentation timestamp for track buffer is not set:

       Remove all coded frames from track buffer that have a presentation timestamp greater than or equal to presentation timestamp and less than frame end timestamp.

       If highest presentation timestamp for track buffer is set and less than or equal to presentation timestamp:

       Remove all coded frames from track buffer that have a presentation timestamp greater than or equal to highest presentation timestamp and less than frame end timestamp

   16. Remove decoding dependencies of the coded frames removed in the previous step:

       If detailed information about decoding dependencies is available:

       Remove all coded frames from track buffer that have decoding dependencies on the coded frames removed in the previous step.

       Note

       For example if an I-frame is removed in the previous step, then all P-frames & B-frames that depend on that I-frame should be removed from track buffer. This makes sure that decode dependencies are properly maintained during overlaps.

       Otherwise:

       Remove all coded frames between the coded frames removed in the previous step and the next random access point after those removed frames.

       Note

       Removing all coded frames until the next random access point 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.

   17. If spliced audio frame is set:

       Add spliced audio frame to the track buffer.

       If spliced timed text frame is set:

       Add spliced timed text frame to the track buffer.

       Otherwise:

       Add the coded frame with the presentation timestamp, decode timestamp, and frame duration to the track buffer.

   18. Set last decode timestamp for track buffer to decode timestamp.
   19. Set last frame duration for track buffer to frame duration.
   20. If highest presentation timestamp for track buffer is unset or frame end timestamp is greater than highest presentation timestamp, then set highest presentation timestamp for track buffer to frame end timestamp.
       Note

       The greater than check is needed because bidirectional prediction between coded frames can cause presentation timestamp to not be monotonically increasing eventhough the decode timestamps are monotonically increasing.

   21. If frame end timestamp is greater than group end timestamp, then set group end timestamp equal to frame end timestamp.
   22. If generate timestamps flag equals true, then set timestampOffset equal to frame end timestamp.

2. If the HTMLMediaElement.readyState attribute is HAVE_METADATA and the new coded frames cause HTMLMediaElement.buffered to have a TimeRange for the current playback position, then run the following steps:

   1. Set the HTMLMediaElement.readyState attribute to HAVE_CURRENT_DATA.
   2. If this is the first transition to HAVE_CURRENT_DATA, then queue a task to fire a simple event named loadeddata at the media element.

3. If the HTMLMediaElement.readyState attribute is HAVE_CURRENT_DATA and the new coded frames cause HTMLMediaElement.buffered to have a TimeRange that includes the current playback position and some time beyond the current playback position, then run the following steps:

   1. Set the HTMLMediaElement.readyState attribute to HAVE_FUTURE_DATA.
   2. Queue a task to fire a simple event named canplay at the media element.

4. If the HTMLMediaElement.readyState attribute is HAVE_FUTURE_DATA and the new coded frames cause HTMLMediaElement.buffered to have a TimeRange that includes the current playback position and enough data to ensure uninterrupted playback, then run the following steps:

   1. Set the HTMLMediaElement.readyState attribute to HAVE_ENOUGH_DATA.
   2. Queue a task to fire a simple event named canplaythrough at the media element.
5. If the media segment contains data beyond the current duration, then run the duration change algorithm with new duration set to the maximum of the current duration and the group end timestamp.

3.5.13 Coded Frame Removal Algorithm

Follow these steps when coded frames for a specific time range need to be removed from the SourceBuffer:

1. Let start be the starting presentation timestamp for the removal range.
2. Let end be the end presentation timestamp for the removal range.

3. For each track buffer in this source buffer, run the following steps:

   1. Let remove end timestamp be the current value of duration

   2. If this track buffer has a random access point timestamp that is greater than or equal to end, then update remove end timestamp to that random access point timestamp.

      Note

      Random access point timestamps can be different across tracks because the dependencies between coded frames within a track are usually different than the dependencies in another track.

   3. Remove all media data, from this track buffer, that contain starting timestamps greater than or equal to start and less than the remove end timestamp.
   4. Remove decoding dependencies of the coded frames removed in the previous step:

      If detailed information about decoding dependencies is available:

      Remove all coded frames from this track buffer that have decoding dependencies on the coded frames removed in the previous step.

      Note

      For example if an I-frame is removed in the previous step, then all P-frames & B-frames that depend on that I-frame should be removed from this track buffer.

      Otherwise:

      Remove all coded frames between the coded frames removed in the previous step and the next random access point after those removed frames.

      Note

      Removing all coded frames until the next random access point 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.

   5. If this object is in activeSourceBuffers, the current playback position is greater than or equal to start and less than the remove end timestamp, and HTMLMediaElement.readyState is greater than HAVE_METADATA, then set the HTMLMediaElement.readyState attribute to HAVE_METADATA and stall playback.

      Note

      This transition occurs because media data for the current position has been removed. Playback cannot progress until media for the current playback position is appended or the selected/enabled tracks change.

4. If buffer full flag equals true and this object is ready to accept more bytes, then set the buffer full flag to false.

3.5.14 Coded Frame Eviction Algorithm

This algorithm is run to free up space in this source buffer when new data is appended.

1. Let new data equal the data that is about to be appended to this SourceBuffer.
2. If the buffer full flag equals false, then abort these steps.
3. Let removal ranges equal a list of presentation time ranges that can be evicted from the presentation to make room for the new data.
   Note

   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 buffered attribute to observe whether portions of the buffered data have been evicted.

4. For each range in removal ranges, run the coded frame removal algorithm with start and end equal to the removal range start and end timestamp respectively.

3.5.15 Audio Splice Frame Algorithm

Follow these steps when the coded frame processing algorithm needs to generate a splice frame for two overlapping audio coded frames:

1. Let track buffer be the track buffer that will contain the splice.
2. Let new coded frame be the new coded frame, that is being added to track buffer, which triggered the need for a splice.
3. Let presentation timestamp be the presentation timestamp for new coded frame
4. Let decode timestamp be the decode timestamp for new coded frame.
5. Let frame duration be the coded frame duration of new coded frame.
6. Let overlapped frame be the coded frame in track buffer with a presentation interval that contains presentation timestamp.
7. Update presentation timestamp and decode timestamp to the nearest audio sample timestamp based on sample rate of the audio in overlapped frame. If a timestamp is equidistant from both audio sample timestamps, then use the higher timestamp. (eg. floor(x * sample_rate + 0.5) / sample_rate).
   Note

   For example, given the following values:

   • The presentation timestamp of overlapped frame equals 10.
   • The sample rate of overlapped frame equals 8000 Hz
   • presentation timestamp equals 10.01255
   • decode timestamp equals 10.01255

   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)

8. If the user agent does not support crossfading then run the following steps:
   1. Remove overlapped frame from track buffer.
   2. Add a silence frame to track buffer with the following properties:
      • The presentation timestamp set to the overlapped frame presentation timestamp.
      • The decode timestamp set to the overlapped frame decode timestamp.
      • The coded frame duration set to difference between presentation timestamp and the overlapped frame presentation timestamp.
      Note

      Some implementations may apply fades to/from silence to coded frames on either side of the inserted silence to make the transition less jarring.

   3. Return to caller without providing a splice frame.
      Note

      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.

9. Let frame end timestamp equal the sum of presentation timestamp and frame duration.
10. Let splice end timestamp equal the sum of presentation timestamp and the splice duration of 5 milliseconds.
11. Let fade out coded frames equal overlapped frame as well as any additional frames in track buffer that have a presentation timestamp greater than presentation timestamp and less than splice end timestamp.
12. Remove all the frames included in fade out coded frames from track buffer.
13. Return a splice frame with the following properties:
    • The presentation timestamp set to the overlapped frame presentation timestamp.
    • The decode timestamp set to the overlapped frame decode timestamp.
    • The coded frame duration set to difference between frame end timestamp and the overlapped frame presentation timestamp.
    • The fade out coded frames equals fade-out coded frames.
    • The fade in coded frame equal new coded frame.
      Note

      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 splice timestamp equals presentation timestamp.
    Note

    See the audio splice rendering algorithm for details on how this splice frame is rendered.

3.5.16 Audio Splice Rendering Algorithm

The following steps are run when a spliced frame, generated by the audio splice frame algorithm, needs to be rendered by the media element:

1. Let fade out coded frames be the coded frames that are faded out during the splice.
2. Let fade in coded frames be the coded frames that are faded in during the splice.
3. Let presentation timestamp be the presentation timestamp of the first coded frame in fade out coded frames.
4. Let end timestamp be the sum of the presentation timestamp and the coded frame duration of the last frame in fade in coded frames.
5. Let splice timestamp be the presentation timestamp where the splice starts. This corresponds with the presentation timestamp of the first frame in fade in coded frames.
6. Let splice end timestamp equal splice timestamp plus five milliseconds.
7. Let fade out samples be the samples generated by decoding fade out coded frames.
8. Trim fade out samples so that it only contains samples between presentation timestamp and splice end timestamp.
9. Let fade in samples be the samples generated by decoding fade in coded frames.
10. If fade out samples and fade in samples do not have a common sample rate and channel layout, then convert fade out samples and fade in samples to a common sample rate and channel layout.
11. Let output samples be a buffer to hold the output samples.
12. Apply a linear gain fade out with a starting gain of 1 and an ending gain of 0 to the samples between splice timestamp and splice end timestamp in fade out samples.
13. Apply a linear gain fade in with a starting gain of 0 and an ending gain of 1 to the samples between splice timestamp and splice end timestamp in fade in samples.
14. Copy samples between presentation timestamp to splice timestamp from fade out samples into output samples.
15. For each sample between splice timestamp and splice end timestamp, compute the sum of a sample from fade out samples and the corresponding sample in fade in samples and store the result in output samples.
16. Copy samples between splice end timestamp to end timestamp from fade in samples into output samples.
17. Render output samples.

Note

Here is a graphical representation of this algorithm.

3.5.17 Text Splice Frame Algorithm

Follow these steps when the coded frame processing algorithm needs to generate a splice frame for two overlapping timed text coded frames:

1. Let track buffer be the track buffer that will contain the splice.
2. Let new coded frame be the new coded frame, that is being added to track buffer, which triggered the need for a splice.
3. Let presentation timestamp be the presentation timestamp for new coded frame
4. Let decode timestamp be the decode timestamp for new coded frame.
5. Let frame duration be the coded frame duration of new coded frame.
6. Let frame end timestamp equal the sum of presentation timestamp and frame duration.
7. Let first overlapped frame be the coded frame in track buffer with a presentation interval that contains presentation timestamp.
8. Let overlapped presentation timestamp be the presentation timestamp of the first overlapped frame.
9. Let overlapped frames equal first overlapped frame as well as any additional frames in track buffer that have a presentation timestamp greater than presentation timestamp and less than frame end timestamp.
10. Remove all the frames included in overlapped frames from track buffer.
11. Update the coded frame duration of the first overlapped frame to presentation timestamp - overlapped presentation timestamp.
12. Add first overlapped frame to the track buffer.
13. Return to caller without providing a splice frame.
    Note

    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.