Streams with a minimum coded frame width or height below 16 should have a maximum parameters level
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Page 643:
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
While ambiguous, it is likely "the tables above" refers to the second and third tables in this section, which exclude undefined levels, reserved levels, and maximum parameters.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the AV1 level-validation behavior against the requirements quoted from page 643, especially the references to the second and third tables. Determine how streams below the 16-pixel minimum dimensions should be handled and define the expected maximum-parameters-level result; the issue names no file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100