Care to elaborate? Your comment reads as a sentence-long "NO, YOU!" right now. What about Canonical is a problem, and who are they causing the problem for?
As a "Linux idiot" myself, I hear your disapproval of the parent post, but am curious to hear the details that support your opinion (I might be able to learn something from it).
pilgrim689: Why is everybody hating on Canonical for
ditching X11?
sneak: Because they're "Linux idiots" who love X11.
ihsw: They don't love X11, they just hate Canonical.
ihsw is saying that the change isn't getting negative reactions because of the change itself, but because it is being made by Canonical.
I thought everyone was hating on Canonical for ditching X because rather than support the fledgling standard replacement for X, Wayland, they once again (just like with systemd vs upstart, compiz vs mutter/kdm) go off and do their own thing.
And if it turns out like either of those, they end up with an inferior barely maintained product that gets pushed to the sidelines once they show it off on a showroom floor.
Skimming the article, Canonical has some legitimate criticisms of Wayland, and are working on something that doesn't have those problems. Yay, this would be good! Except that it's by Canonical, and as you said, "Canonical never delivers". (That wasn't a quote from you, it was an iteration of "OP (never) delivers")
What I said was that when Canonical does deliver, they let the delivery wither and die without support because they are spread like a teaspoon of mayo thin on their footlong distro sandwich. See: Upstart, Compiz, Software Center.
> It certainly improves certain details of the user experience, when it works correctly, also usually consuming more CPU than flash player
You make a sweeping statement which is not true for every system. Looking at what happens playing a Youtube music video, according to htop:
- pulseaudio is using between 0 and 1% CPU
- plugin-container (wrapping Flash) is at 3%
- firefox oscillates between 20 and 40%
Now, my understanding is that, at the time pulseaudio came out, it was using untested functionalities in audio drivers which, for many chipsets, did not actually work and progressively got fixed. There was the same problem with graphics drivers when KDE 4.0 was introduced. Maybe you're out of luck and actually have a defective driver?
I'm not sure I have a bad driver, the last two chipsets I used were Intel (and no weird audio devices), works fine with other sw. Latest distro tested: RHEL 6 and Fedora 16
For me, PA would stay around 5%, 10% sometimes, and even more depending on the task. Not to mention crashing every week (at a random moment)
I'm not sure if this could affect the CPU usage. I hear that you can play with the resample setting to lower it, but I haven't had to do that on a 5+ yo desktop.
Nonsense. Fedora is a fine desktop Linux... I run it on a woefully underpowered laptop which I use for development, and it is every bit as usable as, say, Ubuntu (which I use on my corporate laptop). In fact, I'd take my Fedora/KDE setup over this Ubuntu/Unity setup any day.
Am I the only person in the world who has never had anything but a pleasant experience with PulseAudio? The first time I noticed that I was using it, I had already been using it for a year...
No, you're not the only one. I'd been forewarned of the awfulness of pulse, but didn't even notice its installation until later, when I discovered all the useful things I could do with it: play music over the office Apple airplay thingy; use two sets of headphones simultaneously; send audio to another computer in the house. Without any typing, searching, or rebooting,
I remember OSS and Alsa, and I don't miss either. As far as I can see, it makes Linux audio work like any other computer in this millennium.
I haven't had any recent trouble with it. Back in the early days, it didn't always work well with SDL, but that was fixed years ago. I've been able to crash the daemon with stress tests, but it seems to restart automatically.
I can't understand all the dislike of PulseAudio either. It certainly has a nicer API than /dev/dsp.
My most recent attempt to use PulseAudio (as it came via Ubuntu) had the quirk of not activating the headphone jack when something was inserted. It dutifully turned off my speakers, but no sound was available elsewhere.
I previously had stock Debian on the machine, and everything was working fine. A half day's effort was put into toying with ALSA configs that Pulse was deferring to for whatever driver choices it made. Dozens of help articles or threads where everyone else in the world could proclaim "Thanks, that fixed it for me!" left me with less functionality than I started with.
The only thing Pulse has ever done right for me was was help to record some loopback audio on an otherwise-crippled sound card.
No, there are a decent chunk of users for whom it works fine. Maybe as many as 95%. But there's also a substantial number of users for whom it introduces major problems - which would be more forgiveable (at least to yours truly) if it provided any visible advantages over existing systems.
(After a few months of trying to make pulse work I left for FreeBSD, which works beautifully and avoids a lot of linux's change (seemingly) for the sake of change)
For me, PA crashes around once a week (and this is with the latest version I tried), or just plain stops working (like muting the sound, garbled sound, etc)
Not to mention the delay that happens while switching songs in mplayer for example. Use ALSA and song switch is instantaneous.
Once every two or three months, when I remember to apply updates.
> - What audio softwares you use the most
Only flash (youtube, primarily. Also youtube's html5 player probably, I haven't paid much attention to that) and mplayer. A few years ago, XMMS2. I used to use an XMMS2 client I wrote for music, now I just use some bash scripts and mplayer; I can't say I've noticed any delay while switching songs with mplayer or XMMS2.
When I play music from my laptop through my raspberry pi connected to my TV with pusleaudio, then I notice an audio delay. That is the only sore spot pulseaudio has ever presented me.
Very interesting. I thought some instability may be due to PA staying up for a long time, but apparently not.
About the delay, try this: mplayer *mp3 (in a directory with mp3 files, of course), then press >. There should be a significant delay in switching songs (like, 0.5s). Make sure mplayer shows it's using the [Pulse] driver
I agree with. The only problems I've ever had with it have turned out to either be problems with the actual hardware or problems with the clients, not problems with Pulse Itself.
I will admit having a lot of a hate for figuring out which audio 'profile' is which...
If you've got the plugs for 7.1 and a normal line in as well as possibly a digital one, they you've probably got 23 choices of profile for your built in audio device. Add in a GPU with HDMI and the NVIDIA driver and you probably get at least another 7+ choices all labeled Nvidia... I find I frequently have to guess multiple times whenever I hook up a TV via HDMI.
But it works quite well if you define works as works without adding on any usability riders.
No issue on a couple of machines. Running with a call to start-pulseaudio-x11 from my .xsession, works fine. I believe running it as a system daemon is not recommended, though.
Not this again... You could have complained about this years ago, but it makes no sense today. PulseAudio got fixed.
> user experience
you can set up PulseAudio for LAN audio streaming with padevchooser (GUI). Could you do this with ESD? Arts? Tell me about this audio streaming solution with super UX for Linux that you know...
Parent seems to have been experimenting this issue recently. Saying "PulseAudio got fixed" does not mean "it works perfectly for everybody" (see https://bugzilla.redhat.com/show_bug.cgi?id=813407 ). Most people will care more about getting a sound system which works without crashing and not sucking up CPU before getting sound system with streaming. The fact that you and me have had a good experience with it does not mean other people are not having issues with it (just as their bad experience may not reflect the overall quality of the software).
That's a Fedora bug. It wouldn't be bleeding-edge (enough!) if it didn't crash. Running Fedora and complaining in a public forum about crashes (without saying the distribution name in the first place!) makes no sense to me.
"you can set up PulseAudio for LAN audio streaming with padevchooser (GUI)."
Yes, and? I understand this is a useful feature for some people, but I'm just interested in listening to music and PA does not me allow to do that without frequent crashes and bugs
I don't care about the features of a car if it stops working at random. And yes, this has happened on every distro I tried since PA started being bundled. Every single distro, every single machine I've had only a stable system with PA OFF
Bugs can be fixed. Pulse is newer than Alsa and more complex, you should expect bugs. If you don't have a problem with the implementation details of PA (software mixing, optional software equalizing, networked audio, stateful audio adaption to devices) then just report the bugs and make it better. Don't whine and try to fragment the Linux space any worse than it already is, especially with Mir's announcement.
The real question is why did you need something newer in the first place ? Are years of bugs, misconfigurations, random crashes worth the minimal improvement end-users will get in the end (when everything finally works for everyone) ?
Yes, pulseaudio has all sorts of awesome esoteric features. You can stream sound transparently from a linux box to a windows one. That's kind of useless if it brings down your computer.
Oh, didn't realize you were asking about the UI specifically. I believe you would just set an environment variable of where you wanted the sound to go.
The part I liked was that you would start ESD and everything just worked.
I conducted an experiment on my last laptop, having noticed PulseAudio taking up more CPU than my media player. I found, quite consistently, that disabling PA led to my media player using more CPU on its own than the sum of the media player and PA when both were running.
I agree with this, I have similar experiences with pulse. I also use the pulse equalizer, which is super easy to set up.
I like it. I think it does things right, and they can optimize it more over time. It is better than having a fast audio subsystem that just can't do what I want. Pulse is a kitchen sink that at least covers its bases.
