-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
ao_pipewire: fix ao-volume #9830
Conversation
@t-8ch can you take a look please. |
@pkunk What issue does it fix? That should be part of the commit message. I assume that the call to |
Updated the commit message. |
Thanks! I'm curious about the incorrect scaling. Because this worked for me (and presumably the other testers). Muting will also be affected for some users. The trailing |
Just to be 100% sure. Did you tested
Ah yes, I have added |
Yes.
I can also see the volume in pavucontrol matching exactly the values in mpv. |
Yes, just tested, you right. Seems fix for On unrelated note, just tested 5.1 and ao-volume basically nonfunctional here, just resets everything to 0. |
Pass channel volumes to `pw_stream_set_control` as array. This is correct calling conventions and prevents right channel muting every time ao-volume property is changed. Terminate `pw_stream_set_control` calls with 0.
Thanks for testing!
I don't have anything against the cosmetic changes. It's up to the mpv maintainers.
As for 5.1, if you have the setup to test it, any contribution would be appreciated!
Feb 5, 2022 12:40:59 Alex B ***@***.***>:
… Yes, just tested, you right. Seems fix for *pw_stream_set_control()* is enough.
I'll remove my changes for scaling. I personally still prefer them, but they are not related to the problem.
On unrelated note, just tested 5.1 and ao-volume basically nonfunctional here, just resets everything to 0.
—
Reply to this email directly, view it on GitHub[#9830 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAFPITJPQ3O4QM5IWLVTLTLUZUEEVANCNFSM5NSZ73VQ].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].
You are receiving this because you were mentioned. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Tracking image][https://github.com/notifications/beacon/AAFPITNINRY4UEZL5GV3FJDUZUEEVA5CNFSM5NSZ73V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHVW42PQ.gif]
|
This is now ready to merge from my PoV. |
LGTM. |
Thanks! |
It seems to break if media file is using more than 2 channels. It can be worked around by passing |
Store volume only in mpv format, convert it from spa a soon as possible.
Pass volumes to
pw_stream_set_control
as array.