OPUS 1.6.1 comsume more CPU than 1.5.2
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Description
We compared the CPU usage of Opus 1.6 and Opus 1.5(The compile options are exactly the same, and fixed-point is not used). When DRED is not enabled, we observed that the encoder CPU consumption in 1.6 increases by about 5%–10% compared to 1.5. The exact number depends on the platform performance—the lower the platform performance, the more noticeable the increase.
The figures I attached here show the cost time on a high-performance machine. I also broke down and measured the time spent in SILK and CELT separately. The results show a noticeable increase in CELT processing time. After checking the code, this appears to be introduced by tone detection. SILK also shows some overall CPU increase.
So my question is: is this CPU increase in 1.6 compared to 1.5 expected? What benefits does it bring—for example, improvements in speech quality or something else?
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
No source file or test is named. Start by reproducing the reported encoder CPU comparison between Opus 1.6 and 1.5 with matching compile options and DRED disabled, then isolate the CELT tone-detection and SILK changes; done means determining whether the increase is expected and documenting its measurable quality or feature benefit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100