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

Level bitstream conformance requirement conditions are ambiguous #314

Open
rzumer opened this issue Sep 18, 2020 · 1 comment
Open

Level bitstream conformance requirement conditions are ambiguous #314

rzumer opened this issue Sep 18, 2020 · 1 comment

Comments

@rzumer
Copy link

rzumer commented Sep 18, 2020

It is specified at section A.3, page 643, that:

When the mapped level is contained in the tables above, it is a requirement of bitstream conformance that the following constraints hold:
(...)

  • FrameWidth is greater than or equal to 16
  • FrameHeight is greater than or equal to 16

Firstly, the wording of the first sentence is ambiguous, because some tables include undefined levels, reserved levels and maximum parameters. It is not clear whether the conformance requirements apply only to levels <= 6.3, or to all levels in the first table. I propose rewording the sentence to clarify which levels the list of requirements apply to.

Secondly, the frame size requirements are inconsistent with the reference encoder behavior. aomenc will encode frames below this size and set a level <= 6.3. See this comment for a sample. I assume that this is a bug in aomenc rather than a spec issue, but would like a confirmation.

@rzumer rzumer changed the title 16x16 minimum frame size requirement conditions are ambiguous Level bitstream conformance requirement conditions are ambiguous Sep 18, 2020
@xzhaao
Copy link

xzhaao commented Oct 5, 2020

For the first issue, "in the tables above" is indeed ambiguous. Maybe labels and captions should be added for tables to avoid such ambiguity when tables are being referenced in the spec, but it require a lot of changes. For this specific issue, clarifying the relevant levels sounds good enough.

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

No branches or pull requests

2 participants