Re: pulseaudio related problems....
Le lundi 17 février 2014 à 13:24 +0000, Wookey a écrit :
> The main complaint in this thread seems to be 'my sound worked with
> ALSA, but installing PA stopped/stops it working'. It seems to me that
> PA should try very hard to make sure that whatever output ALSA was using
> before is still used when PA is installed. Is there really no way to
> determine what that was? Somewhere else in this thread someone said 'if
> you have a .asound file then you will lose'. That seems harsh - why
> cannot the config in that be used to ensure PA outputs to whatever is
> 'currently configured'? Shouldn't the presence of such config _help_
> make it find the right output and levels?
Trying to guess what ALSA did and parsing ALSA configuration files
(which can be extremely complex) doesn’t sound like a recipe to write
reliable software.
I think the solution is to make PulseAudio more clever about default
output selection:
* video output being HDMI is an indication you should use HDMI →
this is very complex to implement since it requires integration
with X
* some devices appear in the system but are not actually connected
to something, maybe we can blacklist them
* PA can expose bugs in kernel drivers that did not appear when
you did not use the advanced features (e.g. latency control)
None of this is simple, but if we have to make something complex, it
should be the correct solution rather than trying to mimic what ALSA did
before.
> I am nearly as clueless as Mr Tille about audio and have also
> experienced regular problems with no output, no input, wrong audio card,
> vol sliders at zero, but I don't know to what degree PA is any worse than
> ALSA. I had got the hang of ALSAmixer, just in time for it to no longer
> solve my problems. The problem with PA seemed to be an extra layer of
> 'magic' which was great if it picked the right things, but useless if it
> didn't. This thread helped me discover 'pavucontrol' which seems to be
> the thing that exposes the 'magic' in question, and has enabled me to
> get mic + hangouts working reliably (audio out was already working).
KDE/GNOME users have been mostly unaffected since the volume control
application handled both setups for a while, and now relies completely
on PulseAudio (at least for GNOME).
When you have trouble with sound, at first:
* Click on the volume icon
* Click on the “volume control” button
* Select the HDMI or analog device, and set a few options
I don’t think it’s unreasonable to expect the user to follow that
workflow.
--
.''`. Josselin Mouette
: :' :
`. `'
`-
Reply to: