[pulseaudio-discuss] Why no 'default device' option?
ngoonee at gmail.com
Thu Nov 26 01:11:53 PST 2009
On Thu, 2009-11-26 at 08:42 +0000, Colin Guthrie wrote:
> 'Twas brillig, and Jeremy Nickurak at 25/11/09 20:37 did gyre and gimble:
> > On Wed, Nov 25, 2009 at 11:48, Colin Guthrie <gmane at colin.guthr.ie
> > <mailto:gmane at colin.guthr.ie>> wrote:
> > PA will always remember what your app has chosen. So if you play
> > something with an app for the very first time, it is assigned to the
> > fallback device (we know no better).
> > Is this the case even if you don't manually select one? Ie, the first
> > time it's used, it uses the "fallback" device. The second time, does it
> > still go to the "fallback", or does it go to the same device it
> > "fell-back" to last time?
> > I'm hoping it's the former, in which case... what is the difference
> > between a fall-back device and a default-device?
> Well, there is a save_sink flag we set when we are supposed to save the
> sink... it's a little confusing and I've not fully groked the code, but
> it should only be set when the user has specifically moved the stream.
> However, I'm not 100% sure that is the case right now.
> I'd have to look at the code to answer 100% here, but certainly the
> intention is that the sink is only saved if the user has actively moved
> the sink (e.g. calls the appropriate API command).
I can confirm that on my setup (0.9.19) the sink for an app (take mpd
for example) is only saved if I manually move it. So say I have on-board
sound and a BT headset connected, I move the mpd output to the BT
headset. Then I disconnect the BT headset and the mpd output falls back
to on-board. Even if I restart PA/the machine repeatedly, as long as I
don't specifically assign the mpd output to any other sink, as soon as
connect my BT headset it moves to the BT sink.
More information about the pulseaudio-discuss