3 ms·
This is on Arch. All the logs pretend that it’s all functional. I think it might just be a Intel NUC issue.
by captn3m0 5y ago
This 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.