Media Timed Events

3.1 Dynamic content insertion

A media content provider wants to allow insertion of content, such as personalised video, local news, or advertisements, into a video media stream that contains the main program content. To achieve this, media timed events can be used to describe the points on the media timeline, known as splice points, where switching playback to inserted content is possible.

The Society for Cable and Televison Engineers (SCTE) specification "Digital Program Insertion Cueing for Cable" [SCTE35] defines a data cue format for describing such insertion points. Use of these cues in MPEG-DASH and HLS streams is described in [SCTE35], sections 12.1 and 12.2.

3.2 Audio stream with titles and images

A media content provider wants to provide visual information alongside an audio stream, such as an image of the artist and title of the current playing track, to give users live information about the content they are listening to.

HLS timed metadata [HLS-TIMED-METADATA] uses in-band ID3 metadata to carry the artist and title information, and image content. RadioVIS in DVB ([DVB-DASH], section 9.1.7) defines in-band event messages that contain image URLs and text messages to be displayed, with information about when the content should be displayed in relation to the media timeline.

3.3 Control messages for media streaming clients

MPEG-DASH defines a number of in-band delivered control messages that are used to notify a client appication or library such as dash.js. These messages include: MPEG-DASH defines a number of control messages for media streaming clients (e.g., libraries such as dash.js). These messages are carried in-band in the media container files. Use cases include:

• Signalling that the DASH manifest document (MPD) has expired and should be updated. This method is used as an alternative to setting a cache duration in the response to the HTTP request for the manifest, so the client can refresh the manifest document when it actually changes, as opposed to waiting for a cache duration expiry period to elapse. This also has the benefit of reducing the load on HTTP servers caused by frequent server requests.
• Analytics callback events, to allow content providers to track media playback. In response to this message, to the client makes an HTTP request to a URL specified in the media timed event data.
• Signalling early termination of the media presentation, for cases where the media ends earlier than expected from the current DASH manifest document.

Reference: M&E IG call 1 Feb 2018: Minutes, [DASH-EVENTING].

3.4 Subtitle and caption rendering synchronization

A subtitle or caption author wants ensure that subtitle changes are aligned as closely as possible to shot changes in the video. The BBC Subtitle Guidelines [BBC-SUBTITLE] describes authoring best practices. In particular, in section 6.1 authors are advised "it is likely to be less tiring for the viewer if shot changes and subtitle changes occur at the same time. Many subtitles therefore start on the first frame of the shot and end on the last frame."

3.5 Synchronized map animations

A user records footage with metadata, including geolocation, on a mobile video device, e.g., drone or dashcam, to share on the web alongside a map, e.g., OpenStreetMap.

[WEBVMT] is an open format for metadata cues, synchronized with a timed media file, that can be used to drive an online map rendered in a separate HTML element alongside the media element on the web page. The media playhead position controls presentation and animation of the map, e.g., pan and zoom, and allows annotations to be added and removed, e.g., markers, at specified times during media playback. Control can also be overridden by the user with the usual interactive features of the map at any time, e.g., zoom. Concrete examples are provided by the tech demos at the WebVMT website.

3.6 Media analysis visualization

A video image analysis system processes a media stream to detect and recognize objects shown in the video. This system generates metadata describing the objects, including timestamps that describe the when the objects are visible, together with position information (e.g., bounding boxes). A web application then uses this timed metadata to overlay labels and annotations on the video using HTML and CSS.

3.7 Presentation of auxiliary content in live media

During a live media presentation, dynamic and unpredictable events may occur which cause temporary suspension of the media presentation. During that suspension interval, auxiliary content such as the presentation of UI controls and media files, may be unavailable. Depending on the specific user engagement (or not) with the UI controls and the time at which any such engagement occurs, specific web resources may be rendered at defined times in a synchronized manner. For example, a multimedia A/V clip along with subtitles corresponding to an advertisement, and which were previously downloaded and cached by the UA, are played out.

4.1 MPEG Common Media Application Format (CMAF)

MPEG Common Media Application Format (CMAF) [MPEGCMAF] is a media container format optimized for large scale delivery of a single encrypted, adaptable multimedia presentation to a wide range of devices and adaptive streaming methods, including HTTP Live Streaming [RFC8216] and MPEG-DASH [MPEGDASH]. It is based on the ISO BMFF [ISOBMFF] and supports the AVC, AAC, HEVC codecs, Common Encryption (CENC), and subtitles using IMSC1 and WebVTT. Its goal is to reduce media storage and delivery costs by using a single common media format across different client devices.

