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

Fix #765, Profile clarification regarding channels #785

Merged
merged 3 commits into from
May 13, 2024
Merged

Conversation

sunghee-hwang
Copy link
Collaborator

@sunghee-hwang sunghee-hwang commented Nov 23, 2023

index.bs Outdated
@@ -1830,6 +1830,7 @@ Common restrictions on the [=IA Sequence=] for all profiles specified in this ve
NOTE: This behavior is to allow future versions of this specification to define new profiles that support a number of audio elements and/or a number of sub-mixes greater than those recommended in this profile, while still permitting streams compliant with these new profiles to be processed by parsers compliant with the profiles defined in this version of the specification.

- When [=num_layers=] = 1, [=DemixingParamDefinition()=] for demixing MAY be present in the [=Audio Element OBU=] and IA decoders MAY use [=demixing_info_parameter_data=] or [=default_demixing_info_parameter_data=] for (dynamic) down-mixing.
- The limit on the number of channels, which a profile SHALL be able to handle, applies to the sum of channels across all [=Audio Element=]s in a [=Mix Presentation=] before mixing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use of "SHALL" for a profile is strange to me. I would simply say "which profiles MAY define"

index.bs Outdated Show resolved Hide resolved
@sunghee-hwang sunghee-hwang merged commit 0e0d2c0 into main May 13, 2024
@sunghee-hwang sunghee-hwang deleted the issue_765 branch May 13, 2024 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants