-
Notifications
You must be signed in to change notification settings - Fork 178
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
volume in GUI doesn't match CLI #3089
Comments
Why do you need it to be the same? And which one (in your opinion) is the truth? I think they're just rounded differently. |
No need. Thought you may want to know since it's misleading when you set it to x via CLI and y shows up in the GUI. My intent was lowering the volume evenly over time. No opinion. Thanks to support of fb2k's RG I rarely touch volume. Side note: Identical RG scanning in db would be great, so we don't have to use fb2k. Currently it gives different values which ruins the purpose of RG. fb2k also has other useful RG scanning features. Given the nature of audio perception, the cubic one might be most true. But one could argue linear is signal reality. Not many programs even provide the choice. For my goal cubic is most useful, but it's probably hard to tell the difference in practice unless you sit there with a stopwatch. |
Steps to reproduce the problem
Look at the volume in the GUI and compare with the CLI:
GUI gives these three:
-8dB
linear 38%
cubic 72%
deadbeef --volume
gives83% (-8.50 dB)
Noticed while building a script that sets the volume.
What's going on? Describe the problem in as much detail as possible.
Information about the software:
Deadbeef version: 1.9.6
OS: Linux 6.8.8
The text was updated successfully, but these errors were encountered: