Re: Overlapping speech with brltty and espeak-ng again

[Eric Scheibler <email@eric-scheibler.de>]

I think, that I found the cause of the overlapping.

I disabled lightdm on startup. Therefore my notebook initially loads no GUI, no orca and no speech
dispatcher. Instead only brltty is available on tty1, which I use with brltty-espeak. And then,
everything works like expected. Then I start mate and orca and the overlapping begins.

So I searched for running speech-dispatcher instances with:
ps axo user,pid,command | grep -i speech

and found:
eric      7478 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf
eric      7480 /usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf
eric      7485 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf
eric      7487 /usr/bin/speech-dispatcher --spawn --port 6560 --socket-path /run/user/1000/speech-dispatcher/speechd.sock --communication-method unix_socket

Then I killed all speech dispatcher instances:
pkill speech-dispatch

and the overlapping is gone again and brltty works with espeak-ng like a charm.

Then I tested the following from tty1:
spd-say hello

Speech dispatcher speaks "hello" and the overlapping is back again.

The process monitor lists:
eric      7093 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf
eric      7095 /usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf
eric      7100 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf
eric      7102 /usr/bin/speech-dispatcher --spawn --communication-method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock

But in this case speech dispatcher quits automatically after 4-5 seconds and the overlapping is gone
with it. Seems, that the slightly different run options are responsible for that. If I use orca
again, then same result like above.

Conclusion: The overlap-bug only occurs as long as a speech dispatcher instance is running.
Question is: Should the speech dispatcher always be active and the bug lies there or is orca
responsible for the issue, cause it runs the speech dispatcher and never kills it afterwards?

Installed packages
brltty                                5.4-7
brltty-espeak                         5.4-7
espeak-ng                             1.49.0+dfsg-10
espeak-ng-data:amd64                  1.49.0+dfsg-10
espeak-ng-espeak                      1.49.0+dfsg-10
libespeak-ng1:amd64                   1.49.0+dfsg-10
speech-dispatcher-espeak-ng           0.8.6-4

/etc/default/speech-dispatcher
RUN=no

/etc/speech-dispatcher/speechd.conf
DefaultModule espeak-ng
AudioOutputMethod "libao"       # tested with alsa too

Cheers
Eric