Comment 450 for bug 371897

Revision history for this message
In , Ben Shadwick (benshadwick) wrote :

(In reply to comment #333)
> I usually agree with the 'stick to latest versions' thing, but I believe one
> thing should be noted here:
> http://www.alsa-project.org/main/index.php/Main_Page_News
> The official ALSA releases have been kind of rare lately (1 during 2010, and
> the latest being 2011-01-31), so the only way to keep it updated is to actually
> compile it, which can be a problem for those users who don't have a clue on how
> to do it; just think at those who try Linux (mostly Ubuntu) and then find out
> their games/programs aren't working as they expected under Wine (and believe
> me, I've seen way too many of those)...
> I don't want to sound harsh, but unless there's a better way to keep
> alsa-plugins updated (at least to a version that does make the sound work), PA
> shouldn't be considered 'supported through alsa'
That sounds backwards from my understanding of how things work, at least on Ubuntu. I thought that PulseAudio is in charge of everything by default, and when an app (like Wine) thinks it's using ALSA in this setup, it's actually using a wrapper provided by PulseAudio that translates ALSA calls to PulseAudio calls?