Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmff and cmfs assumptions in section 4 #27

Open
sdp198 opened this issue Aug 14, 2020 · 2 comments
Open

cmff and cmfs assumptions in section 4 #27

sdp198 opened this issue Aug 14, 2020 · 2 comments
Labels
last-chance-for-comment Last call for comments, if no comments, will be implemented or closed

Comments

@sdp198
Copy link

sdp198 commented Aug 14, 2020

Towards the end of section 4 there is this text:
If the Segment Type Box(styp)is present and contains:

  • 'cmff': an CMAF media segment as defined in this specification mustconform to a CMAF Fragment (as defined in CMAF Spec)
  • 'cmfs': an CMAF media segment as defined in this specification mustconform to a CMAF Segment (as defined in CMAF Spec)

These statements aren't necessarily correct. Those brands can be used on the first chunk of a CMAF Fragment and first chunk of a CMAF Segment respectively.

As the "CMAF Byte Stream Media Segment " is defined in this document to be a single CMAF Chunk then a CMAF Segment or CMAF Fragment consisting of multiple CMAF Chunks will necessarily be multiple CMAF Byte Stream Media Segments for the purposes of this spec. If those brands are applied in the manner permitted by CMAF then the "must" here will not be satisfied.

I think this text can be safely removed, as the user agent does not need to know about Fragment or Segment boundaries. However if it is desired to say something then two things are needed:

  • To indicate that the brand indicates the start of a series of one or more "CMAF Byte Stream Media Segment"s which conform to the requirements of a CMAF Fragment/Segment
  • The wording "CMAF media segment as defined in this specification" needs to be changed to "CMAF Byte Stream Media Segment" since taht is actually what is defined in this specification.
@haudiobe haudiobe added the Public-Review Comment Provided during Public Review label Oct 5, 2020
@haudiobe
Copy link
Member

AHG 2020/11/19: Propose to remove - agreed.

@haudiobe haudiobe added the last-chance-for-comment Last call for comments, if no comments, will be implemented or closed label Nov 19, 2020
@haudiobe haudiobe removed the Public-Review Comment Provided during Public Review label Dec 7, 2020
@haudiobe
Copy link
Member

haudiobe commented Dec 7, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
last-chance-for-comment Last call for comments, if no comments, will be implemented or closed
Projects
None yet
Development

No branches or pull requests

2 participants