Add optional framerate or max_framerate to VideoDecoderConfig
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Codecs typically have level constraint related to maximum luma samples/ macroblocks per-second. As such, for isConfigSupported(VideoDecoderConfig config), if level is part of the codec string in config, the maximum possible framerate should be specified in config, which the agent will use in combination of resolution, and the level info in codec string, to decide if the decoder could safely claim support of current codec/profile/level.
The framerate is currently missing from the VideoDecoderConfig. It should be added as optional to facilitate isConfigSupported(). It is encouraged for application to specify the framerate on decoder creation as well, to avoid the agent decoding at an extremely high FPS that exhausts resources.
Contributor guide
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 with the VideoDecoderConfig definition and the isConfigSupported() processing described in the issue. Determine how an optional framerate or max_framerate field should interact with resolution and codec level information. Done means the configuration can carry this limit and support checking can use it to assess decoder capability; no files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100