[pulseaudio-discuss] [PATCH 0/3] Suspending loopback

Tanu Kaskinen tanu.kaskinen at digia.com
Fri May 4 02:33:25 PDT 2012

On Fri, 2012-05-04 at 11:11 +0200, Dalleau, Frederic wrote:
> Hi Tanu,
> On Fri, May 4, 2012 at 6:23 AM, Tanu Kaskinen <tanuk at iki.fi> wrote:
> > On Thu, 2012-05-03 at 18:17 +0200, Frédéric Dalleau wrote:
> > About the third patch - do you have module-suspend-on-idle loaded? If
> > so, why doesn't it suspend the source? If the source doesn't go to the
> > IDLE state when all its outputs are corked, then that's a bug. If the
> > source does go to the IDLE state, but module-suspend-on-idle doesn't
> > suspend it, then that's a bug too.
> >
> That's chicken egg problem, the source never goes to idle because
> the loopback has a source-ouput using it. And the source-output is not corked
> because the source is not suspended.

Ah, right, I understood the point of the third patch wrong. So the
scenario is that the bluetooth state changes from PLAYING to CONNECTED
without Pulseaudio asking for it? What's the use case? Does it mean that
while the device supports the A2DP_SOURCE profile, it's not usable right
now? I think changing the card profile to "off" would be the right
reaction. Ideally the routing policy would get a signal that "this port
is not available right now, but it's worth trying again later", but
there's no infrastructure for that yet.


More information about the pulseaudio-discuss mailing list