Repository navigation
Conversation
Reference LOCMAF (draft-einarsson-moq-locmaf-01) as a new packaging option rather than folding it into CMSF (per moq-wg#24 and the London interim): - add LOCMAF as a normative reference - add a short LOCMAF Packaging section registering the "locmaf" packaging value (Table 3) and a mandatory-when-locmaf "locmafVersion" track field ("major.minor", e.g. "0.3") - LOCMAF reuses CMSF init (initRef), switching/Group/Object rules, and DRM (contentProtectionRefIDs) unchanged; only the Object-payload encoding differs, specified entirely in [LOCMAF]
wilaw
reviewed
Jul 8, 2026
| a "packaging" type value of "locmaf". | ||
|
|
||
| ### LOCMAF version {#locmafversion} | ||
| Location: T Required: Conditional JSON Type: String |
Collaborator
There was a problem hiding this comment.
Suggested change
| Location: T Required: Conditional JSON Type: String | |
| Required: Conditional JSON Type: String Location: Track Object |
Contributor
Author
There was a problem hiding this comment.
Your suggested format aligns with MSF, but not with what is used in this CMSF draft:
#### Max Object SAP starting type {#maxobjsapstartingtype}
Location: T Required: Optional JSON Type: Number
### Content Protections {#contentprotections}
Location: R Required: Optional JSON Type: Array
...
However Locations: T, R, CP, DS are not defined as far as I can see.
It is probably a good idea to adopt the same format as MSF for all values, but I keep this for now.
Made a better catalog example combining cmaf and locmaf, and showing the great benefit for audio.
|
Any update? |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per the London interim, LOCMAF should be added as a packaging in CMSF.
Since LOCMAF is not deeply tied to CMSF, @wilaw in moq-wg/msf#24 suggested adding a reference to a standalone draft draft-einarsson-moq-locmaf-01 rather than the full format being folded into CMSF. This also has the advantage that one draft can be updated without the other.
This PR references LOCMAF as a new packaging option in CMSF and defines how it is signaled.
locmafVersiontrack field ("major.minor", e.g. "0.3").Fixes: #24
Fixes: #28