On Thu, Nov 5, 2009 at 3:31 PM, Dima Ryazanov <email address hidden> wrote:
> So you're saying PA won't work unless ALL applications suddenly start
> using PA rather than ALSA? Isn't this a bit unrealistic?
No, I'm saying that applications must be configured such that they
don't think they're the only things that are important. mpd ships one
such configuration, using hw:0,0 instead of dmix:0. hw:0,0 is *bad*,
because it essentially blocks other apps from working.
In the best of all worlds, PA will coexist with apps configured to use
dmix/dsnoop, which means that PA needs to use dmix/dsnoop, and that
isn't blessed by upstream. However, it is one migration path. [This is
a significant difference to PA upstream, since I do believe that user
experience is important, and while people continue to use ALSA
natively without PA, PA needs to be configured to use dmix/dsnoop. But
I'm not going to break everyone further.]
On Thu, Nov 5, 2009 at 3:31 PM, Dima Ryazanov <email address hidden> wrote:
> So you're saying PA won't work unless ALL applications suddenly start
> using PA rather than ALSA? Isn't this a bit unrealistic?
No, I'm saying that applications must be configured such that they
don't think they're the only things that are important. mpd ships one
such configuration, using hw:0,0 instead of dmix:0. hw:0,0 is *bad*,
because it essentially blocks other apps from working.
In the best of all worlds, PA will coexist with apps configured to use
dmix/dsnoop, which means that PA needs to use dmix/dsnoop, and that
isn't blessed by upstream. However, it is one migration path. [This is
a significant difference to PA upstream, since I do believe that user
experience is important, and while people continue to use ALSA
natively without PA, PA needs to be configured to use dmix/dsnoop. But
I'm not going to break everyone further.]