Re: Flushing issue (was: So, where'd the volume controls get to?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Oct 11, 2020 at 01:53:55AM +0200, Samuel Thibault wrote:
> Ok but isn't it getting interrupted by the next key press also very
> fast?
> 
> Making the rate to 9 and running less on a long text, then keeping the
> down key pressed, I do get gibberish speech indeed, since it basically
> tries to speak the first words of each line very fast before the next
> key press switches to the next line. But what else would be expected?

Ok. I've just put up with this for the last two or three years, and
assumed that others either weren't experiencing this, or were just
putting up with it like me. If this can actually be gotten rid of
though, that would make software speech nice to use again. Here's how
to reproduce. I'm testing on a devuan Beowulf system, which is based
on debian buster. I have no pulseaudio installed, though as far as I
can tell, this is still the same with or without pulseaudio
running. This is specific to espeakup for me, it doesn't happen with
speechd-up, or with a hardware synthesizer. The espeakup version is
1:0.80-15, the espeak-ng version is 1.49.2+dfsg-8. 

1. modprobe speakup_soft

2. Start espeakup. I do this with

service espeakup start

3. Set speakup rate to 7 or 8, I have it set to 7.

4. Open the sound card with another application. This can be orca,
   aplay, mplayer, and probably something else too. The other sound
   source doesn't need to actually be playing something. It could be
   simply orca loaded in the GUI and ready to speak, or a file paused
   in mplayer. The sound device just needs to be opened and held ready
   for use by something else.

5. Load a screen full of content, man espeakup should be as good as
   anything.

6. Move to top of screen with speakup+9. Move down the screen with
   numpad 9, the speakup say next line command. Let the line read for
   the first few words, and press numpad 9 again to move to next
   line. What you should hear is that espeak doesn't finish reading
   the current line before the next line starts to speak. This causes
   the two speech chunks to overlap, making it difficult to hear the start
   of the next line of text.

I hope this demonstrates the issue. If there are other questions,
please ask.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@xxxxxx
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup



[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]

  Powered by Linux