Support for custom modes with 50 sample framesize
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I use OPUS for its very low coding delay. The delay at 100 sample framesize (at 48kHz) is already great, but I noticed that the OPUS custom interface allows to set an even smaller framesize of 50 samples.
However, when using a framesize of 50 samples, the codec fails to work properly (lots of distortion, and I don't think it is due to insufficient bitrate).
Thus my question, should a framesize of 50 samples work in principle? Or is 100 samples the minimum supported framesize and the option to select 50 with the OPUS custom interface is a bug?
Regards,
Steffen
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 with the OPUS custom interface and reproduce encoding with 50-sample and 100-sample framesizes at 48 kHz. Compare the resulting distortion and determine the intended minimum supported framesize; done means the support status is confirmed and the issue has a clear fix or rejection criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100