search

Dash-Industry-Forum / Guidelines-TimingModel

DASH-IF implementation guidelines: the DASH timing model
9 stars 1 forks source link

5.1. CMAF and ISO BMFF #14

Closed irajs closed 4 years ago

irajs commented 5 years ago

This section can be removed.

The SHALL statement should be moved to Media Segment section, under CMAF compatibility.

That section can start with: Media Segments SHALL be compliant to [MPEGCMAF] clauses 7-11.

Consequently: (all the other current SHALL statements goes here as statement of fact).

haudiobe commented 5 years ago

I agree in principle, but we need to be very clear what we mean by "Media Segments SHALL be compliant to [MPEGCMAF] clauses 7-11"? It is not correct. We need to be clear where the interop point is. We had been very clear and careful in the ad insertion context. I propose we align with ad insertion doc.

haudiobe commented 5 years ago

(v5 editing: 08/07/2019) Suggestion to reference DASH Profile for CMAF.

irajs commented 5 years ago

Implemented as:

CMAF and ISO BMFF Requirements## {#cmaf-bmff-constraints}

Media segments SHALL be compliant to [[MPEGDASHCMAFPROFILE]].

Note: [[MPEGDASHCMAFPROFILE]] defines the media segment format using [[!MPEGCMAF]], which is largely based on [[!ISOBMFF]].

sandersaares commented 4 years ago

Closing as this has been addressed in August.