#asahi · 2025-09-15 16:30
Meleodyno firefox is running at 48000hz, everything is looking at pw-top#asahi · 2025-09-15 16:23
chadmedfirefox will do that for example iirc#asahi · 2025-09-15 16:23
chadmedis some application opening the graph at 44.1?#asahi · 2025-09-15 16:20
Meleodyalso the highest common sample rate would be 48000hz in my config not 44100hz...#asahi · 2025-09-15 16:18
Meleody66207hz is the highest sample rate in the graph, but it certainly isn't shared with other applications or a common one#asahi · 2025-09-15 16:17
MeleodyI know, I just want avoid resampling twice, because I manually route the input in my DAW where it gets properly resampled. And I thought it was strange that it accepted 66207hz but not 33103hz, but thanks for the reply :)#asahi · 2025-09-15 16:15
chadmedthat besides, the audio amps only support 44.1 and 48 anyway so no matter what you do something at 33.103 is going to get resampled somewhere in the chain#asahi · 2025-09-15 16:14
chadmedits nothing to do with the dsp config #asahi · 2025-09-15 16:13
chadmedthe issue is that pipewire will force the _entire_ graph to the highest common sample rate, you cant have multiple things using multiple sample rates afaik#asahi · 2025-09-15 16:13
chadmedMeleody: i saw the issue, sorry im travelling at the moment#asahi · 2025-09-15 16:08
Meleodyhi everyone, I have a small issue with pipewire upsampling an application requesting a 33103hz sample rate to 44100hz (prior to outputting to speaker), if anybody has a quick fix I'd appreciate it: https://github.com/AsahiLinux/asahi-audio/issues/76#asahi · 2025-09-15 15:46
chadmedno idea whats causing it, havent had time to do any debugging#asahi · 2025-09-15 15:46
chadmedSeti_: chaos_princess: the 100% volume thing is some race or something introduced in a wp or pw update a few versions ago #asahi · 2025-09-15 13:49
maettu102as a workaround#asahi · 2025-09-15 13:49
maettu102dd if=/dev/zero bs=1024 count=1 2>/dev/null | paplay --format=s16le --rate=48000 --channels=2 --raw#asahi · 2025-09-15 13:49
maettu102just append this to your ~/.zshrc or ~/.bashrc or whatever you use#asahi · 2025-09-15 09:35
Seti_neither does wpctl set-volume @DEFAULT_SINK@ 10%+#asahi · 2025-09-15 09:35
chaos_princesswell, i tried :P#asahi · 2025-09-15 09:34
Seti_chaos_princess: wpctl get-volume @DEFAULT_SINK@ returns volume 1.00 and running wpctl set-volume @DEFAULT_SINK@ 10%- doesnt change it#asahi · 2025-09-15 09:26
chaos_princessjust to check, try running `wpctl set-volume @DEFAULT_SINK@ 10%+`#asahi · 2025-09-15 09:23
chaos_princesswell, turns out that was wrong#asahi · 2025-09-15 09:23
Seti_chaos_princess: ok so the sound control isnt working after reboot, but i still see all three running and when i press mute (which has no effect) i still see them shoot up in htop#asahi · 2025-09-15 09:18
Seti_I can see pipewire, wireplumber, pipewire-pulse shooting up in htop when i press mute (currently everything working) I'll try after a reboot now#asahi · 2025-09-15 09:17
chaos_princessso, check all three#asahi · 2025-09-15 09:17
Seti_pulse-audio control#asahi · 2025-09-15 09:17
Seti_I think so#asahi · 2025-09-15 09:16
chaos_princesspactl is the pulse thing, right?#asahi · 2025-09-15 09:16
chaos_princesspipewire, wireplumber, pipewire-pulse #asahi · 2025-09-15 09:15
Seti_chaos_princess: what should i look for? pipewire? wireplumber?#asahi · 2025-09-15 09:14
chaos_princesstry rebooting, run htop and see if all the various sound processes are running#asahi · 2025-09-15 09:14
Seti_gahdamn#asahi · 2025-09-15 09:13
chaos_princessi think this is default on systemd#asahi · 2025-09-15 09:13
Seti_at least not knowingly#asahi · 2025-09-15 09:13
Seti_sounds reasonable but i havent tweaked anything like that afaik #asahi · 2025-09-15 09:13
chaos_princessis there a chance that you have socket activation, and the server hasn't started yet#asahi · 2025-09-15 09:12
Seti_chaos_princess: from reboot#asahi · 2025-09-15 09:12
LarstiQKinda maybe similar for me. I turn the speakers off compeltely but they're back on after reboot.#asahi · 2025-09-15 09:12
chaos_princessis it from reboot, or from running system?#asahi · 2025-09-15 09:11
jbeyup#asahi · 2025-09-15 09:11
Seti_seems to be the same thing that they are reporting on the issue, sound control works as soon as something with sound is played#asahi · 2025-09-15 09:10
j`eyoh#asahi · 2025-09-15 09:10
Seti_j`ey: i opened a video in firefox with sound and now everything is working again #asahi · 2025-09-15 09:10
jbeyeah, back to 100% after boot#asahi · 2025-09-15 09:08
Seti_and there they reported that the volume control returned once something that played sound was ran on their computer#asahi · 2025-09-15 09:08
Seti_aha, so i saw this issue on the asahi-audio page https://github.com/AsahiLinux/asahi-audio/issues/73#asahi · 2025-09-15 09:06
Seti_would explain why brightness control is fine since its not pactl control, so not a hw issue or sway issue#asahi · 2025-09-15 09:05
Seti_same story if i do for setting mute, seems like it is a pactl issue and not sway#asahi · 2025-09-15 09:03
Seti_j`ey: pactl get-sink-volume @DEFAULT_SINK@ is unchanged after running pactl set-sink-volume \@DEFAULT_SINK@ -5%#asahi · 2025-09-15 09:01
j`eycan you run those commmands in a terminal to make sure theyre working there#asahi · 2025-09-15 09:00
Seti_it was working fine before