VideoDecoder bit exactness
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
As far as I can tell, the spec today makes no explicit mention about bit-exactness of the output from a VideoDecoder.
A decoder by definition needs to have a bit-exact representation of the reconstructed state in each reference buffer, otherwise there will be video corruption in the form of prediction drift. However, some decoders may perform additional processing on a copy of the reconstructed state, before handing the frame to the user. The post-processing could be in the form of e.g. deblock or debanding algorithms, sharping/superres filters etc etc
I think it would be prudent to:
(1) Add spec language to indicate that the expected output of a decoder instance should be the bit-exact exact form.
(2) Add a field in VideoDecoderConfig that allows post processing to be turned on if supported.
With (1) it becomes trivial to create qualification tests as you can just use a hash the known output for each frame.
With (2) we optionally allow further enhancements to be applied, but only when desired.
It's debatable if (2) should just be an on/off toggle, or if something more fine grained is needed (e.g. a post processing "strength" slider, or even toggles for each kind of available filter).
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 WebCodecs specification's VideoDecoder and VideoDecoderConfig definitions and review the existing issue discussion. Resolve whether decoded output must be bit-exact and how optional post-processing should be controlled, then update the spec and add the hash-based qualification coverage described in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100