CMAF media may contain in-band media timed events in the form of Event Message (emsg) boxes in ISO BMFF files. emsg is specified in [MPEGDASH], section 5.10.3.3, and described in more detail in the following section of this document.

4.2 MPEG-DASH

MPEG-DASH is an adaptive bitrate streaming technique in which the audio and video media is partitioned into segments. The Media Presentation Description (MPD) is an XML document that contains metadata required by a DASH client to access the media segments and to provide the streaming service to the user. The media segments can use any codec, typically within a fragmented MP4 (ISO BMFF) container or MPEG-2 transport stream.

In MPEG-DASH, media timed events may be delivered either in-band or out-of-band:

• In-band media timed events are delivered via "event message" (emsg) boxes in ISO BMFF files. The presence of emsg events in the media container for given event schemes is signaled in the MPD document using an EventStream XML element ([MPEGDASH], section 5.10.2).
• Out-of-band media timed events are delivered via Event XML elements contained within an EventStream element in the MPD.

An emsg event contains the following information, as specified in [MPEGDASH], section 5.10.3.3:

• id — Event message identifier
• scheme_id_uri — A URI that identifies the message scheme
• value — The event value (string)
• timescale — Timescale units, in ticks per second
• presentation_time_delta — Presentation time delta (with respect to the media segment), in timescale units
• event_duration — Event duration, in timescale units
• message_data — Message body (may be empty)

4.3 HTTP Live Streaming

HTTP Live Streaming (HLS) allows for delivery of timed metadata events, both in-band and out-of-band:

• HLS supports delivery of ID3 timed metadata carried in-band within MPEG-2 Transport Streams [HLS-TIMED-METADATA]. ID3 metadata is stored as a complete ID3v2.4 frame in an elementary stream (PES) packet, including a complete ID3 header [ID3v2].
• Out-of-band events are delivered using the EXT-X-DATERANGE tag in a HLS playlist file.

An EXT-X-DATERANGE tag contains the following information, as specified in [RFC8216], section 4.3.2.7:

• ID — Unique event identifier
• CLASS — An identifier that indicates the event semantics. All events with the same CLASS have the same semantics
• START-DATE — The date and time of the start of the event
• END-DATE — The date and time of the end of the event (optional)
• DURATION — Event duration, in seconds (optional). May be zero
• PLANNED-DURATION — Expected event duration, where the actual duration is not yet known (optional)
• END-ON-NEXT — Indicates that the event automatically ends when the next event of the same CLASS starts. If present, this attribute replaces END-DATE and DURATION
• X-<client-attribute> — Allows the application to define its own key/value metadata pairs

4.4 HbbTV

HbbTV is an interactive TV application standard that supports both broadcast (DVB) media delivery, and internet streaming using MPEG-DASH. The HbbTV application environment is based on HTML and JavaScript. MPEG-DASH streaming is implemented natively by the user agent, rather than through a JavaScript web application using Media Source Extensions.

HbbTV includes support for emsg events ([DVB-DASH], section 9.1) and requires this be mapped to HTML5 DataCue ([HBBTV], section 9.3.2). The revision of HTML5 referenced by [HBBTV] is [html51-20151008]. This feature is included in user agents shipping in connected TVs across Europe from 2017.

The HbbTV device test suite includes test pages and streams that cover emsg support. HbbTV has a reference application and content for DASH+DRM which includes emsg support.

4.5 DASH Industry Forum APIs for Interactivity

The DASH-IF InterOp Working Group has an ongoing work item, DAInty, "DASH APIs for Interactivity", which aims to specify a set of APIs between the DASH client/player and interactivity-capable applications, for both web and native applications [DASHIFIOP]. The origin of this work is a related 3GPP work item on Service Interactivity [3GPP-INTERACTIVITY]. The objective is to provide service enablers for user engagement with auxiliary content and UIs on mobile device during live or time-shifted viewing of streaming content delivered over 3GPP broadcast or unicast bearers, and the measurement and reporting of such interactive consumption.

Two APIs are being developed that are relevant to the scope of the present document:

