Conversation

Notices

1. Bernie (codewiz@mstdn.io)'s status on Friday, 12-Nov-2021 07:37:15 UTC Bernie

   Unlike PulseAudio in its early days, #PipeWire is not breaking too many things and angering users across all distros and desktops:
   https://www.reddit.com/r/linux/comments/qrrzno/pipewire_0340/

   Sure, some users are reporting bugs, but remember how many _years_ we spent killing the pulseaudio daemon to fix the damn sound?

   • Tenno Seremel, La ĉiela ombro (tennoseremel@mstdn.io)'s status on Friday, 12-Nov-2021 07:38:39 UTC Tenno Seremel, La ĉiela ombro

     in reply to

     @codewiz Or maybe people haven't started using it en masse yet :blobcatthinking:

   • katie@mstdn.io's status on Friday, 12-Nov-2021 07:40:10 UTC katie

     in reply to

     @codewiz there's no point in switching to that severely lacking buggy garbage at this point, let those who want to have problems use it for 2 or 5 years and perhaps then it'll have basic things like network audio support

     if you look back at the utter disaster pulseaudio was for the first 10 years of it's existence, it's not really reasonable to except that pipewire will be trouble-free for quite some time

   • Tagomago (tagomago@mastodon.social)'s status on Friday, 12-Nov-2021 09:15:01 UTC Tagomago

     in reply to

     @codewiz Coincidentally, I’m having troubles with my sound card kernel module (snd_virtuoso) recently, suddenly losing audio and having to reboot every time 😩 Wishing it were so simple as to kill and restart some service.

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 13-Nov-2021 21:06:29 UTC Bernie

     in reply to

     • jlj 🇨🇦➡️🇬🇧

     @jlj Yes, thinks are working smoothly now, but users aren't flocking to Linux.

     I guess we've earned a bad reputation over the years, which will take years of impeccable quality to erase.

   • jlj 🇨🇦➡️🇬🇧 (jlj@social.nfld.uk)'s status on Saturday, 13-Nov-2021 21:06:52 UTC jlj 🇨🇦➡️🇬🇧

     in reply to
     @codewiz That must've been in the Top 3 answers to problems with the popular distros for many years, back into the oughties.
     
     Linux really has come a long way. I remember how surprised I was, putting Ubuntu on a mate's Aspire last year, only to discover a crippling Wayland bug. So rare these days (and fixed within six months).
   • Tagomago (tagomago@mastodon.social)'s status on Wednesday, 15-Dec-2021 12:24:24 UTC Tagomago

     in reply to

     I believe the actual sound card was the issue, not the driver. I cleaned the dust, plugged it into a different PCI slot and now it seems revived. 🤞

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 13-Nov-2022 05:06:17 UTC Bernie

     in reply to

     • ZeStig :python: :arcolinux:

     @zstg I wonder how that's handled nowadays?

     xev will print the keycode for X11. Check that it's really interpreted as the mute/unmute key.

     Probably, the volume applet of your desktop should intercept this key code and send the appropriate dbus message to the pulseaudio or pipewire daemon. Check what happens with dbus_monitor.

     And finally, you can use alsactl to check if pipewire is really muting the correct output.

   • ZeStig :python: :arcolinux: (zstg@fosstodon.org)'s status on Sunday, 13-Nov-2022 05:06:18 UTC ZeStig :python: :arcolinux:

     in reply to

     @codewiz I can't seem to use the mute (F1) key on my keyboard on Pipewire , though it works on PulseAudio

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 13-Nov-2022 11:31:29 UTC Bernie

     in reply to

     • ZeStig :python: :arcolinux:

     @zstg The audio mute hotkey works for me on Fedora 37 with Plasma Wayland 5.26.3 and Pipewire 0.30.60