-
-
Notifications
You must be signed in to change notification settings - Fork 23
Maximize master volume #46
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
base: main
Are you sure you want to change the base?
Conversation
|
Will look into it in upcoming days, thanks! |
|
Thanks for PR, looks great! Here are my thoughts:
|
|
Forgot to mention, assuming mono or stereo is not great because we allow to specify arbitrary channel count in CLI and mostly are not bound to number of channels. |
|
Okay, will take a look at implementing these changes. |
|
Thanks! FYI: c5ea5ac |
d08881c to
ab00726
Compare
|
Update: since we now have separate options for output and input devices (--out-latency/--in-latency, --out-periods/--in-periods), I think it makes sense to make separate options for volume too. E.g. we can have three options: --out-volume, --in-volume, --no-volume. |
a995b02 to
a77819f
Compare
Implementing #10
When AlsaWriter::open() is run a call to a volume setting function is made. Storing the previous state of the mixer element volume is nontrivial because it can have 9 different channels shown here. I see two options. One option is to assume that there is only mono or stereo. The other would be to store values in a container by getting the channels present. Do you think this is worth pursuing?