[FEATURE] Alternative oversampling algorithms (low latency vs. low alias)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- audio-video-rtc
Research direction
Start by locating the current low-latency oversampling path and reproduce the issue with a 48 kHz input captured at 192 kHz. Compare its sine-sweep spectrogram with the Reaper reference shown in the issue. Done means providing a selectable alternative oversampling algorithm that reduces the folded-back aliasing while preserving the existing low-latency option.
Written by the indexing model from the issue text.
Description
Problem
The plugin now oversamples if the input signal is e.g., 48kHz and the capture is e.g., 192kHz. I appreciate that the oversampling algorithm was chosen to be the one with lowest latency, but the problem is that the current low-latency oversampling creates quite a lot of aliasing when compared e.g., to effect instance oversampling in Reaper. There seems to be a lot of spectral components over the nyquist limit (e.g., in case of 48kHz signal, the oversampling algorithm should not produce components that are over 24 kHz). As shown in the attached spectrogram, those components get folded back (aliased) to the produced output.
Proposed solution
As an alternative (maybe user selectable), use an improved oversampling algorithm that does not produce higher frequency components that then get aliased back.
Additional context
Sine sweep spectrogram, on top using Reaper's per plugin oversampling, below using NeuralAmpModeler oversampling.
- Dominant language
- C++
- Stars
- 71
- Forks
- 32
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 2
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.
More from sdatkinson/AudioDSPTools
-
Rework testing Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Namespaces Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in sdatkinson/AudioDSPTools
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·