VAD
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Description
After evaluating a few VADs I could find, the one included in this project is far superior to the others. A lot of projects are using the VAD from Google’s WebRTC.
To evaluate your VAD, I built opusenc and logged the results similarly to what’s commented out here:
https://github.com/xiph/opus/blob/cdaf661e8d3e85770bf06db8cff12ae6be7fa2a6/src/analysis.c#L938
After reading through the code a couple of times, several questions arose:
- Why are all samples resampled to a sample rate of 48 kHz?
- Could we work together to decouple the VAD/music detection to a greater extent than it is now?
The latter would be very helpful in using the VAD independently of Opus.
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 by reading src/analysis.c around the commented logging code near line 938 and compare it with the linked Google WebRTC VAD. Investigate why processing uses 48 kHz and how VAD and music detection are currently coupled. The issue does not define an implementation target or acceptance criteria, so completion would require agreeing on the decoupling design first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100