Georg, Tanu, and others,

On Tue, Apr 30, 2019 at 2:35 PM Georg Chini <ge...@chini.tk> wrote:

> On 27.04.19 12:26, Tanu Kaskinen wrote:
> > On Fri, 2019-04-26 at 07:37 -0500, Matt Zagrabelny wrote:
> >> On Fri, Apr 26, 2019 at 4:28 AM Tanu Kaskinen <ta...@iki.fi> wrote:
> >>
> >>
> > In /usr/share/pulseaudio/alsa-mixer/paths/analog-output-
> > headphones.conf, change these lines:
> >
> > [Jack Front Headphone]
> > required-any = any
> >
> > to
> >
> > [Jack Front Headphone]
> > required-any = any
> > state.plugged = unknown
> > state.unplugged = unknown
> >
> > and similarly in /usr/share/pulseaudio/alsa-mixer/paths/analog-output-
> > lineout.conf change these lines:
> >
> > [Jack Line Out Front]
> > required-any = any
> >
> > to
> >
> > [Jack Line Out Front]
> > required-any = any
> > state.plugged = unknown
> > state.unplugged = unknown
> >
> > These changes will be overwritten whenever your distribution updates
> > pulseaudio (yes, this sucks, hopefully this will be improved some day;
> > I think George Chini already has something prepared related to
> > disabling jack detection).
> >
> Yes, once the messaging API patches are merged, I have at
> least patches that provide the basic infrastructure to disable
> jack detection on the fly.
>

How are the messaging API patches coming along?

I happened to upgrade this computer the other day and was reminded of this
thread.

Any PA updates for disabling jack detection on the fly?

Thanks for your work in PA and help here, too.

-m
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

Reply via email to