
They’re not supposed to have both installed.
Pipewire is newer and emulates PulseAudio so that it can be used as a drop-in replacement. There’s literally a command called
pipewire-pulserelated to this.It makes me wonder if they really have both installed or are mistaking Pipewire’s emulation for an active PulseAudio installation, and so it’s just Pipewire that’s acting up.
I’d say reboot, but being in space might be one of those times where that’s a non-starter. In which case, they’re going to have to get their hands dirty unpicking system hooks and trying to reattach them all again as and when Pipewire’s working again, assuming it doesn’t do that automatically.
I never had a problem with either Pipewire or real PulseAudio back when that was current. I had motherboard sound physically pop, requiring the purchase of a separate sound card, but never a driver issue, so I can’t even imagine what might be going on.
I’m pretty sure this is a meme based on the real report that they had 2 instances of outlook on windows and not real.
Wait, they had two instances of not real? They are learning too much.
Sorry I am autistic and often don’t know how to properly formulate my thoughts into sentences :D
You’re in the right place, most social media users can’t properly formulate their thoughts into sentences, lol.
This is psyop, they run windows up there, their outlook doesn’t work, and everyone kinda accepted that.
This is a meme, sir.
Most of psyops are done via memes nowadays
deleted by creator
actually awesome
It shits the bed about weekly for me. I’m glad it’s working reliably for someone.
deleted by creator
Systemd just keeps asking me for govt id, I didn’t bring it with me to space
Thanks Dylan
This is a joke right? Yesterday I saw a post that outlook was a problem for them
Yes it’s a joke referencing the two Outlook instances issue, but for Linux people
Real talk, though: why has Linux taken at least five tries (OSS, ALSA, JACK, PulseAudio, PipeWire) to get audio right?!
OSS came first, then got replaced by ALSA after it became proprietary.
PulseAudio is a userspace audio server to which programs connect. It manages audio settings per app, then sends everything to ALSA. JACK is the same but with a focus on low latency.
PipeWire is a modern drop-in replacement for both, and also has support for video on Wayland.
And then there’s also sndio, ported from OpenBSD. This does basically the same thing as OSS/ALSA.
They don’t have the same goals.
JACK is for professional audio.
OSS and ALSA are kernel audio drivers, they’re the most powerful of them all but extremely low level. Everything else, like pulseaudio/pipewire are just higher-level interfaces that feed ALSA audio.
Pulseaudio and pipewire are sound servers.
So really it only took two tries:
OSS -> ALSA
Pulseaudio -> Pipewire
I’m still waiting for the latency to be viable for playing guitar with an audio interface.
I’m using pipewire just fine to do so? I just needed to set the buffer size to something appropriately low and I’ve had no issues from popewire’s side
Maybe it’s time to give it a shot again. Does pipewire have similar functionality to voicemeeter the virtual audio cables?
Never used it, but I use something called pipewire graph or something (I’m on vacation and I can’t be bothered sorry heh)
qpwgraph








