Sebastian Humenda, on Thu 09 Feb 2017 10:23:36 +0100, wrote: > Samuel Thibault schrieb am 08.02.2017, 23:49 +0100: > >Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote: > >> I'm not sure whether the issue is actually in BRLTTY or espeak-ng, but > >> I couldn't encounter any issues while using speech-dispatcher with > >> espeak-ng yet. > > > >Ok. I'm afraid that might be an issue with the way BRLTTY uses espeak > >and espeak-ng behaves: BRLTTY sets a callback, but espeak-ng calls it > >from its own thread, which may pose some unexpected issues. Could you > >try the attached patch? > I've applied the patch and BRLTTY still runs fine. It's a bug which occurs > irregularly, so it's hard to tell whether the issue is fixed.
Sure, let's see how it goes. > >It may cripple BRLTTY functionalities a bit, but at least potentially make it > >more robust for Stretch, and we'll have a closer look upstream. > What exactly do you mean by "cripple"? Well, I don't know precisely actually. See the SynthCallback function, it seems to be looking at espeakEVENT_WORD for tracking speak with braille, and espeakEVENT_MSG_TERMINATED for some management which I don't understand with just a quick look, but didn't seem to be too problematic. Much less than a crash, anyway :) Samuel
