Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We also use an additional compliance term not described in RFC2119:

  • CONDITIONALLY REQUIRED - an item or a feature is supported in the browser if the underlying platform supports this capability.

...

3.3.2.1 Restrictions for HLS content

  1. Audio/video encoding

    1. The same codec MUST be used across all variant streams (all quality levels).

    2. Audio parameters (number of channels and sample rates) MUST be the same across all variant streams.

  2. Media segments

    1. All media segments MUST be independently decodable. Consequently, the first video frame in every segment that contains video MUST be an IDR frame.

    2. Discontinuities in timestamps, frame rate, encoding profiles, or audio/video parameters MUST NOT occur within segments.

  3. Playlist files (M3U8)

    1. Audio and video playlists MUST use the same target duration and MUST contain the same duration of the content.

    2. A playlist MUST NOT contain invalid URLs.

    3. Media sequence numbers MUST be aligned across all variant streams (quality levels), so that media sequence numbers can be used to identify matching content.

    4. For live streams, media segments MUST remain available on the server for at least one target duration after the segment disappears from the playlist.

    5. Playlists MUST use sufficiently accurate segment durations to ensure that the sum of the #EXTINF durations of any contiguous group of segments is within one video frame duration of the actual duration.

    6. Playlists MUST provide at least 6 segments in live/linear streams.

    7. Discontinuities in timestamps, frame rate, encoding profiles, or audio/video parameters MAY occur between segments, but such discontinuities MUST be indicated using the #EXT-X-DISCONTINUITY tag.

    8. EXT-X-STREAM-INF tags MUST always provide CODECS and RESOLUTION attributes.

  4. Subtitles

    1. The app MUST support subtitles that conform to the Subtitles and Closed Captions section.

  5. DRM

    1. The decryption key MUST be directly downloadable via an HTTP or HTTPS URLs

    2. Note that with AES-128 encrypted HLS, segments are completely encrypted.

3.3.2.2 Restrictions for MPEG-DASH content

  • The media segment container format MUST be the ISO Base Media File Format (aka MP4).

  • All media segments MUST be independently decodable. Consequently, the first video frame in every segment that contains video MUST be an IDR frame.

  • Manifest URLs MAY include the MPD anchor, but MUST NOT use any other than the ‘t’ parameter ([3] section C.4)

  • The app MAY support multiple audio tracks associated with multiple Adaptation Sets defined in an MPD of MPEG-DASH.

  • Each audio track MUST be a separate media stream.

  • Support for the <SegmentList> element is NOT REQUIRED.

  • The app MAY support multiple Periods defined in an MPD of MPEG-DASH.

3.3.2.3 Restrictions for MSS content

  • All media segments MUST be independently decodable. Consequently, the first video frame in every segment that contains video MUST be an IDR frame.

  • For live streams that use FragmentLookahead, segments MUST remain available on the server for one DVRWindowLength after they disappear from the Manifest file.

...

3.3.5.3 Playready License Acquisition

  • The app MAY rely on automatic license acquisition, supporting the following:
    • License Acquisition URLs provided in the manifest
    • License Acquisition URL provided in the WebInitiator

...

3.3.8 CMAF multimedia format

Common Media Application Format (CMAF) [34] combines and constrains several MPEG specifications to define a multimedia format optimized for delivery of a single adaptive multimedia presentation to a variety of devices, using various adaptive streaming formats, broadcast, download, and storage methods. The device MUST support this standard.

For more information, refer to the Specification for Devices [1] section 3.6.4. “CMAF multimedia format”.

...

Version: 4.11

Date: 2018-02-22

View filenamevewd-certify-for-apps-PDF: Vewd Certify Devices 4.11-2018.pdfheight250

Apps Requirements 2017

Version: 4.10

Date: 2017-03-16

View filenamePDF: opera-tv-acpdcp-4.10.pdfheight250

Application Requirements 2017

Version: 4.9.0-r1

Date: 2016-11-04

View filenamePDF: opera-tv-acpdcp-4.9.0-r1.pdfheight250