User: Password:
|
|
Subscribe / Log in / New account

The unveiling of kdbus

The unveiling of kdbus

Posted Jan 25, 2014 0:01 UTC (Sat) by makomk (guest, #51493)
In reply to: The unveiling of kdbus by raven667
Parent article: The unveiling of kdbus

PulseAudio now, in 2014, is still bad enough that I'm seriously considering switching back to Windows after almost a decade of primarily running Linux just so that I don't have to suffer through dealing with it anymore. If anything, it's managed to develop new forms of brokenness over the years. For example I have all kinds of fun issues with it crashing randomly or using 100% CPU or randomly mangling audio output until I kill and restart it which weren't there a few years ago. (I'm 80% sure the code in the PulseAudio daemon that supports volume meters is plain wrong in a way that causes random crashes, but all the comments are missing and the variable names misleading so it's impossible to tell - and that's after reverting an optimisation in the latest official release that was included despite being literally incomplete and breaking it further.) Oh, and naturally restarting PulseAudio for any reason randomly kills all sound output in many applications until they're restarted.

Likewise, flat volumes breaks in random and amusing new ways with every version, and I've never encountered any of the mythical hardware it actually works on without annoying pops and glitches and random bursts of excessively loud audio when an app starts or exits. Hell, I've even tried it on hardware with no hardware volume control at all and somehow it still managed to screw that up by trying to adjust the non-existent hardware volume control - so lowering the application volume level had no effect until suddenly it muted the output entirely. So far as I can tell, the entire feature relies on hardware behaving in ways that isn't part of any specification and cannot ever be relied on. Though at least that can be disabled if you edit the right obscure configuration file as root.


(Log in to post comments)

The unveiling of kdbus

Posted Jan 25, 2014 1:07 UTC (Sat) by pizza (subscriber, #46) [Link]

> PulseAudio now, in 2014, is still bad enough that I'm seriously considering switching back to Windows after almost a decade of primarily running Linux just so that I don't have to suffer through dealing with it anymore.

I counter your anectdote with one of my own; half a dozen or so systems over as many years, all working without an audio-related hitch. All using bog-standard onboard AC97 or HD Audio codecs.

So, what applications are having problems? What were already streaming? What pulseaudio version? What hardware? Have you filed any bug reports?

The unveiling of kdbus

Posted Jan 27, 2014 22:50 UTC (Mon) by nix (subscriber, #2304) [Link]

I do have one problem, and it's an annoying one. When programs try to adjust the master volume themselves, PA automatically tweaks all the per-application volumes to compensate -- but when you try to move the master volume back down (in e.g. pavucontrol) the per-application volumes are all reduced, so you have to tweak them up by hand: system boots restore the master volume to a consistent level, but do not change the per-application volumes. The net effect is that every system reboot followed by e.g. a QEMU startup halves the volume of every application playing sound at that time. This is not sane behaviour :(

The unveiling of kdbus

Posted Jan 28, 2014 1:22 UTC (Tue) by paulj (subscriber, #341) [Link]

Ah, this behaviour of PA drives me batty - so it's not just me? I'm never quite sure what is going to happen with the volume when I adjust it. :(

The unveiling of kdbus

Posted Jan 28, 2014 2:19 UTC (Tue) by mathstuf (subscriber, #69389) [Link]

This sounds like flat-volumes. I have this in my .config/pulse/daemon.conf:

> flat-volumes = no

Try and see if that fixes it.

The unveiling of kdbus

Posted Jan 29, 2014 23:35 UTC (Wed) by nix (subscriber, #2304) [Link]

The thing is, I *like* flat volumes in all other respects. It's just that I wish programs that modified the master volume could be faked into adjusting only their own per-app volume instead. The master volume is the user's, and no app should be allowed to fiddle with it.

The unveiling of kdbus

Posted Jan 29, 2014 23:55 UTC (Wed) by mathstuf (subscriber, #69389) [Link]

I wonder if an option in PulseAudio to enforce that behavior would be accepted by upstream. It doesn't sound like an awful plan. The question, I guess, is how do you change the master volume then? pacmd?

The unveiling of kdbus

Posted Jan 30, 2014 0:49 UTC (Thu) by nix (subscriber, #2304) [Link]

I'm using pavucontrol... but in general whatever the desktop environment uses to control the master volume should change it: random programs shouldn't futz about with it, particularly not if there's no easy way for the user to reverse what they did. (If I as a user change the master volume in pavucontrol, everything changes volume -- i.e. it does *not* automatically shift the volume of everything else to compensate. So errant programs can do things I cannot reverse.)

The unveiling of kdbus

Posted Jan 25, 2014 4:18 UTC (Sat) by raven667 (subscriber, #5198) [Link]

PA has been stable for a long time now, I would guess there is something interesting about your hardware or your config and the PA developers would grateful if you worked with them to figure out what it is.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds