Page tree

Versions Compared

Key

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

...

Devices MUST support rendering of subtitles and closed captions as specified in HTML 5.1, "The track element" (4.7.13). Supported track formats are specified in the  Subtitles and Closed Captioning section.

...

  • H.264 as specified in [20]

    • The device MUST support all profile/level configurations up to High Profile Level 4.1 included.

  • H.265 as specified in [19] (CONDITIONALLY REQUIRED)

    • H.265/HEVC MUST be supported when the codec is available on the device

    • The device MUST support all profile/level configurations up to High Profile Level 4.1 included.

    • HEVC Main Level 5 and 5.1 (CONDITIONALLY REQUIRED)

      • These two levels MUST be supported when the device supports Ultra HD/4K resolution (2160p)

    • HEVC Main 10 Level 4.1 and 5.1 (CONDITIONALLY REQUIRED)

      • These two levels MUST be supported when the device supports HDR, either HDR10 or HLG10

      • It is ONLY required in the case of MPEG-DASH streaming use-case
  • VP9 as specified in [22] (CONDITIONALLY REQUIRED)

    • VP9 MUST be supported when the codec is available on the device

    • Profile 0 (CONDITIONALLY REQUIRED)

      • When device supports VP9 then VP9 profile 0 MUST be supported

      • The following VP9 levels MUST be supported (described in [18]): 1, 1.1, 2.1, 3, 3.1, 4, 4.1

      • When the device supports video in Ultra HD/4K resolution (2160p) then it MUST support the VP9 levels (described in [18]): 5, 5.1

    • Profile 2 (CONDITIONALLY REQUIRED)

      • When the device supports HDR, either HDR10 or HLG10, then VP9 profile 2 MUST be supported

      • The device MUST support the VP9 levels (described in [18]): 1, 1.1, 2.1, 3, 3.1, 4, 4.1

      • When the device supports video in Ultra HD/4K resolution (2160p), it MUST support the VP9 levels (described in [18]): 5, 5.1

  • AV1 as specified in [21] (CONDITIONALLY  REQUIREDREQUIRED)

    • AV1 MUST be supported when the codec is available on the device

    • Profile 0 (CONDITIONALLY REQUIRED)

    • When device supports AV1 then AV1 profile 0 (MAIN) MUST be supported.

    • The following AV1 levels MUST be supported (described in [21] ): 2.0, 2.1, 3.0, 3.1, 4.0, 4.1

...

 At any given time only one HTML media element can be playing. The other element intended for dynamic insertion should be explicitly hidden using CSS property and should start prefetching the media data. Once enough data has been loaded, the second media element should appear and play whereas the first one should be hidden and paused. The delay between the end of the presentation of an HTML5 media element and starting presentation of another HTML5 media element is RECOMMENDED to be less than 250 ms. This time requirement is applicable if the first media element refers to either MPEG DASH content or ISOBMFF (MP4) content and the second media element refers to either MPEG DASH content or ISOBMFF (MP4) content.  Advert Advert insertion SHOULD work with two encrypted streams; the 250ms performance, however, is required only in cases of one encrypted stream and one unencrypted stream or two unencrypted streams. The transition between two video streams, one playing, and one preloaded, for any other content than aforementioned, SHOULD be seamless (within 2s).

...

Anchor
1
1
 [1] HLS, HTTP Live Streaming, RFC 8216 August 2017 https://tools.ietf.org/html/rfc8216

Anchor
2
2
[2] Smooth Streaming Protocol :- https://msdn.microsoft.com/en-us/library/ff469518.aspx

...

Anchor
4
4
[4] DVB MPEG-DASH Profile for Transport of ISO BMFF :- https://www.dvb.org/resources/public/standards/a168_dvb-dash.pdf

Anchor
5
5
[5] DASH-IF Guidelines for Implementation - Interoperability Points v3.2 :- http://dashif.org/wp-content/uploads/2015/12/DASH-IF-IOP-v3.2.pdf

Anchor
6
6
[6] Encrypted Media Extensions - W3C Candidate Recommendation 05 July 2016 2016 - https://www.w3.org/TR/2016/CR-encrypted-media-20160705

Anchor
7
7
[7] Media Source Extensions - W3C Candidate Recommendation 05 July 2016 2016 - https://www.w3.org/TR/2016/CR-media-source-20160705

Anchor
8
8
[8] PlayReady documents documents - https://www.microsoft.com/playready/documents/

Anchor
9
9
[9] HTML 5.1 W3C Working Draft, 2 June 2016 :- https://www.w3.org/TR/html51/

Anchor
10
10
[10] "cenc" DRM Initialization Data Format Format - https://www.w3.org/TR/eme-initdata-cenc/

Anchor
11
11
[11] "webm" DRM Initialization Data Format Format - https://www.w3.org/TR/eme-initdata-webm/

Anchor
12
12
[12] "keyids" DRM Initialization Data Format Format - https://www.w3.org/TR/eme-initdata-keyids/

Anchor
13
13
[13] Protected Interoperable File Format Format - http://www.iis.net/learn/media/smooth-streaming/protected-interoperable-file-format

Anchor
14
14
[14] Common Encryption Scheme Scheme - ISO/IEC 23001-7

Anchor
15
15
[15] Web Video Text Tracks Format (WebVTT) - https://w3c.github.io/webvtt/

Anchor
16
16
[16] TTML text track format format - https://www.w3.org/TR/ttml-imsc1/ 

Anchor
17
17
[17] EBU-TT-D text track format format - https://tech.ebu.ch/docs/tech/tech3380.pdf

Anchor
18
18
[18] Definition of video VP9 levels levels - http://www.webmproject.org/vp9/levels 

...

Anchor
20
20
[20] Advanced video coding for generic audiovisual services - International Telecommunication Union (ITU-T) Recommendation for h.264 - https://www.itu.int/rec/T-REC-H.264

Anchor
21
21
[21]  AV1 AV1 Bitstream & Decoding ProcessSpecification Process Specification - https://aomediacodec.github.io/av1-spec/av1-spec.pdf 

...

Anchor
31
31
[31] ETSI TS 102 796 V1.4.1 Hybrid Broadcast Broadband TV Technical Specification http://www.etsi.org/deliver/etsi_ts/102700_102799/102796/01.04.01_60/ts_102796v010401p.pdf

Anchor
32
32
[32] IETF RFC 5246 - https://tools.ietf.org/html/rfc5246

Anchor
33
33
[33] IETF RFC 5289 - https://tools.ietf.org/html/rfc5289

Anchor
34
34
[34] HbbTV 2.0.1 Specification with Errata #2 Integrated and Changes Marked https://www.hbbtv.org/wp-content/uploads/2018/02/HbbTV-SPEC20-00061-000-HbbTV_201_with_errata_2_integrated.pdf

Anchor
35
35
[35] Accessible Rich Internet Applications (WAI-ARIA) 1.1 - https://www.w3.org/TR/wai-aria/

...

Specification for Devices 2018

Version: 4.11

Date: 2017-09-15

View file
nameVewd Certify Devices 4.11.pdf
height250

Specification for Devices 2017

Version: 4.10

Date: 2017-03-16

View file
nameVewd Certify Devices 4.10.pdf
height250

Specification for Devices 2017

Version: 4.9.0-r1

Date:   20162016-11-01

View file
nameVewd Certify Devices 4.9.0-r1.pdf
height250