It’s pretty ironic to have problems with audio not recognizing headphones… on WINDOWS.
Multi-trillion (10^12) dollar company, btw.
(Both laptops are reasonably new.)
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.
Developers Developers Developers Developers
COKE COKE COKE COKE
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
Any idea if Dante Virtual Soundcard supports Linux? I haven’t done any research on it, but I use a lot of audio-over-IP devices for work and all of them use the Dante protocol. It is definitely a “just open the program, tick a few boxes to route things from A to B, and everything works” solution.
It’s proprietary software and it seems doubtful the company will port it to Linux. However it seems there’s a workaround using AES67, or a reversed engineered implementation called teodly.
I’ve never used pasystray. But I regularly use qpwgraph now since I switched to pipe wire. It’s similar to the graph from qjackctl.
I’m not sure if this is what you’re talking about, but win11 can control both input and output per application.
I often route my Pandora audio through my stereo while my default/games go through my computer speakers (or sometimes my headphones)
Oh that’s a given, I’m talking about routing a signal through several pieces of hardware and/or software in a particular way.
For example: the drummer needs to hear a clicktrack and the bass, while the choir needs to hear the orchestra/themselves separate (and they want a little reverb). (Now take this and apply it to everyone on stage)
These kind of situations can get very complex and can get very high stakes.
For those matters in windows you rely on the software that comes with your hardware. Problem is those don’t always play nice together. Or they simply don’t offer the particular situation you need.
In Linux you can do anything you want. So much so that it sometimes adds unto the complexity.
When I tried PulseAudio over network in addition to VNC I just got a really choppy unusable audio.
I just gave up and restored to streaming audio with VLC.
First I tried Ubuntu. Then I tried Mint.
Two years later, still on Mint. It works, it doesn’t spy on me, I’m good.
Work requires Ubuntu. Still with Kubuntu. Works, doesn’t spy on me.
Brothers.
Debian, both at work and home.
Kids, you’re doing alright.
btw, Debian seems to be leaking maintainers and we need to do something about it, before a hostile takeover occurs.
Any source for this?
This was what I was going off of.
https://odysee.com/@BrodieRobertson:5/debian-linux-is-slowly-bleeding:6
There’s also this now that I look into it, which you can base your own thoughts upon.
Thanks for the links!
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.
i’m just amazed that under w10 i was able to change my audio output device without issues meanwhile in w11 after digging into the taskbar you pick an audio output and IT DOESNT DO SHIT IT DOESNT CHANGE AT ALL YOU HAVE TO CHANGE IT BACK AND FORTH UNTIL THE SPIRIT OF WINDOWS ELEVEN DECIDES YOU ARE WORTHY
I’ve been having to lean on my (now deactivated due to declining upgrade) win10 install to get around a couple games anticheat, for games I can play solo. Wild.
The amount of shit that “just (doesn’t) works” is astounding after having had to do nothing more than reboot to fix something busted for years since I switched to mint.
right now the only thing keeping me on linux is fortnite and it’s not even that fun but my buddies wanna play w me
My “win11” work laptop that used to have win10: “you guys can produce audio?”
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
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!
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…
I had issues with Bluetooth Audio once. 18 years ago on my first ever install on an IBM ThinkPad 600E that I had bought used with a USB Bluetooth dongle.
I cannot get Linux mint Bluetooth to work anymore even with a good tp link dongle off my desktop. It skips or hiccups every minute.
I feel like it didn’t do this a few months ago…not one thing I’ve done has fixed, and no one can help me. 🤒
I’ve had this issue with my old Bluetooth buds because their batteries were dying. My new buds don’t have any issues and it’s on the same 2010 laptop running mint with the same Bluetooth adapter, maybe that’s what’s happening to you?
Its actually to connect to a Bluetooth amp thats like 2ft away. Its a shared amp, friends PC is wired to it and I use BT in it. It never has BT issues with any other device, only my desktop. And I’ve tried 3 dongles. And did all the pipewire pulse stuff everyone said to. Nothing. Imagine a CD skip every minute or so, is what it does.
That’s incredibly odd. Do you know where the Bluetooth antenna of your PC is? Maybe it’s getting some signal blocking from a metal component that is between the antenna and the amp? That’s the only other idea I have, because I seen to recall something about Bluetooth having this tendency to “accumulate” errors until it just skips to try and catch up after it got too many bad signals, but I can’t guarantee this is just some slop my brain came up on it’s own trying to figure out your issue
Its a tp link dongle plugged in the back. Probably like 2 ft from the reciever amp.
I don’t recall it doing this a few months ago either. I’ve done updates since then but can’t point to what caused it…
Yeah maybe I should time it and see if the skips come like every minute or if its random.
Little problems like this are what makes me hesitate from switching full time.
Well if I’m fair, everything else has been an absolute joy and made me love computers again. So don’t let my issue stop you!!
I absolutely can do everything faster and better on my Linux desktop than I ever could with windows, and I love learning, so that’s a big plus.
There are far more things I care about other than my Bluetooth issue. Wires exist, its not a big deal to plug in. I do wish it worked, but I’m sure I’ll fix it someday.
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 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.
What is any of this?
Heh, so ALSA has kind of been the audio architecture for Linux distros since forever.
Pulse Audio was supposed to modernize audio for Linux and ultimately replace ALSA.
But last time I installed Linux on my desktop, I couldn’t get audio output from my motherboard’s TOSLINK S/PDIF port no matter which settings I changed in the GUI, uninstalled/reinstalled drivers and codecs and whatnot, etc.
Nothing made any difference until I eventually found some forum post which suggested using ALSAmixer to check the settings for various audio channels. ALSAmixer is not typically installed by default and not commonly used anymore, but it was the only tool that could unmute the digital audio output channel that served the TOSLINK port - that functionality was not present anywhere else in any of the configuration options. Pulse appeared to be in control of the system audio hardware, but in reality it was just sitting on top of and still relying on ALSA to handle the back end. Also, whoever set ALSA to mute some audio channels by default on a clean install… wtf dude, that shit just makes people think their hardware isn’t properly supported and they have a driver issue.
The point being, ALSA was supposed to be deprecated years ago and all of the old audio issues resolved and modernized with a new architecture, but… I’ll believe it when I see it, when whatever the new thing is actually proves itself to be an all-singing, all-dancing audio architecture. I’ve seen this rodeo before, and last time I checked it was still a clownshow.
Interesting. Thanks for explaining.
I would make fun of you for using toslink but eARC is such a scam that I don’t know why they didn’t just bother to upgrade toslink anyway.
I think they’re lying when they say it can’t handle the bandwidth. It’s a fricken fiber optic cable, just bump the transmitter.
Why is eARC a scam? Doesn’t it carry higher audio bitrates than optical?
I had a Samsung TV and Samsung home theater in a box as my first 4k setup. The last update to the TV broke eARC.
Just wanted to throw out at every opportunity why I will not buy a Samsung anything.








