Hey Kirk, I hope you and the family are all well. As I noted, I can use the keyboard, to have speakup play the line change tones while using review by word, so that's not it. I'm guessing there's some problem in espeakup or speakup_soft. I'll update a buster system to use a 5.10 kernel and see what happens. Be well, --FC > On Dec 15, 2021, at 12:37 PM, Kirk Reiser <kirk@xxxxxxxxxx> wrote: > > Hi Frank: Yes, I've noticed the problem. My guess is they've lowered > the keyboard interrupt priority so it doesn't get recognized until all > output is complete. That's just a guess however and yes it is > iritating as hell. > > Kirk > > On Wed, 15 Dec 2021, Frank Carmickle wrote: > >> Hi all, >> >> I've been noticing a problem with speakup/espeakup/espeak-ng, across kernels 5.10 5.14 and now 5.15. When I write a lot of output to a screen, say dmesg without a pager, screen review stops working for a few seconds. I know speakup is still responding because the tones are played when navigating by word when moving to a new line. The speech is interrupted appropriately but it will not speak again for a few seconds. >> >> Has anyone else experienced this? Does anyone have an idea of where to look to help sort this out. >> >> I very much liked the former functionality of being able to press a key to momentarily flush the buffer and pick up reading the screen immediately. >> >> Thanks all, >> --FC >> >> >
