DVB DASH Validation

Validator implements checks to assert conformance to TS 103 285 DVB DASH.

DVB-DASH suite tests some of the subclauses in DVB-DASH ETSI TS 103 285.

The test includes ignores, which are strictly speaking not conformance violations.

However, the ignore implies that inserted syntax may be ignored by players, or elements with certain syntax may be ignored.

Because of this reason, investigating ignore information is recommended.

Ignore clause 4.2.2.

The Subset element may be ignored

Must Fix clause 4.2.2.

The Period.SegmentList element shall not be present

Must Fix clause 4.2.2

If a Period element contains multiple Adaptation Sets with @contentType=”video” then at least one “Adaptation Set shall contain a Role element with @schemeIdUri=””urn:mpeg:dash:role:2011”” and @value=””main””.”

Ignore clause 4.2.4

The @group attribute may be ignored

Ignore clause 4.2.4

Any Adaptation Set without an @contentType attribute may be ignored

Ignore 4.2.4

Adaptation Sets which contain BaseURL elements with Absolute BaseURLs may be ignored

Ignore 4.2.4

Any AdaptationSet with a ContentComponent element may be ignored

Ignore 4.2.5

Representations with a value of the @mimeType attribute starting with a string other than “xxx/mp4” where xxx is one of “video”, “audio”, “application” or “text” may be ignored. Additional profile or codec specific parameters may be added to the end of the value of the @mimeType attribute.

Must Fix Clause 4.2.6

The Period.SegmentTemplate element shall not be present.

Ignore Clause 4.2.7

The @group attribute may be ignored

Ignore Clause 4.2.7

Any AdaptationSet without an @contentType attribute may be ignored

Ignore clause 4.2.7

Any AdaptationSet with a ContentComponent element may be ignored.

Ignore Clause 4.2.8

Representations with a value of the @mimeType attribute starting w ith a string other than “xxx/mp4” where xxx is one of “video”, “audio”, “application” or “text” may be ignored. Additional profile or codec specific parameters may be added to the end of the value of the @mimeType attribute.

Ignore clause Representation.SegmentList

If either the Representation.SegmentList or the Representation.SegmentTemplate element is present in a Representation element then this Representation element may be ignored.

Ignore clause 4.2.8

If the Representation element does not contain a BaseURL element then this Representation element may be ignored

Should Fix clause 4.4.

For any Adaptation Sets with @contentType=”video” the following attributes should be present: - @maxWidth (or @width if all Representations have the same width) DVB BlueBook A168r6 (October 2022) 23 - @maxHeight (or @height if all Representations have the same height) - @maxFrameRate (or @frameRate if all Representations have the same frame rate) - @par (Picture Aspect Ratio)

Must Fix Clause 4.4.

For any Representation within an Adaptation Set with @contentType=”video” the following attributes shall be present: - @width, if not present in the AdaptationSet element - @height, if not present in the AdaptationSet element - @frameRate, if not present in the AdaptationSet element - @scanType, if interlaced pictures are used within any Representation in the Adaptation Set

Should Fix clause 4.4.

For any Representation within an Adaptation Set with @contentType=”video” the following attributes should be present or inherited from the Adaptation Set: @sar (Sample Aspect Ratio)

Should Fix Clause 4.7.2

The MPD should contain at least one UTCTiming element (as defined in ISO/IEC 23009-1 ) with the @schemeIdURI attribute set to one of the following: - urn:mpeg:dash:utc:ntp:2014 - urn:mpeg:dash:utc:http-head:2014 - urn:mpeg:dash:utc:http-xsdate:2014 - urn:mpeg:dash:utc:http-iso:2014 - urn:mpeg:dash:utc:http-ntp:2014

Should Fix clause 5.1.1

Encoded video may use additional luminance resolutions for adaptive streaming listed in Table 25 and Table 26

Should Fix clause 5.1.2

Segments shall start with SAP types 1 or 2 as described in ISO/IEC 14496-12.

Technically this is a must fix, but it was relaxed in the DVB-DASH suite

implementation to a should fix.

Must Fix clause 5.1.3

If present, the value of the @codecs attribute shall be set in accordance with IETF RFC 6381, clause 3.3

Must Fix clause 5.2.1

Players which support HEVC shall support both sample entries using ‘hvc1’ and ‘hev1’ (both storage for VPS/SPS/PPS within the initialization segment or inband within the media segment)

Must Fix clause 5.2.1

Segments shall start with SAP types 1 or 2 as described in ISO/IEC 14496-12 [6].Where ‘hev1’ sample entries are used, video segments should contain all SPS and PPS NALs referenced by a coded video sequence in the first access unit of that coded video sequence.

Must Fix clause 5.2.2

For representations in the scope of the DVB-DASH 2017 profile, these shall be signalled (@codecs).

Must Fix clause 5.2.2

If present, the value of the @codecs attribute shall be set in accordance with ISO/IEC 14496-15 [4], clause A.3.

Must Fix clause 5.2.3

Encoded video may use additional luminance resolutions for adaptive streaming listed in Table 25, Table 27 and 27a.

Must Fix clause 6.1.1

clause 6.2 and 6.3.1 codecs string for aac

Must Fix 8.4

Players shall be able to process ContentProtection descriptors from the MPD.

Players may ignore ContentProtection descriptors with @schemeIdUri attribute values that they do not understand. Any Adaptation Set containing protected content shall contain one “mp4protection” ContentProtection descriptor as described in ISO/IEC 23009-1 , clause 5.8.5.2 first bullet with the following values: @schemeIdUri = “urn:mpeg:dash:mp4protection:2011” @value = “cenc” or “cbcs” Furthermore, this “mp4protection” Content Protection descriptor should include the extension defined in ISO/IEC 23001-7 , clause 11.2: @default_KID attribute under the “urn:mpeg:cenc:2013” namespace. This reflects the default KID value found within the ISO BMFF ‘tenc’ box. Any Adaptation Set containing protected content shall also contain one Content Protection descriptor for each supported DRM. Those Content Protection descriptors may contain DRM specific data. These ContentProtection descriptors shall use the UUID urn in the @schemeIdUri attribute as defined in ISO/IEC 23009-1, clause 5.8.5.2, third bullet. If an AdaptationSet includes one or more ContentProtection elements that the Player recognizes as identifying both a DRM system and the use of the “cenc” encryption scheme then the Player shall not reject or ignore the AdaptationSet solely because it does not also include an “mp4protection” content protection descriptor