[pulseaudio-discuss] [V4 PATCH] module-switch-on-connect: add an argument for conditionally connecting

Tanu Kaskinen tanu.kaskinen at linux.intel.com
Sun Sep 28 02:50:54 PDT 2014


On Sun, 2014-09-28 at 12:41 +0300, Tanu Kaskinen wrote:
> On Mon, 2014-09-22 at 11:50 +0800, Hui Wang wrote:
> > On a machine without fixed connecting audio devices like internal
> > microphone or internal speaker, and when there is no external audio
> > devices plugging in, the default source/sink is alsa_input/alsa_output
> > and there is no input devices/output devices listed in the gnome
> > sound-setting.
> 
> How can the default source/sink be alsa_input/alsa_output if there are
> no alsa devices?

Answering myself: probably you meant that there are alsa devices, but
they are currently all unavailable.

> > Under this situation, if we connect a bluetooth headset, the gnome
> > sound-setting will list bluez input/output devices, but they are not
> > active devices by default. This looks very weird that sound-setting
> > lists only one input device and one output device, but they are not
> > active. To change this situation, we add an argument, the policy is
> > if a new source/sink is connected and current default source/sink's
> > active_port is AVAILABLE_NO, we let the new added one switch to
> > default one.
> 
> Surely it doesn't make any sense to have the default sink/source point
> to non-existing devices if there are other devices available. To me this
> seems like something to fix in the core than working around in modules.
> 
> I happen to have some code that improves the core default device
> tracking. I can submit a patch next week. It might fix your issue too.

My code doesn't take the port availability into account (perhaps it
should, I'm not sure), so probably it won't fix your problem.

-- 
Tanu



More information about the pulseaudio-discuss mailing list