<br><br><div class="gmail_quote">On Tue, Oct 20, 2009 at 14:16, Daniel Chen <span dir="ltr"><<a href="mailto:seven.steps@gmail.com">seven.steps@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">On Tue, Oct 20, 2009 at 3:20 PM, Jeremy Nickurak<br> <<a href="mailto:pulseaudio-discuss@trk.nickurak.ca">pulseaudio-discuss@trk.nickurak.ca</a>> wrote:<br> > Maybe the distributions broke it, and have never really fixed it (Ubuntu<br> > certainly isn't following the "Perfect Setup" advice, even in karmic AFAICT.<br> > Audio goes to pulse if and only if it the app expressly requests a<br> > connection to the pulseaudio daemon, which of course causes problems)<br> <br> </div>While Ubuntu has done really bad things[0], Luke and I really don't<br> intentionally break anyone's audio. In fact, since Jaunty/9.04, all<br> audio in Ubuntu is routed through PulseAudio (in Ubuntu, cf.<br> /usr/share/alsa/pulse*). (The bits were there for Intrepid/8.10, but<br> the integration arguably was shabby.)<br></blockquote><div><br>Is this actually the case? I've always modified /etc/asoundrc or ~/.asoundrc to get applications working as expected, but maybe that's redundant now. <br> </div></div>