this post was submitted on 29 Jan 2024
413 points (93.8% liked)
Technology
58111 readers
5296 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
plus many USB devices need drivers, and god knows the OEM isn't gonna make them. i.e. steering wheels, stream decks, some audio interfaces. i know there is a software for streamdecks, but i imagine it's not even half of what it could do on windows.
At least all joysticks, mice and keyboards implement the HID standard and work effortlessly. The drivers they make you install on Windows are usually just tack-on products for things like configuring RGB profiles. Even professional audio interfaces and mixers (I'm currently running the SSL2+) just connect and work thanks to the USB audio standard (which transmits lossless 24-bit audio up to 192 kHz over USB).
If you're referring to digital cameras or smart watches, yes, the former is a hit-and-miss and the latter... a total miss (Garmin Connect, I'm looking at you).
Not all Audio interfaces work. I use a GoXLR and I can’t get any output from Linux to my audio setup. Can’t read the microphone either.
Not all products work as easily as you say.
A quick check seems to indicate that these, too, should work as easily as I say (there's even a tool on GitHub that gives you the same level of control as the official Windows app: https://github.com/GoXLR-on-Linux/GoXLR-Utility).
But I know sometimes it's different in the real world. Kernel too old, chosen distro has a weird audio setup, desktop environment (Gnome/KDE) only acknowledges the presence of the device if it was already connected on boot-up, etc. etc.
I’ve tried that a few times. It requires booting into windows first, then shutting down and rebooting to Linux or passing it through a WindowsVM to start it and then reassigning it to the main OS.
It just got to be too much of a headache they it wasn’t worth staying on linux.