-
-
Notifications
You must be signed in to change notification settings - Fork 577
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
[Problem]: No audio with 4.3.5-1 #1946
Comments
Thanks for the post. The pipewire backend is the one called |
Do i need to build it for Also, it was working with default (no edits on |
You’d need to check the package makers about support for Yeah, the default is probably |
so i manually built 4.3.5-1 from trunk branch
Changing to pw, i get a bunch of errors
but pipewire is running in user service
|
I guess I am also curious as to why upgrading from 4.3.4-1 broke if the only thing that changed on |
I also see no error output or crashing in systemd with pacman package under |
Have you tried reverting to 4.3.4-1 and default config to see if that works again? I'm wondering if there was another package updated on your system at the same time that is actually the cause of the problem. I had some packages update on my Fedora system recently - I'm still not sure which package it was (presumably either an alsa or pipewire one), but my configuration using an alsa loopback device broke. I had to use a different name for the same alsa audio device for it to start working again. |
As I have cleared pacman caches since the last release, I have to manually build that version. I am getting the same result. There were no other packages updated at the time shairport-sync was. |
Thanks for the comments. There are a few moving parts here, so it's difficult to figure out what's happening. It might be useful to get the settings and configuration strings for both built versions using Another thing to consider is the interaction between PipeWire and a GUI -- please see PulseAudioAndPipeWire. Finally, for the moment, it's also worth checking that the output device's volume controls are set and that it's not muted -- it's caught a few people out before 😏. |
Deep dive time. Hopefully I can document this well enough (expands comment box). In every following scenario, the bin was deleted, sudo pacman -R shairport-sync
sudo rm "$(which shairport-sync)"
sudo rm /etc/shairport-sync.conf
sudo rm /usr/share/man/man1/shairport-sync.1
sudo systemctl disable shairport-sync.service
sudo rm /usr/lib/systemd/system/shairport-sync.service
sudo killall shairport-sync 4.3.5-1Arch Pacman PackageArch Package - Extra Repo
Compiled and Installed
4.3.4-1Compiled and Installed
I never see a shairport-sync PipeWire sink show up The sink that used to work is turned up, and still plays audio from the system just fine. |
Okay, thanks for that comprehensive report! 4.3.5-1The package does not have pipewire support built in -- when you look at the version string:
...it does not include Compiled and InstalledThis does include pipewire support but the configuration file does not ask to use the pipewire backend, so it defaults to the Then you launch Shairport Sync with the
Likewise, this needs explanation (call it Explanation 2) -- see discussion below. 4.3.4-1This acts the same way as 4.3.5 under the same conditions. DiscussionUnfortunately, these problems are all caused by the way PipeWire (and PulseAudio) works. Please see PulseAudioAndPipeWire.md. (BTW, this is not to denigrate either of these -- they address a different set of use cases very well!) PipeWire only offers services to users that have logged in though the GUI. Explanation 2Thus, when you ask to use the
Explanation 1If you don't ask to use the Summary
WorkaroundsIf you have a second Also, sometimes, when PipeWire isn't actively using the main |
What happened?
Updated to 4.3.5-1 via pacman and now I can no longer get audio output. I have PipeWire.
Relevant log output
System Information.
/ossssso+/:- -:/+osssso+-
+sso+:-++:.
-/+/.
Configuration Information.
The text was updated successfully, but these errors were encountered: