[pulseaudio-discuss] pulseaudio and espeakup (fwd)

[Jude DaShiell]

Pulseaudio and speakup fight and speakup looses badly.  By fighting I 
mean once both run speakup allows for a user to log in then shortly 
after that login speech comes out strangled to the point it's no longer 
understandable and volume of speech is also decreased.  The 
speech-dispatcher package may also be involved in this fight depending 
on which accessibility distro you install.  Turning speakup off and 
turning speakup back on does not solve this problem either.  If anyone 
is interested and has vm space or hard drive space available, you could 
download and install slint latest version from sourceforge.net and 
install slint with speech enabled and choose console startup rather than 
graphical startup to find out directly what in one instance what is 
happening.  Just be aware slint is systemv not systemd.  If you want to 
see what happens in debian hit the s as a boot parameter on its 
installation to install debian with accessibility.  Debian of course has 
debian-accessibility at lists.debian.org from which further discussion of 
their issue will emanate.  My context for all of this is I'm retired so 
have the time needed; I have never seen anything in this life so have 
need of screen readers, I find windows too unstable to use in a home 
environment without technical support since windows is not a 
self-healing system, and I test linux distributions for accessibility 
that want to have accessibility or claim to have accessibility and I try 
to support the linux accessibility community with reports when I find 
things out.

On Wed, 3 Jan 2018, Georg Chini wrote:

> Date: Wed, 3 Jan 2018 12:23:27
> From: Georg Chini <georg at chini.tk>
> To: General PulseAudio Discussion <pulseaudio-discuss at lists.freedesktop.org>,
>     Jude DaShiell <jdashiel at panix.com>, pulseaudio-discuss at freedesktop.org
> Subject: Re: [pulseaudio-discuss] pulseaudio and espeakup (fwd)
> 
> On 03.01.2018 18:09, Jude DaShiell wrote:
>> 
>>
>>  ---------- Forwarded message ----------
>>  Date: Wed, 3 Jan 2018 12:05:21
>>  From: Samuel Thibault <sthibault at debian.org>
>>  To: Alex ARNAUD <alexarnaud at hypra.fr>
>>  Cc: pkg-pulseaudio-devel at lists.alioth.debian.org,
>>  debian-accessibility at lists.debian.org
>>  Subject: Re: pulseaudio and espeakup
>>  Resent-Date: Wed,? 3 Jan 2018 17:05:39 +0000 (UTC)
>>  Resent-From: debian-accessibility at lists.debian.org
>>
>>  Hello,
>>
>>  Alex ARNAUD, on sam. 30 d?c. 2017 11:21:35 +0100, wrote:
>>>  A possible solution could be to enable to emit sound from TCP or Unix
>>>  socket as described here:
>>>  http://billauer.co.il/blog/2014/01/pa-multiple-users/
>>
>>  I thought about it indeed, I'm just afraid it's quite involved.
>>
>>>  It seems it's not only a accessibility issue because a computer could be
>>>  used by multiple users and in some situations sighted users encounter
>>>  this
>>>  problem also.
>>
>>  Yes, and such a solution needs cooperation with the pulseaudio
>>  maintainers anyway, we can't tinker something without synchronization.
>>
>>>  I'm not sure removing PulseAudio is a good idea. As I understand New
>>>  Firefox
>>>  releases require PulseAudio to emit sound.
>>
>>  Oh right, so we have to bite the itch anyway.
>>
>>>>  We really need to fix this (and I'm really depressed that it seems
>>>>  nobody took the time to manage to work out a solution).
>>>
>>>  I agree with you on this particular point but you couldn't miss the
>>>  contribution of Paul and Jeremy on accessibility team on packaging that
>>>  could allow you to focus on more complicated tasks you seems to be aware
>>>  of.
>>
>>  Sure, I'm really glad to see things happening, thanks a lot to the
>>  contributors :D
>>
>>  I was just thinking about accessibility in general, AIUI the problem
>>  is generally known since quite a long time, and AFAIK some discussions
>>  happened somewhere on some pulseaudio lists but without actual
>>  conclusions and solutions, while this does not seem to be a so technical
>>  issue like Debian packaging is, so a lot of people could have led the
>>  discussion.
>>
>>  Samuel
>
> Unfortunately the mail does not state what the problem is. Could you please
> elaborate?
>
>

--