![]() In order to clearly separate the requirements of referenced specifications vs. "SHALL", "SHOULD" and "MAY") are used when this document defines a new requirement or further constrains a requirement from a referenced document. This document uses statements of fact when describing normative requirements defined in referenced specifications such as and. If a client implementer follows the client-oriented requirements described in this document, the client plays the content conforming to this document. If a service provider follows these requirements in a published DASH service, that service is likely to experience successful playback on a wide variety of clients and exhibit graceful degradation when a client does not support all features used by the service. ![]() Requirements in this document describe required service and client behaviors that DASH-IF considers interoperable: While alternative interpretations may be equally valid in terms of standards conformance, services and clients created following the guidelines defined in this document can be expected to exhibit highly interoperable behavior between different implementations.Īny identified bugs or missing features may be submitted through the DASH-IF issue tracker at. The guidelines provide support the implementation of conforming service offerings as well as the DASH client implementation. The guidelines are provided in order to address DASH-IF members' needs and industry best practices. The integration of different media codecs into DASH-based distribution is also defined. The specified features enable relevant use cases including on-demand and live services, ad insertion, content protection and subtitling. The scope of the DASH-IF InterOperability Points ( IOPs) defined in this document is to provide support interoperable services for high-quality video distribution based on MPEG-DASH and related standards. 15 Annex: Signaling Dolby Vision profiles and levels.14 Annex: Dolby Vision streams within ISO BMFF.12.8.4 License Acquisition URL XML Element Laurl.12.8.2.2 Key Hierarchy and CMAF Chunked Content.12.8.1.1 Periodic Re-Authorization Content Protections Constraints.12.8 Additional Constraints for Specific Use Cases.12.7 Client Interactions with DRM Systems.12.6 Mix ISOBMFF and MPD Content Protections Constraints.12.5.2 MPD Content Protections Constraints.12.5.1.2 ContentProtection Element for the UUID Scheme.12.5.1.1 ContentProtection Element for the mp4protection Scheme.12.5 DASH MPD Support for Common Encryption and DRM.12.4.2 ISOBMFF Content Protection Constraints.12.4 ISOBMFF Support for Common Encryption and DRM.11.19.1 Requirements for enhancement layer.11.16 MPEG-D Unified Speech and Audio Coding.11.10 Enhanced AC-3 (Dolby Digital Plus).11.8 CEA-608/708 Digital Television (DTV) Closed Captioning.11.4 Bitstream switching with H.264 and H.265.11.3 Decoder configuration with H.264 and H.265.10.11.9.3 Blackouts and alternative content.10.11.8.2 Cue interpretation by the packager. ![]() 10.11.8.1 Cue interpretation by the MPD generator.9.11.6.2 Service configuration for main live.9.11.6.1 Service configuration for simple live.9.11.6 Proposed service configuration and MPD generation logic.9.11.3 Media segment duration variations.9.11 Reliable and consistent-delay live service.9.10 Converting a live service to an on-demand service.9.6 Robust and seamless period transitions.9.5 Selecting the minimum update period.9.4 Safety margins in availability timing.9.3 Selecting the media segment duration.9.2 Selecting the suggested presentation delay.9.1 Selecting the time shift buffer size.8.1 Surviving transforming boxes and other adaptation middleboxes.6.8 Specifying initial position in presentation URL.6.7 Update signaling via in-band events.6.2 Preview thumbnails for seeking and navigation.5.3.4.3 Converting simple addressing to explicit addressing.5.3.4.2 Moving the period start point (simple addressing).5.3.4.1 Inaccuracy in media segment timing when using simple addressing.5.3.3.1 Moving the period start point (explicit addressing).5.3.2.1 Moving the period start point (indexed addressing).5.2.12.1 Offer content with imperfectly aligned tracks.5.2.10 Timing of stand-alone IMSC1 and WebVTT text files.5.2.9.5.2 Removing content from the MPD.5.2.9.1 Real time clock synchronization. ![]() 5.2.7.1 Media segment duration deviation.4.1 Relationship to the previous versions of this document.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |