Linux audio issues were common during the transition to PulseAudio, but that was almost 20 years ago now.
I was about to say... Maybe I've just been lucky, but I haven't had the slightest issue with Linux audio. Ever.
And they continued until the transition to Pipewire.
pipewire is so cool! It's so easy to set it up to sling to snapcast!
[sobbing] I don't know what the fuck snapcast is, I just want sound to work!
Agreed, it was the next step from pulseaudio. To say it wasnt problematic is incorrect, as it had many problems and needed a lot of manual intervention.
Nowadays, pipewire appears alot more stable, even with the compatibility layers for when stuff uses pulseaudio.
I've been using Linux as my main operating system since 2010 and can't recall having any audio issues. My desktop has 5 sound cards and they all work fine. I don't use bluethooth for audio, so I guess that makes things easier.
Yeah, but does your half-assed linux install come with the incredibly useful NoPilot? Huh?
Checkmate, linux nerds!
does your half-assed linux install come with the incredibly useful NoPilot?
Nope. If for some incredibly bonkers reason I actually wanted to use it, I'd have to actually -- gasp! -- go to a website and talk to it through a website interface, rather than an interface directly integrated into every goddamn app on my own computer. That's like ... two, maybe even three extra clicks!
(Seriously, though. If for some reason I wanted to talk to a chatbot, I could do that on the chatbot's website. Why do I need it to be integrated into fucking Notepad?)
Why do I need it to be integrated into fucking Notepad?
The rate at which every security practice is being torn down for the sake of clankers is giving me suicidal tendencies. Surely you will not regret giving the token-based randomness machine root access!
And don't worry, the mega-corp that has constantly lied about things in the past promises that all the data from the integrated app that gets sent back to company HQ only gets used for training better chatbots (probably) (maybe) (possibly) (unless it's, like really good blackmail material). And every single thing you've ever typed into Notepad surely isn't just sitting there on a company server, waiting for a subpoena from an increasingly authoritarian government to gain access to...
(And, of course, that program you coded in Notepad? The fact that it was used to train Microsoft's next chatbot, which then went on to magically write code strikingly similar to yours to be integrated into the next Microslop project without notifying or compensating you in any way ... purely coincidental, of course. It's not stealing -- it's training. Running it through a chatbot first magically removes all copyright protection from your code.)
PipeWire (written by Wim Taymans) did a lot of good for the Linux distro ecosystem when it comes to audio.
I remember the times before pipewire, not that fun.
Yet more fun than using microslops slop
The fun part about windows is you don’t know if it’s breaking because of the coke code from the 80’s or the vibe code from the ‘20s.
You forgot the Ballmer Peak code from the 00's
Oh, yeah, cocaïne fuelled developers bouncing around. I'd forgotten about those.
On Windows audio cuts out every so often.
Also an update broke a driver a bit ago and I had to edit the registry to fix it.
Linux is my comfort OS, everything just works.
Linux is my comfort OS, everything just works.
This exactly!
People who remember trying Linux 20 years ago look at me like I'm crazy. But Linux is so cozy, now!
When you want to route your audio a certain way (let’s say audio recording/production or such)
Windows: oh sure, you just gotta download a shitty proprietary driver/program, get that to talk to your daw and from there on it’s…let’s hope it does what you wanna do.
Linux: You want routing options? Have some …(ALL the options)
As someone that is using RTP to send audio from and to different Linux computers, this is unfortunately an option that is getting more difficult to use as time passes. A few years ago when pulseaudio was dominating, it was trivial to just tick a few boxes, enable RTP, see a lit of devices in pasystray, and choose it with a few clicks. Now since pipewire, this is no longer possible. Sure, RTP still works, but using the command line is now mandatory, as all the GUI options have disappeared.
I still find myself reinstalling pulseaudio on most of my computers running Linux because I need RTP audio and it's disappointing that it's getting harder and harder to get it to work on Linux.
Yeah they now expect you to use their native protocol for sharing audio on the network.
https://wiki.archlinux.org/title/PipeWire#Sharing_audio_devices_with_computers_on_the_network
To be fair, a lot of bluetooth headphone problems i had on my work laptop was just microsoft teams.
My most recent project requires me to use teams again -.-
It finds new ways to loose my peripheral devices ever day and adds effects to my camera that are not even available in the menu. I'm wondering if they try to get you to install it, or hate Mac users or Firefox or whatever. I mean it has been bad for all the time I knew it, but it seems to be getting even worse.
LOL Yeah, I mean Linux has always had audio problems, but I find that I can solve Linux related ones mine faster than on Windows (when I used that garbage). The time it took grew smaller as my knowledge grew. Pulseaudio will randomly shit the bed and take Alsa with it. So about three terminal commands and 5 minutes later my sound is often repaired. It is weird that a billions of dollars sort of company can't get that shit right or make it a speedy fix at the very least. The troubleshooting tool would take fucking forever and often shit the bed. Touching the Powershell was cursed, but Linux made the terminal a blessed experience!
I did IT for my company on the side of my job for a year or two.
Prolific problem where windows would disable the microphone but every single "windows tool" said it was working perfectly fine except teams would say it was not available.
The only possible fix that someone on the internet found was to download an old sketchy file from a 3rd party source for an archived version of their "pre-help-assistant AI slop" audio troubleshooter, and run that and it would immediately say "oh, it is disabled, let me re-enable it for you"
Even though every tool, setting, and even registry said it was enabled.
Microsoft has the worst audio.
Linux: "I am the non-janky OS now!"
Hot take: There is not now, nor has there ever been, a non-janky OS.
Some Linux distributions are absolutely less janky than Windows at the moment, though, absolutely.
I haven't used a mac in a few years, but it was pretty jank-free the last time I tried it, but I'm certain the situation there has gotten worse.
just got a new laptop and wanted to boot into windows once so i could make sure bitlocker was off and i had to go through 15 minutes of clicking decline on upsells for 365 vs clicking on install linux mint from the live usb and being yes install
So real. Never have audio issues on my Linux PC.
Meanwhile my company issue ThinkPad just doesn’t want to work with any Bluetooth audio input. I can’t take work calls from any other device either due to IT policy…
Linux revoked my mic permissions in the middle of a call today, on Google Meet. Happened before on Zoom.
I have not root-caused it to see if there was flaky hardware or what.
Ok, this prompted me to root-cause the issue. A bad cable between laptop and USB dock seems most likely. Hardware issue, not Linux!
Most machines have issues with the headset headphones.
Windows, Mac, Linux.
Many headphones that are headsets will pair as a dual device with the crappy two way audio that sounds like you just connected to your cars Bluetooth from 2005x
Over the years, I've just come to accept that, no matter the OS, there are just some things computers suck at. Working with hardware is one of them.
I’m pretty sure working with software is the other.
I remember when I used to have audio problems all the time, including headphones literally just not even working somehow. Then I switched to Linux.
I mean honestly 😬 it still kinda sucks compared to Windows. Less problems on Windows vs my Linux laptop. Do they mean wired headphones? Because I use Fedora on my framework 13 and my bluetooth headphones just do not want to play sometimes. It works after some reconnecting and switching outputs. Or my bluetooth keyboard is just not connecting sometimes. And I have to "forget" it and re-pair it. Sometimes I think a lot of my colleagues or friends with Linux systems just get used to rolling with punches/issues because it feels better to be working on Linux. At least I don't have to click away stupid full screen Microsoft Account reminders etc.
I have to "forget" it and re-pair it.
If you're dual-booting, you need to sync the Bluetooth pairing keys between Windows and Linux.
My "win11" work laptop that used to have win10: "you guys can produce audio?"
I remember using my Bluetooth headset on my windows 10 laptop would completely freeze the settings and volume menus... It was a really powerful laptop too... So bizarre
Uh huh uh huh uh huh... call me when ALSAmixer is no longer needed to unmute the TOSLINK output on a new install because who the fuck knows why it's muted by default in ALSA and that setting is not surfaced anywhere in the UI.
Literally, neither my PC screen works, nor does the download version of spotify work on my Win11 PC. Literally unusable garbage... Long live ubuntu for just doing what i tell it to do.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.