I can see the same issue, but this happens after resuming from suspend (not every time, though). Unloading/loading tunnel module helps in most cases (sometimes, though, only restart of pipewire service works)
I'm on pipewire-0.3.52 now, and I think, there is no such issue anymore. I'm closing this ticket for now, and will monitor it... I have other issue, I guess it's similar to #1881 (closed). To fix it, I have to unload/load tunnel module, and sometime even restart pipewire. Maybe this issue masks current one...
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment: 0.3.28, Gentoo, Sway
Description of Problem: I found that if I'm using PipeWire to pass data to remote pulse server, sound is cracking when I'm seeking through audio, or when there is no sound playing and notification sounds. I found in previous tickets recommendation to set node.pause-on-idle to false, I set it via sink_properties=node.pause-on-idle=false, but according to pw-mon, link is still achieving "paused" state
How Reproducible: 100%
Steps to Reproduce:
Actual Results: Sound is cracking
Expected Results: Sound is not cracking
Additional Info Eg. pw-dump -N > file
(As Attachment Please):
pw-dump
Just tried with master, and it works as expected -
update: id:0 key:'default.configured.audio.sink' value:'{ "name": "remote" }' type:'Spa:String:JSON'
update: id:0 key:'default.configured.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.sink' value:'{"name":"remote"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
after loading the module. Closing the ticket, sorry for the noise!
Hello! I have two sinks in PW - alsa_output.pci-0000_00_1f.3.analog-stereo and remote (which is result of pactl load-module module-tunnel-sink sink_name=remote server=myservername
). When I'm setting default sink to remote, sound is going to the tunnel, and metadata is set correctly:
update: id:0 key:'default.configured.audio.sink' value:'{ "name": "remote" }' type:'Spa:String:JSON'
update: id:0 key:'default.configured.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.sink' value:'{"name":"remote"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
When remote sink becomes unavailable, WP switches to alsa sink (which is expected), but it set it as default in metadata:
update: id:0 key:'default.configured.audio.sink' value:'{ "name": "remote" }' type:'Spa:String:JSON'
update: id:0 key:'default.configured.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.sink' value:'{"name":"alsa_output.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
When I'm loading the module again, WP is not switching it back to remote, even though default.configured.audio.sink
is still remote
My expectation was that WP should switch default.audio.sink
not only when previous default sink becomes unavailable, but also when it becomes available again (as it's explicit preference, made by user)
Hello! I have two sinks in PW - alsa_output.pci-0000_00_1f.3.analog-stereo and remote (which is result of pactl load-module module-tunnel-sink sink_name=remote server=myservername
). When I'm setting default sink to remote, sound is going to the tunnel, and metadata is set correctly:
update: id:0 key:'default.configured.audio.sink' value:'{ "name": "remote" }' type:'Spa:String:JSON'
update: id:0 key:'default.configured.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.sink' value:'{"name":"remote"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
When remote sink becomes unavailable, WP switches to alsa sink (which is expected), but it set it as default in metadata:
update: id:0 key:'default.configured.audio.sink' value:'{ "name": "remote" }' type:'Spa:String:JSON'
update: id:0 key:'default.configured.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.sink' value:'{"name":"alsa_output.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
update: id:0 key:'default.audio.source' value:'{"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}' type:'Spa:String:JSON'
When I'm loading the module again, WP is not switching it back to remote, even though default.configured.audio.sink
is still remote
My expectation was that WP should switch default.audio.sink
not only when previous default sink becomes unavailable, but also when it becomes available again (as it's explicit preference, made by user)
I'm still thinking that this is worthy to be done, as Chrome OS does it. I don't see, how I can mark it as Feature Request, though.
Seems that it's working properly now, closing
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment:
pipewire-0.3.31, Gentoo Linux, Sway
Description of Problem:
When I'm muting source in PipeWire (using pactl set-source-mute), I can see that it's muted in pactl, but alsamixer shows that it's not. Also, LED on keyboard is also not lights up. Same thing in other direction - if I'm muting source in alsa (and LED shows me that it's muted), PipeWire thinks that it's not muted, in pactl list sources
.
I'm using PipeWire on Thinkpad T460s, with onboard sound card.
No such problem with sink!
How Reproducible:
100%
Steps to Reproduce:
pactl list sources
pactl set-source-mute 39 0
Actual Results:
No sound can be recorded from laptop's mic.
Expected Results:
Muted status must be synced between software and hardware devices.
Additional Info Eg. pw-dump -N > file
(As Attachment Please):pw-dump.file
I've tried latest pipewire from git (and wireplumber as session manager, also from git) - same issue. There are also a lot of messages
[W][89372.745607] mod.pulse-tunnel | [module-pulse-tun: 204 playback_stream_process()] 0x565399120f60: overrun write:47957420 filled:30332 size:8240 max:4194304
[W][89389.684711] mod.pulse-tunnel | [module-pulse-tun: 204 playback_stream_process()] 0x565399120f60: overrun write:51209496 filled:30472 size:8236 max:4194304
in logs, but seems that they're not appearing when I'm seeking/starting play. Seems that they might be related with periodical stutters.
I found the cause - only logind backend in libseat can set session type, so, it's not related to wlroots update. Closing the ticket.
Hello! I found that swayidle is not stopping systemd from shutting down my laptop. After some research, I found that it fails to set IdleHint, because session type is tty. I checked XDG_SESSION_TYPE - it seems to be set to wayland
by sway itself. No errors is sway debug log, regarding libseat, only these (except lines about input devices):
00:00:00.014 [INFO] [wlr] [libseat] [libseat/libseat.c:73] Seat opened with backend 'seatd'
00:00:00.014 [INFO] [wlr] [libseat] [libseat/backend/seatd.c:228] Enabling seat
00:00:00.014 [INFO] [wlr] [backend/session/session.c:110] Successfully loaded libseat session
And one line from swayidle:
2022-02-27 11:55:47 - [Line 245] Failed to send SetIdleHint signal: Idle hint control is not supported on non-graphical sessions.
P.S. sway-1.7, wlroots-0.15.0, seatd-0.6.3
Hello! I found that swayidle is not stopping systemd from shutting down my laptop. After some research, I found that it fails to set IdleHint, because session type is tty. I checked XDG_SESSION_TYPE - it seems to be set to wayland
by sway itself. No errors is sway debug log, regarding libseat, only these (except lines about input devices):
00:00:00.014 [INFO] [wlr] [libseat] [libseat/libseat.c:73] Seat opened with backend 'seatd'
00:00:00.014 [INFO] [wlr] [libseat] [libseat/backend/seatd.c:228] Enabling seat
00:00:00.014 [INFO] [wlr] [backend/session/session.c:110] Successfully loaded libseat session
And one line from swayidle:
2022-02-27 11:55:47 - [Line 245] Failed to send SetIdleHint signal: Idle hint control is not supported on non-graphical sessions.
P.S. sway-1.7, wlroots-0.15.0, seatd-0.6.3
Thank you, attaching a file: log
The same behavior was on previous release, I just wanted to get a recent one and check :)
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment:
pipewire-0.3.31, Gentoo Linux, Sway
Description of Problem:
When I'm muting source in PipeWire (using pactl set-source-mute), I can see that it's muted in pactl, but alsamixer shows that it's not. Also, LED on keyboard is also not lights up. Same thing in other direction - if I'm muting source in alsa (and LED shows me that it's muted), PipeWire thinks that it's not muted, in pactl list sources
.
I'm using PipeWire on Thinkpad T460s, with onboard sound card.
No such problem with sink!
How Reproducible:
100%
Steps to Reproduce:
pactl list sources
pactl set-source-mute 39 0
Actual Results:
No sound can be recorded from laptop's mic.
Expected Results:
Muted status must be synced between software and hardware devices.
Additional Info Eg. pw-dump -N > file
(As Attachment Please):pw-dump.file
I found a way to pass property to node created by tunnel, but it doesn't help.
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment: 0.3.28, Gentoo, Sway
Description of Problem: I'm using ipv6 addresses in my local network, and pipewire-pulse is listening only on ipv4 addresses. Pulseaudio works perfectly on ipv6 addresses
How Reproducible: 100%
Steps to Reproduce:
Actual Results: 0.0.0.0:4713
Expected Results: [::]:4713
Additional Info Eg. pw-dump -N > file
(As Attachment Please):
[I][003505885.569680][pulse-server.c:6053 make_inet_socket()] pulse-server listening on tcp:00000000:4713
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment: 0.3.28, Gentoo, Sway
Description of Problem: I found that if I'm using PipeWire to pass data to remote pulse server, sound is cracking when I'm seeking through audio, or when there is no sound playing and notification sounds. I found in previous tickets recommendation to set node.pause-on-idle to false, I set it via sink_properties=node.pause-on-idle=false, but according to pw-mon, link is still achieving "paused" state
How Reproducible: 100%
Steps to Reproduce:
Actual Results: Sound is cracking
Expected Results: Sound is not cracking
Additional Info Eg. pw-dump -N > file
(As Attachment Please):
pw-dump