this post was submitted on 20 Jun 2025
1084 points (98.3% liked)
linuxmemes
25823 readers
382 users here now
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.
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.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What distro? What sound card?
You might try something new that runs pipewire by default, if you haven’t already. But I might also know of some specific quirks with specific cards.
Things a random user of Windows never asks themselves in their lives
Only because the sound card is exclusively designed for windows.
It’s not that way anymore. I actually can’t configure gain (and some other features) for my Fiio KA3 on Windows. Now Android (and iOS) are their main priority.
Which does give the useful quirk of allowing me to configure it in desktop linux…
This is going to be a pattern though. It won’t necessarily get better for the Linux desktop, but Windows is going to increasingly feel the pain of being a “lower priority” OS for hardware.
We're not doing this. People in the Linux community are so tweaked by years of bad support that they assume every complaint is a call for help.
It is not.
I know what's broken, I know why, I know it's not easily fixable, I have a workaround. This is not a tech support thread.
I don't need information from users more savvy than me, I need the bad sound firmware they're loading in lieu of specific support for my audio card to be fixed, or even better, replaced by actual specifically supported firmware so my card works. In the meantime, crappy on-board audio and wasting money on hardware I'm not using it is.
I was kind curious too, even if I can’t fix it. But… okay.
That's fair, and I don't have a problem with that. I'm just annoyed by the tendency of the community to react to criticism with technical advice, which I find to be a frustrating crutch.
FWIW, the card is a Sound Blaster X AE5 (that name sure has aged poorly), and I've had similar issues with it in both a Manjaro and a Bazzite install.
IMO that reaction is healthy, as long as it isn’t a hostile “you’re holding it wrong” (which was not my intent, and is very much a community problem). Communal troubleshooting is the nature of the Linux desktop.
If you don’t want advice, that’s fine, probably reasonable based on what you described. But I have had some similar (but not so severe) issues with Fioo and Xonar cards that got fixed with some low level configs I had no idea existed.
And maybe I could get to some more in-depth solution that sorts it out, but that's me spending time on a problem that a) I shouldn't have to, and b) I have a functional workaround for already.
Communal troubleshooting is the nature of Linux desktop, but also a massive problem. You shouldn't need communal troubleshooting in the first place. It's not a stand-in for proper UX, hardware compatibility or reliable implementation. If the goal is for more people to migrate to Linux the community needs to get over the assumption that troubleshooting is a valid answer to these types of issues.
Which is not to say the community shouldn't be helpful, but there's this tendency to aggressively troubleshoot at people complaining about issues and limitations and then to snark at people actively asking for help troubleshooting for not reading documentation or not providing thorough enough logs and information. I find that obnoxious, admittedly because it's been decades, so I may be on a hair trigger for it at this point.
If it helps for a future purchase, Focusrite's external interfaces have been amazing for Linux support.
To the point where I didn't even notice; It just worked perfectly out of the box.
I'm assuming you've already checked this, but is your interface set to the same frequency/bit depth between Linux and windows? Or if it uses optical, whether it's set to the same word clock source.
I tried fiddling with the Windows settings, but that didn't fix it immediately, and the sound is clearly wrong on Linux even with a power cycle. And googling for it I'm not alone in having issues and support for the thing is patchy. I mean, rebooting should have fixed it anyway. There's no reason why either OS wouldn't initialize those things on boot.
I am not particularly commited to the thing, so I wouldn't buy an upgrade. The only reason I have it is at some point I ended up with a motherboard that wouldn't do 5.1 out of the box, so I got something relatively affordable to slap in there. It sounds noticeably better than integrated audio, though, so now that I have it I'd like to use it, even if I'm not on the problematic old motherboard.
But again, I dislike the tendency to recommend functional hardware or technical support. It's kinda frustrating. And frankly, it works on Windows, so if I was looking for a fix, that's right there. The onus is on Linux for support in this type of setup where the issue is not on the Windows side that's a reboot away.