You must log in or # to comment.
My audio is JACKed
Try run the decibel linux pendrive you made earlier and preserved in a working audio state.
And/or there are GUIs for JACK connectivity… ?
Outlook and now Pulse!
It’s a joke about the outlook thing. Not actually real
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.
Dad, don’t do this in front of my friends. You’re embarrassing me.
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
Haha thanks. I feel dense in retrospect
Sometimes satire is hard to detect in this joke of a reality we’re living in.
Ain’t that the truth. Have a good evening!
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.
That’s the thing about open source. Someone always thinks they can do better
That’s not a feature thats exclusive to open source though. Circular reasoning like this just distracts from the fact that software just like hardware is constantly evolving, even in personal spaces. Thinking someone can do better has no relevance on the “open source” aspect or the political leaning.
You mean someone thinks they need to do better not by enhancement but by complete replacement. See: Systemd and its own flailing.
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
Holy audio
New tip just dropped
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)
There’s helvum and carla control that allow you to edit the entire audio graph with all ins and outs for all hardware and software so you can route it however you like. No need for VAC and such. But even if you do, you can load pulseaudio modules i.e.
pactl load-module module-null-sinkand then route them withqjackctlwhich is absolutely crazy and awesome how pipewire lets you do that.
Give Ubuntu Studio a try maybe? It comes with a lot of audio production stuff preinstalled and preconfigured, one of the most important ones in this context being low-latency process scheduling.
Essentially most distros just have default process scheduling options, which means a process might be starved for CPU time, theoretically for up to 2s or so at a time, which is very bad if that process is generating or consuming an audio stream. Low-latency scheduling, while not entirely preventing it from happening, should significantly reduce this.
You could also just configure most other distros Kernels to do low-latency scheduling of course. Or if you don’t want to muck about with kernel settings try Ubuntu Studio, which has that and more all ready to use.
Ohhhhhh the newbies don’t remember EsounD (
EnlightenmentEnlightened Sound Daemon). Basically, it was an attempt at doing PulseAudio-esque stuff way back in the OSS era. Which is to say, it just supported software mixing of multiple audio sources, because OSS usually only allowed single process to output audio. EsounD was janky and didn’t work well, obviously. Probably the neatest thing about it was that it exposed the mixed output stream to any other app, so that made visualisers much easier to make (edit: another thing that newbies in this day and age don’t realise, but I cannot emphasise enough how crucial visualisers were for the late 1990s / early 2000s music experience). ALSA basically supported hardware mixing (if available) out of the box, so of course it immediately became my favourite.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
Systemd just keeps asking me for govt id, I didn’t bring it with me to space
Thanks Dylan
I actually had a sound issue the other day. Just no sound, how weird. It worked the day before. Checked wpactl, volumes etc, everything was fine and working. Restarted pipewire, still no sound.
Turns out my external mixer lost power because the powet socket was slightly loose.
Can’t believe Linux would do such a thing
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
While I don’t disagree, given there was a user making throwaway accounts solely to post controversial comics on !comicstrips@lemmy.world, this is a pretty specific joke that only Linux users would understand and appreciate. It of course is parodying the 2 instances of outlook issue they had on the rocket.
Yeah, I don’t actually believe all of that jokes are literally psyop. It wasn’t entirely serious comment.
It wasn’t entirely unserious either.
fake. pipewire is actually awesome.
that nagging sleep issue though? yeah…
Sleep is my favourite function to complain about, it breaks shit at random on windows and Linux, nobody seems to know why or how. The fact that sleep works as well as it does on consoles and steam deck is a miracle to me.
Well that one is pretty obvious isn’t it? Consoles and the like have a single target hardware, or very few at least, so their testing is way more reliable. Meanwhile a random PC will have one of several hundred chip designs, implemented by a few dozen different vendors, ranging over decades. Development for and testing under such conditions is just way more complicated, so all devs can really do is aiming for #worksonmymachine and hope for detailed bug reports and feedback when others have issues.
actually awesome
It shits the bed about weekly for me. I’m glad it’s working reliably for someone.
pipewire was actually the magic end of all my audio issues on all my computers. what kind of setup do you run?
But on a serious note, mine just jumps up and down in volume randomly
Does the buzzer count as having sound?
I have it piping audio to three different devices at the same time. And believe it or not they’re all in sync… most of the time.
Funny thing, but it’s windows I got problem sound problems with. Randomly decide to ignore mic, speakers doesn’t get out of “phone call quality mod”. Every time I need to disconnect then reconnect just for my colleagues to hear me out.
Linux? No problem. Easy effects run perfectly too (except when low CPU availability… But everything at that point gets problems)
Being in IT with windows 11 is awful.
“Why isn’t my mic/audio working?”
Me: “Idk, restart the computer”
“That fixed it. I don’t understand, it was just working yesterday. Why did it stop working?”
Me: “Windows 11 sucks…”
Not to mention how awful it is being in a teams call as the IT guy and my mic isn’t working because, again, windows is ass
And the awful thing is when you’re the only one having this specific issue. I’m the “bad audio” guy, another is the “VPN never works”, etc…
Wow. I’ve just stepped out of the office for a rage break because pipewire shat the bed again. It’s amazing how sound seems to be a solved problem 5 or 10 years ago but now it’s just offal.
edit:
$ systemctl status --user pipewire Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)wheeeee
That’s not a pipewire problem, that’s a systemctl problem.
Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined
The error means systemctl --user can’t reach your user’s D-Bus session because the required environment variables aren’t set. This typically happens when you’ve switched users via su or sudo rather than logging in directly, because htose don’t initialize a full systemd/PAM session. It could also be that your session wasn’t properly initialized by systemd-logind or a number of other things. Try spawning a proper user session:
sudo machinectl shell your_username@and try the systemctl command again.
typically happens when you’ve switched users via su or sudo rather than logging in directly,
- I wish typical scenarios were the only ones we had – it’d be a trivial solution.
- This is a largely unmolested install because I don’t want to be debugging my desktop. If I had a point other than whingeing, here, that would be it: when the default, vanilla, least-tuned setup falls over on the regular, then it’s fundamentally a failure at its “you had one job” task.
If it’s consistently breaking then your distro is messing up something. Bad defaults, broken scripts, etc.
The problem is that the environment variables are expected to be there and they are not there.
So, if you’re not doing something odd, then your distro is pushing misconfigurations or some other piece of software is interfering with your environmental variables. Whatever the vanilla setup for your distro is, it is not setup correctly.
I do agree that it’s frustrating, just aim the ire in the right direction… whoever configured your system’s defaults.
Yeah, it was working fine but then it got really hard to use pulse. Just when it was stable, we get a few good years before having to switch to a new unstable thing, since pulse lost support.
I never understood why we didn’t just stick with ALSA. OSS was crap, certainly, but ALSA seemed to do the job.
Depending on the output device it’s still using ALSA underneath (e.g. Bluetooth output instead is given to the BT stack), PipeWire is dealing with managing and routing the audio output rather than actually performing it.
I used to have crackling issues with pulseaudio. It needed restarting constantly. Not issue since the switch to pipewire. So my experienced was the absolute opposite of yours.
it got really hard to use pulse
Pulse was another tumour by Lennart. I have no regrets in its passing.
all the new technology!!
oh, now there is no sound…
For we all live underground
My laptop is Mint and it’s never given me audio issues. My gaming rig is Nobara and the only audio issue I’ve had with it is that I forgot to switch the output to the TV.