• Application subscription/DASH client dispatch of DASH event stream messages containing interactivity information. Events can be delivered in-band (emsg) and/or as MPD events.
• Application subscription/DASH client dispatch of ISO BMFF Timed Metadata tracks providing similar functionality to DASH event streams.

Two modes for dispatching events are defined [DASHIF-EVENTS]. In on-receive mode, events are dispatched at the time the event arrives, and in on-start mode, events are dispatched at the given time on the media timeline. The "arrival" of events from the DASH client perspective may be either static or pre-provisioned, in the case MPD Events, or dynamic in the case of in-band events carried in emsg boxes. The application can register with the DASH client which mode to use.

4.6 SCTE-35

The Society for Cable and Televison Engineers (SCTE) has produced the SCTE-35 specification "Digital Program Insertion Cueing for Cable" [SCTE35], which defines a data cue format for describing insertion points, to support the dynamic content insertion use case.

[SCTE214-1] section 6.7 describes the carriage of SCTE-35 events as out-of-band events in a MPEG-DASH MPD document. [SCTE214-2] section 9 and [SCTE214-3] section 7.3 describe the carriage of SCTE-35 events as in-band events in MPEG-DASH using MPEG2-TS and ISO BMFF respectively, using emsg.

[RFC8216] section 4.3.2.7.1 specifies how to map SCTE-35 events into HLS timed metadata, using the EXT-X-DATERANGE tag, with SCTE35-CMD, SCTE35-OUT, and SCTE35-IN attributes.

This places an implicit requirement on the user agent in handling of event synchronization related to insertion cues. The content originator may provide the cue in advance with as little as 2 seconds of the insertion time. Therefore the propagation of the event data associated with the insertion cue to the application by the user agent should be considerably less than 2 seconds.

4.7 MPEG Working Draft on Carriage of Web Resources in ISO BMFF

The MPEG Working Draft on Carriage of Web Resources in ISO BMFF [WEB-ISOBMFF] is a draft document that specifies the use of the ISO BMFF container format for the storage and delivery of web content. The goal is to allow web resources (HTML, JavaScript, etc.) to be parsed from the storage and processed by a user agent at specific presentation times on the media timeline, and so be synchronized with other tracks within the container, such as audio, video, and subtitles.

The Media & Entertainment Interest Group is actively tracking this work and is open to discussing specific requirements for synchronized rendering of in-band delivered web resources, as development progresses.

4.8 WebVTT

[WEBVTT] is a W3C specification that provides a format for web video text tracks. A VTTCue is a text track cue, and may have attributes that affect rendering of the cue text on a web page. WebVTT metadata cues are text that is aligned to the media timeline. Web applications can use VTTCue to carry arbitrary data by serializing the data to a string format (JSON, for example) when creating the cue, and deserializing the data when the cue's onenter DOM event is fired.

Web applications can also use VTTCue to trigger rendering of out-of-band delivered timed text cues, such as TTML or IMSC format captions.

5.1 MPEG-DASH and ISO BMFF emsg events

The DataCue API has been previously discussed as a means to deliver in-band media timed event data to web applications, but this is not implemented in all of the main browser engines. It is included in the 18 October 2018 HTML 5.3 draft [HTML53-20181018], but is not included in [HTML]. See discussion here and notes on implementation status here.

WebKit supports a DataCue interface that extends HTML5 DataCue with two attributes to support non-text metadata, type and value.

interface DataCue : TextTrackCue {
  attribute ArrayBuffer data; // Always empty

  // Proposed extensions.
  attribute any value;
  readonly attribute DOMString type;
};

type is a string identifying the type of metadata:

and value is an object with the metadata item key, data, and optionally a locale:

value = {
  key: String
  data: String | Number | Array | ArrayBuffer | Object
  locale: String
}

Neither [MSE-BYTE-STREAM-FORMAT-ISOBMFF] nor [INBANDTRACKS] describe handling of emsg boxes.

On resource constrained devices such as smart TVs and streaming sticks, parsing media segments to extract event information leads to a significant performance penalty, which can have an impact on UI rendering updates if this is done on the UI thread. There can also be an impact on the battery life of mobile devices. Given that the media segments will be parsed anyway by the user agent, parsing in JavaScript is an expensive overhead that could be avoided.

