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 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.

Examples include HLS timed metadata [ HLS-TIMED-METADATA ], which uses in-band ID3 metadata to carry the image content, and RadioVIS in DVB ([ DVB-DASH ], section 9.1.7), which 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.2 3.3 MPEG-DASH manifest expiry notifications

Section 5.10.4 of [ MPEGDASH ] describes an MPEG-DASH specific event that is used to notify a DASH player web application that it should refresh its copy of the manifest (MPD) document. An in-band emsg event is used an alternative to setting a cache duration in the response to the HTTP request for the manifest, so the client can refresh the MPD when it actually changes, so reducing the load on HTTP servers caused by frequent server requests.

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.3 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.

Reference: M&E IG TF call 17 Sept 2018: Minutes .

3.4 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.5 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. The 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 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 events are emsg boxes in ISO BMFF files. The presence of emsg events in the media container for given event schemes is signalled in the MPD document using an EventStream XML element ([ MPEGDASH ], section 5.10.2).
• Out-of-band events are represented by 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:

• 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
• id — Event message identifier
• message_data — Message body (may be empty)

4.2 4.3 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 nativey 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-TESTS ]). HbbTV has a reference application and content for DASH+DRM which includes emsg support.

4.3 4.4 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. The origin of this work is a related 3GPP work item on Service Interactivity ([ 3GPP-INTERACTIVITY-WID ], [ 3GPP-INTERACTIVITY-TR ]). 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. In Mode 1, events are dispatched at the time the event arrives, and in Mode 2, 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 inband events carried in the emsg . The application can register with the DASH client which Mode to use.

Reference: M&E IG, Media Timed Events Task Force call 20 Aug 2018: Minutes .

4.4 4.5 BBC Subtitle Guidelines SCTE-35

The BBC Subtitle Guidelines ([ Society for Cable and Televison Engineers (SCTE) has produced the SCTE-35 specification "Digital Program Insertion Cueing for Cable" [ BBC-SUBTITLES SCTE35 ]) describe best practice ], which defines a data cue format for authoring subtitles or captions. In particular, the guidelines place requirements on the synchronization accuracy of caption rendering. For example, in section 6.1, caption authors are advised "it is likely describing insertion points, 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 support the last frame." dynamic content insertion use case.

Subtitles for video are typically authored against video at a nominal frame rate, e.g., 25 frames per second, which corresponds to 40 milliseconds per frame. The actual video frame rate may be adjusted dynamically according to the video encoding, but the subtitle timing must remain the same ([ [ EBU-TT-D SCTE214-1 ], Annex E). Where captions are rendered by application JavaScript code, ] section 6.7 describes the carriage of SCTE-35 events in response to TextTrackCue events, this places a requirement on user agents for timely delivery of these events, so that application code can respond and render the cues. 4.5 SCTE Media Splicing Requirements MPEG-DASH MPD document, as out-of-band events. [ SCTE214-2 The Society for Cable ] section 9 and Televison Engineers (SCTE) has produced [ SCTE214-3 ] section 7.3 describe the carriage of SCTE-35 specification "Digital Program Insertion Cueing for Cable" events as in-band events in MPEG-DASH using MPEG2-TS and ISO BMFF respectively, using emsg .

This places an implicit requirement on the user agent in handling media-timed events 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.6 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 is open to discussing specific requirements for media timed events as development progresses.

4.7 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 schedule out-of-band metadata events by serializing the event data to a string format (JSON, for example) when creating the cue, and deserializing the data when the cue is triggered.

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.1 5.1 MPEG-DASH and ISO BMFF emsg events

The DataCue API has been previously discussed as a means to deliver in-band 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.

[ 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 TextTrack s is done by the user agent, rather than by application JavaScript code.

Editor's note 5.2 Synchronization of text track cue rendering To support DASH clients implemented in web applications, there is therefore either a need

Subtitles for an API that allows applications to tell the UA video are typically authored against video at a nominal frame rate, e.g., 25 frames per second, which schemes it wants corresponds to receive, or the UA should simply expose all event streams 40 milliseconds per frame. The actual video frame rate may be adjusted dynamically according to applications. Which of these is preferred? 5.1.2 Synchronization and the video encoding, but the subtitle timing must remain the same ([ EBU-TT-D ], Annex E).

This places a requirement on user agents for timely delivery of TextTrackCue and VTTCue events, so that application code can respond and render the cues. For subtitle rendering to be possible with frame accuracy, we recommend that cue events are fired within 20 milliseconds of their position on the media timeline .

The timing guarantees provided time marches on steps in [ HTML ] regarding control the triggering firing of cue events during media playback. Time marches on requires a TextTrackCue timeupdate events may event to be not fired at the HTMLMediaElement between 15 and 250 milliseconds since the last such event, and this requirement therefore specifies the rate at which time marches on is executed during playback. In practice it has been found that the timing varies between browser implementations.

There are two methods a web application can use to handle text track cues:

• Add an oncuechange handler function to the TextTrack and inspect the track's activeCues list. Because activeCues contains the list of cues that are active at the time that time marches on is run, it is possible for cues to be enough missed by a web application using this method, where cues appear on the media timeline between successive executions of time marches on during media playback. This may occur if the cues have short duration, or by a long-running event handler function.
• Add onenter and onexit handler functions to avoid each cue. The time marches on steps guarantee that enter and exit events being missed . will be fired for all cues, including those that appear on the media timeline between successive executions of time marches on during media playback. This method is only possible for cues created by the web application, i.e., VTTCue objects, and not cue objects created by the user agent.

An issue with handling of text track and data cue events in HbbTV was reported in 2013. HbbTV requires the user agent to implement an MPEG-DASH client, and so applications must use the first of the above methods for cue handling, which means that applications can miss cues as described above.

5.2 5.3 Synchronized rendering of web resources

5.3 5.4 Rendering of web content embedded in media containers

There is no API for surfacing web content embedded in ISO BMFF containers into the browser (e.g., the HTMLCue proposal discussed at TPAC 2015 ).

6.1 Subscribing to event streams

The API should allow web applications to subscribe to receive specific event types. For example, to support DASH emsg and MPD events, the API should allow subscription by id and (optional) value . This is to make receiving events opt-in from the application point of view. The user agent should deliver only those events to a web application for which the application has subscribed. The API should also allow web applications to unsubscribe from specific event streams by event type.

6.2 Out-of-band events

To be able to handle out of band events, the API must allow web applications to create events to be added 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 event, including start and end times, event type, and data payload. The payload should be any data type (e.g., the set of types supported by the WebKit DataCue ). For DASH MPD events, the event type is defined by the id and (optional) value fields.

6.3 Event triggering

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

• Generate a JavaScript event when an in-band media timed event is parsed from the media container or media stream (DAInty Mode 1) 1).
• Generate a JavaScript event events when the current media playback position reaches the start time and the end time of a media timed event during playback (DAInty Mode 2). This applies equally to in-band events that the user agent has extracted from the media container, and out-of-band events added by the web application.

The API must provide guarantees that no events can be missed during linear playback of the media.

6.4 In-band event processing

We recommend updating [ INBANDTRACKS ] to describe handling of in-band media timed events supported on the web platform, following a registry approach with one specification per media format that describes the event details for 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

The In order to acheive greater synchronization accuracy between media playback and web content rendered by an application, the time marches on algorithm steps in [ HTML ] should be reviewed and updated to ensure that events are delivered modified to the web application within allow delivery of media timed event start time constraints described elsewhere in this report. and end time notifications within 20 milliseconds of their positions on the media timeline .