pulseaudio and espeakup

[Jude DaShiell]

Perhaps lost or dropped might provide some interesting reading.

On Fri, 2 Feb 2018, Samuel Thibault wrote:

> Date: Fri, 2 Feb 2018 14:27:23
> From: Samuel Thibault <sthibault at debian.org>
> To: debian-accessibility at lists.debian.org,
>     pkg-pulseaudio-devel at lists.alioth.debian.org,
>     Scott Leggett <scott at sl.id.au>
> Subject: Re: pulseaudio and espeakup
> Resent-Date: Fri,  2 Feb 2018 19:28:07 +0000 (UTC)
> Resent-From: debian-accessibility at lists.debian.org
> 
> Hello,
>
> Samuel Thibault, on sam. 06 janv. 2018 14:45:04 +0100, wrote:
>> Scott Leggett, on sam. 06 janv. 2018 23:47:42 +1100, wrote:
>>> can deal with devices being assigned to them and going away.
>>
>> It seems promising but I need more details. At which layer does this
>> happen? Does pulseaudio have hooks for this? I.e. espeakup would provide
>> hooks for relieving the audio device when pulseaudio feels the need to?
>> It seems to me that it's the kind of approach which would work.
>
> I haven't had any feedback on this.  What is meant by "assigned to them
> and going away"?  Which pulseaudio functions implements this?  I have
> looked for "going", "away", "destroy", etc. in the pulseaudio headers (I
> didn't find any other documentation in the source package), to no avail.
>
> Do you have ideas on which keywords I should look for in pulseaudio?
> (I'm fine with diving in the source coed, I'd just rather not start
> without any clue what to look for)
>
> Samuel
>
>

--