News for hackers. Stuff that matters.
Re:PulseAudio has been removed from dports by na85 on Monday August 22, 2016 @12:18PM (#12337360)
>Who needs features anyway.

Can you name a single feature or use case addressed by PulseAudio that isn't addressed by ALSA?

Re:PulseAudio has been removed from dports by Symmetry on Monday August 22, 2016 @12:35PM (#12337494)
Unplugging my headphones and letting other people be able to hear what I'm listening to? I mean, with ALSA I can shut down whatever program I'm using, switch to speakers from headphones, then start the program up again but that's a bit cumbersome. Maybe it is possible with ALSA somehow but not with the programs and distros I'm familiar with. When PulseAudio came out all of a sudden Linux went from less convenient to use headphones and speakers with than Windows to distinctly more convenient.
Re:PulseAudio has been removed from dports by ne0phyte on Monday August 22, 2016 @12:49PM (#12337594)
I never had a laptop where plugging in headphones didn't disable the speaker (and nothing I could do about that in software).

If that really is the case you could use dmix and have audio played on both the headphone and speaker output. You would still have to mute the speakers when plugging in the headphones though.

Re:PulseAudio has been removed from dports by pyre on Monday August 22, 2016 @04:52PM (#12339345)
> If that really is the case you could use dmix and have audio played on both the headphone and speaker output. You would still have to mute the speakers when plugging in the headphones though.

You're stating that Pulseaudio isn't necessary because someone could do the same thing with a combination of dmix and manual intervention? Have you considered the possibility that someone might like the convenience of not needing to do manual intervention?

Re:PulseAudio has been removed from dports by ne0phyte on Monday August 22, 2016 @05:02PM (#12339417)
Huh? I never stated that Pulseaudio isn't necessary.

I just pointed out a possible solution/workaround with ALSA and dmix for redirecting the audio output to two devices/pcm outputs.

After years of using just ALSA and messing around with its config on different computers I am now using Pulseaudio too. Once it's running it's a lot easier to use and more flexible, especially when it comes to hot-plugging and switching between inputs and outputs.

Re:PulseAudio has been removed from dports by khedoros on Monday August 22, 2016 @12:54PM (#12337641)
I assume they're either using USB headphones or some other case of having multiple audio output devices, like my desktop with onboard sound and a separate PCI sound card.
Re:PulseAudio has been removed from dports by the_mitsuhiko on Monday August 22, 2016 @12:56PM (#12337655)
That does not apply to non 3.5mm headphones and even those are software driven now in many notebooks.
Re:PulseAudio has been removed from dports by Ded7xSEoPKYNsDd on Monday August 22, 2016 @12:52PM (#12337620)
PulseAudio features I have used in the past that I don't think ALSA has:

* playing audio from/to another Bluetooth device (with bluez)

* playing audio on a PulseAudio server running somewhere on the network

* transparent encoding of audio output as DTS (for surround support over SPDIF)

I also seem to remember plain ALSA having trouble with multiple applications playing sound at the same time, which is just pathetic.

I'm sure some of these could in theory be built on top of ALSA, but fact is that today's Linux distributions use PulseAudio, and for me it always worked well.

Re:PulseAudio has been removed from dports by trothamel on Monday August 22, 2016 @12:35PM (#12337498)
I'm not sure about ALSA's capabilities in this area, but one thing PulseAudio does well is moving playing audio streams between sound devices. (For example, moving it from my monitor's speakers to my USB headphones.) Being able to control mixers on a per-application basis is also quite nice.
Re:PulseAudio has been removed from dports by izacus on Monday August 22, 2016 @12:50PM (#12337604)
How do I make my bluetooth headset (which supports both A2DP and Handset profile) work with ALSA so it switches to headset profile when mic is active, reverts to A2DP when it's not and switches back to laptop audio when BT is off?
Re:PulseAudio has been removed from dports by dezgeg on Monday August 22, 2016 @12:35PM (#12337496)
How's the situation for hotplugging sound devices in ALSA nowadays? The top Google results for "alsa hotplug" all point to editing configuration files or udev rules or shell scripts.
Re:PulseAudio has been removed from dports by abstractbeliefs on Monday August 22, 2016 @12:20PM (#12337372)
On the flip side, if everything can be done by ALSA, and PA is seemingly objectively worse, for what reason are people building their software against PA? Why is it being included anywhere at all?
Re:PulseAudio has been removed from dports by janoc on Monday August 22, 2016 @12:54PM (#12337642)
Except ALSA cannot do everything that PA does. ALSA is low-level Linux sound API that PA builds on. Read the post above, it explains the difference.

Basically, if you want multiple sounds playing at the same time (e.g. music + desktop notifications) and you don't have hardware mixer (many common sound chips don't and rely on Windows drivers/sound system to provide the functionality), you are out of luck (no, the ancient dmix plugin is not a solution!). Bluetooth audio (headsets) doesn't really work without PA.

Configuring apps to use different devices (music should go to speakers and video conferencing to a headset ...) is a pain without PA - most applications don't let you select the input/output devices.

And many other things. ALSA is good, but without PA the sound support on a modern Linux desktop would be stuck right in the late 90s. Is it necessary? Not strictly, but it is one heck of a convenience that most don't even realize they have.

Here is a good post from 2008 explaining many of the issues PulseAudio solves and addressing some of the old FUD:

http://0pointer.de/blog/projects/jeffrey-stedfast.html

Unfortunately, there are tons of people with strong opinions about both PA and systemd but very little actual knowledge about what these components do and what issues they address in a modern Linux/Unix system. But that doesn't prevent them from spreading BS FUD and conspiracies about this or that group trying to dominate the market or take over the competing Linux distros.

Re:PulseAudio has been removed from dports by dTal on Monday August 22, 2016 @03:45PM (#12338876)
>no, the ancient dmix plugin is not a solution!

Given that that's exactly what it's for, why isn't it?

Re:PulseAudio has been removed from dports by orkoden on Monday August 22, 2016 @12:23PM (#12337416)
Because many devs are on Linux distros, that include PulseAudio by default. Support for *BSD ports is often a bit weak for software like that.
Re:PulseAudio has been removed from dports by dleslie on Monday August 22, 2016 @12:23PM (#12337415)
The power of defaults.

Why write for ALSA when the distro ships with PA, and so all of its configuration tools are PA-focused?

Re:PulseAudio has been removed from dports by mveety on Monday August 22, 2016 @02:05PM (#12338155)
Also pulseaudio allows them to sorta support OSS and whatever else pulseaudio will output to for free.
Re:PulseAudio has been removed from dports by lmm on Monday August 22, 2016 @12:32PM (#12337473)
Basically it's a RedHat conspiracy to make open-source programs not work on non-Linux.
Re:PulseAudio has been removed from dports by GranPC on Monday August 22, 2016 @12:39PM (#12337530)
I don't see how building your program against ALSA (Advanced Linux Sound Architecture) would make it more compatible with non-Linux OSs.
Re:PulseAudio has been removed from dports by pyre on Monday August 22, 2016 @12:50PM (#12337607)
Maybe @lmm wishes that Redhat threw support behind OSS4? Is that supported under the *BSDs?