-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Click / pop / crackle sound on pitch changes after key reset #10450
Comments
Commented by: ubuntu-linux-user |
Commented by: daschuer Unfortunately the fix introduces the risk for an underflow due to the double amount of CPU which is worse because it affects all decks. I don't see a chance to fix this in a dot release. I am afraid this issue needs to be solved within soundtouch and rubberband. |
Commented by: ubuntu-linux-user According to #4030 (comment) this issue should be discussed upstream at |
Reported by: ubuntu-linux-user
Date: 2021-06-27T10:35:08Z
Status: Confirmed
Importance: High
Launchpad Issue: lp1933756
Attachments: [Demo sound to reproduce the problem (sine wave at 440Hz)](https://bugs.launchpad.net/bugs/1933756/+attachment/5507433/+files/Demo sound to reproduce the problem (sine wave at 440Hz))
Problem:
A click / pop / crackle sound is introduced whenever the key crosses the original key of the track on non-zero pitch.
Steps to reproduce the problem:
Effect: Whenever the slider crosses p, a click / pop / crackle sound is introduced.
This behavior is particularly problematic in combination with vinyl control: an analog record introduces a continuous pitch variance of a few 0.0x% (at least on my machine). When the key is reset, this leads to heavy click noise, because the pitch continuously goes below and above p.
The problem does not occur when pitch is set to zero.
The problem is independent of the Pitch-Bend-Engine, it occurs with Soundtouch as well as with Rubberband. It occurs on a Windows notebook and a Linux desktop machine with different hardware, so I guess it is not a driver issue.
Environment:
The text was updated successfully, but these errors were encountered: