Closed Venator777 closed 2 years ago
Thanks for reporting this! I’m going to try to reproduce and see if this is alsa-specific.
A couple questions if you don’t mind:
default.audio.sink
from pw-dump
when firefox is playing audio? I’m surprised it’s not visible.{ "subject": 0, "key": "default.audio.sink", "type": "Spa:String:JSON", "value": { "name": "alsa_output.pci-0000_10_00.4.analog-stereo" } },
https://github.com/smasher164/pw-volume/releases
Wait that's perfect then. Since, I'm using pw-cli under the hood, we can probably figure out where the discrepancy is.
That's definitely weird, since pw-volume literally just calls pw-dump and grabs that field. Maybe there's some false assumption about the output of pw-dump I'm making?
Ok so the issue occurs on both versions. I just double checked and pw-cli does work when volume is playing, if it helps the exact command I use is:
pw-cli s 41 Props '{ mute: false, channelVolumes: [ x.xxx, x.xxx ] }'
Just so you know, I haven't forgotten about this. I just recently joined a new job, and it'll take some time before I can wind down and attend to this. Hope you can understand!
If you're able to run the main
branch, please let me know if it fixes your issue.
Thanks!
Just built, yes this fixed the issue, thanks a lot!
Everything works as expected when no audio is playing. However, if I for example have firefox open with any audio playing, any attempt to run it results in this message:
In the case of Firefox, stopping the audio does not help, Firefox has to be fully closed before it starts working again. In the case of some other programs, as long as the audio is not playing, I can still change the volume.
I also noticed that the volume is really loud, a 'normal' volume level would be at around 0.5% but I think this is something with my alsa setup and not related to the issue.