Avoiding parsing in JavaScript is also important for low latency video streaming applications, where minimizing the time taken to pass media content through to the media element's playback buffer is essential.

[HBBTV] section 9.3.2 describes a mapping between the emsg fields described above and the TextTrack and DataCue APIs. A TextTrack instance is created for each event stream signalled in the MPD document (as identified by the schemeIdUri and value), and the inBandMetadataTrackDispatchType TextTrack attribute contains the scheme_id_uri and value values. Because HbbTV devices include a native DASH client, parsing of the MPD document and creation of the TextTracks is done by the user agent, rather than by application JavaScript code.

5.2 Synchronized rendering of web resources

In browsers, non media web rendering is handled through repaint operations at a rate that generally matches the display refresh rate (e.g., 60 times per second), following the user's wall clock. A web application can schedule actions and render web content at specific points on the user's wall clock, notably through Performance.now(), setTimeout(), setInterval(), and requestAnimationFrame().

In most cases, media rendering follows a different path, be it because it gets handled by a dedicated background process or by dedicated hardware circuitry. As a result, progress along the media timeline may follow a clock different from the user's wall clock. [HTML] recommends that the media clock approximate the user's wall clock but does not require it to match the user's wall clock.

To synchronize rendering of web content to a video with frame accuracy, a web application needs:

• A way to track progress along the media timeline with sufficient precision. The actual precision required depends on the use case. Subtitles for video are typically authored against video at the nominal video frame rate, e.g., 25 frames per second, which corresponds to 40 milliseconds per frame, even when the actual video frame rate gets adjusted dynamically ([EBU-TT-D], Annex E). This suggests a 20 milliseconds precision, or half of the duration of a typical video frame, to render subtitles with frame accuracy.
• In cases where synchronization needs to occur at frame boundaries, a way to tie the rendering of non media content, typically done at the display refresh rate, with the rendering of a video frame. This need does not replace the former one: a web application that needs to render web content at media frame boundaries may also need to perform actions at specific points on the media timeline regardless of when the next frame gets rendered.

The following sub-sections discusses mechanisms currently available to web applications to track progress on the media timeline and render content at frame boundaries.

6.1 Subscribing to receive media timed event cues

The API should allow web applications to subscribe to receive specific types of media timed event cue. For example, to support MPEG-DASH emsg and MPD events, the cue type is identified by a combination of the scheme_id_uri and (optional) value. The purpose of this is to make receiving cues of each type opt-in from the application's point of view. The user agent should deliver only those cues to a web application for which the application has subscribed. The API should also allow web applications to unsubscribe from specific cue types.

6.2 Out-of-band events

To be able to handle out-of-band media timed event cues, including MPEG-DASH MPD events, the API should allow web applications to create and add timed data cues to the media timeline, to be triggered by the user agent. The API should allow the web application to provide all necessary parameters to define the cue, including start and end times, cue type identifier, and data payload. The payload should be any data type (e.g., the set of types supported by the WebKit DataCue).

6.3 Event triggering

For those events that the application has subscribed to receive, the API should:

• Generate a DOM event when an in-band media timed event cue is parsed from the media container or media stream (DASH-IF on-receive mode).
• Generate DOM events when the current media playback position reaches the start time and the end time of a media timed event cue during playback (DASH-IF on-start mode). This applies equally to cues generated by the user agent when parsed from the media container and cues added by the web application.

The API should provide guarantees that no media timed event cues can be missed during linear playback of the media.

6.4 In-band media timed event processing

We recommend updating [INBANDTRACKS] to describe handling of in-band media timed events supported on the web platform, possibly following a registry approach with one specification per media format that describes the details of how media timed events are carried in that format.

6.5 MPEG-DASH events

We recommend that browser engines support MPEG-DASH emsg in-band events and MPD out-of-band events, as part of their support for the MPEG Common Media Application Format (CMAF) [MPEGCMAF].

6.6 Synchronization

In order to achieve greater synchronization accuracy between media playback and web content rendered by an application, the time marches on steps in [HTML] should be modified to allow delivery of cue onenter and onexit DOM events within 20 milliseconds of their positions on the media timeline.

Additionally, to allow such synchronization to happen at frame boundaries, we recommend introducing a mechanism that would allow a web application to accurately predict, using the user's wall clock, when the next frame will be rendered (e.g., as done in the Web Audio API).