4 ms·
Pipewire is great, but it is sadly lacking in end-user documentation. With pulseaudio, if something broke or needed tweaking - I had thousands of forum posts to
by captn3m0 5y ago
Pipewire is great, but it is sadly lacking in end-user documentation. With pulseaudio, if something broke or needed tweaking - I had thousands of forum posts to go through. Even the Arch Wiki has a PulseAudio/Troubleshooting section with various configuration suggestions.
For Pipewire, there is no end-user documentation that I've found so far.
On one my setups, and all media stops playing, including videos if I forget to plug in my headphone. Restarting pipewire or plugging in devices after that doesn't seem to help, and I have no idea about the pipewire configuration files to even attempt any changes. I would really appreciate some end user debugging and configuration related documents.
- eloeffler 5y agoI haven't used it yet, but could it be that you haven't checked for a while? https://wiki.archlinux.org/title/PipeWire#Troubleshooting https://wiki.archlinux.org/title/PipeWire#Troubleshooting There are a couple of sections there
- captn3m0 5y agoNopes, I’ve tried most of this already.
- prvc 5y ago>With pulseaudio, if something broke or needed tweaking >I had thousands of forum posts to go through. That points to what sounds like two disadvantages, if anything.
- captn3m0 5y agoThat was part of my point - PA’s troubleshooting/tweaking experience was terrible, but it was still feasible.
- prvc 5y agoIf you were to experience a novel or rare problem with PulseAudio, you would be in the same boat. The likelihood of a user encountering a problem is more apt than assuming as a given that you're dealing with a problem.
- mjevans 5y agoCurrently you want bleeding edge PipeWire. Many underrun issues are addressed with newer versions. Archlinux seems to stay updated, if you're not using a rolling distro (E.G. Debian) you might need to pin some packages from a future version.
- captn3m0 5y agoThis is on Arch. All the logs pretend that it’s all functional. I think it might just be a Intel NUC issue.
- mjevans 5y agoThese logs? Check them. journalctl --user -b -u pipewire journalctl --user -b -u pipewire-pulse journalctl --user -b -u pipewire-media-session I also have this from earlier when I had errors; now I use it only right after startup because I'm doing output to multiple audio cards simultaneously. systemctl --user restart pipewire.service pipewire-pulse.service pipewire-media-session.service ; systemctl --user restart pipewire-multi.service (The -multi one is a local service based on the guide for multi-output audio.) If you see log entries similar to: pipewire-pulse[1173]: client 0x55f2d47effa0 [Firefox]: stream 0x55f2d484f7d0 UNDERFLOW channel:0 offset:221184 underrun:16384 I fixed this for multi-output audio by 'increasing the headroom' cp /usr/share/pipewire/media-session.d/alsa-monitor.conf ~/.config/pipewire/media-session.d/ vi ~/.config/pipewire/media-session.d/alsa-monitor.conf There's a section near the end for alsa_input and alsa_outputs, WITHIN actions update-props, I un-commented and set: node.pause-on-idle = false audio.rate = 48000 api.alsa.headroom = 1536 However I believe that's specific to my multi-audio output setup and a mixture of different soundcards; I could probably hunt for a lower headroom value.
- encryptluks2 5y agoBleeding edge indicates the software is using an unstable branch. The stable branch of software (non-beta) is not considered bleeding edge.