value of optimizeForLatency in emitted decoder configuration
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
It seems odd that the value of optimizeForLatency in the decoder configuration spit out by the encoder does not reflect the value of latencyMode set in the encoder configuration.
In the encode-decode sample, I had expected (but not checked) that setting latencyMode: "realtime" in the encoder config would result in optimizeForLatency: true in the decoder config. Because the decoder config didn't automatically set optimizeForLatency: true, the measured decoder latencies for VP8 and AV1 were considerably higher (~ 100 ms) than expected (and higher than the encoder latencies).
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 encode-decode sample and inspect how latencyMode and optimizeForLatency are represented in the encoder and emitted decoder configurations. Compare the VP8 and AV1 latency measurements, then determine the expected relationship and document or test the behavior so the configuration and measured latency are consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100