Which is exactly why I ignored the silly troll attempt by bringing Doom 3 a 2004 game into the argument. PA is about now and looking forward and if older games and their libraries need to be patched to work with it, so be it. PA is frankly the most mature approach to Linux audio we've had so far and while some might see it as VOIP/AOIP techdemo its networked audio approach is what gives it great multi device functionality and ability to switch devices on the fly without needing to muck around in config files. That's a mature approach because each device is profiled and works to the same standard which allows for greater variety of device support in the future.
Announcement
Collapse
No announcement yet.
Linux is not ready for Steam
Collapse
X
-
Originally posted by IsawSparks View PostPA is frankly the most mature approach to Linux audio we've had so far and while some might see it as VOIP/AOIP techdemo its networked audio approach is what gives it great multi device functionality and ability to switch devices on the fly without needing to muck around in config files.
*grabs picture of Xfce mixer again*
Not much .config file mucking with that. And switching devices is a drop-down menu.
Why do we need a complicated sound daemon because Gnome Volume Control is crap?
Comment
-
That's one solution which while simple doesn't offer the broader device compatibility, nor forward thinking which PA does.
Also, you're entirely ignoring the AC3 routing and mixing issues when it comes to ALSA due to poor chipset profiles and poorly maintained driver support. Mucking around with asound.rc to get DTS and Dolby 5.1 vs PA properly detecting and routing streams accordingly to my Sony 5.1 Amp?
Thanks, I'll take PA. It just works.
Comment
-
And USB output works as well. You just select the USB device in that drop-down and you're done.
Bluetooth needs work.
After I connect a pair of headphones using Bluetooth Properties 2.28.1, sound still plays through the speakers. Running "sudo alsa reload" fixes this, but it should happen automatically when new headphones or speakers connected. This confused me until I figured it out; I had tried "sudo alsa-utils restart", which didn't make any difference, leading me to conclude my configuration files were broken. http://wiki.bluez.org/wiki/HOWTO/AudioDevices doesn't mention the reload command, and the inst...
But why do we need an entire sound daemon to allow for Bluetooth audio? That functionality should just be added to the core sound API itself.
Comment
-
Comment