-
Notifications
You must be signed in to change notification settings - Fork 22
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
porting the dithering function from kaldi #40
Conversation
1a60898
to
1c96f64
Compare
okay, I added the missing part, the local build including the test binaries was okay... |
the failed there is a |
- 1.0 is too much, and would break the systems
for me it is ready, i just changed the default dithering constant k2 uses audio samples [-1..+1] |
Thanks! Will check it tomorrow morning. |
Thank you for your contribution! |
Hey, can we please change dither constant to be 1.0 like it was before. 0.00003 vs 1.0 can cause a lot of confusion in existing code. |
Could you create a PR to change it to 1.0? |
The problem is, that in some situations 1.0 is the correct value (for +/- 32k audio signal), while in other situation 0.00003 is the correct value (+/- 1.0 audio signal range), and both options are possible use-cases. So there will be confusion either on one or the other side. And the detection cannot be 100% reliable, as there can be an input signal with hard zero's in it. So it is better to document it, and give a hint to the users. But, it is true that if default is 1.0, being internally divided into 0.00003. And, occasionally it is used with +/-32k input singal, it will effectively disable the dithering. While as it is now, using 1.0 will break the system with +/-1.0 audio signal. So, changing the default to 1.0 is a safer way... |
Let it stay then, sorry for confusion and thanks for the patch. |
No description provided.