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.)
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.)
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)
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)
Virutal Audio Cables, route audio output from OBS to Zoom/Meet as a microphone.
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.
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
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.
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.