public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: Flushing issue (was: So, where'd the volume controls get to?)
Date: Sun, 11 Oct 2020 01:53:55 +0200	[thread overview]
Message-ID: <20201010235355.uqqvyyjqxupfw5qw@function> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2010101905240.36490@befuddled.reisers.ca>

Kirk Reiser, le sam. 10 oct. 2020 19:17:42 -0400, a ecrit:
> In fact, if I just hold down the previous-lineor next-line keys it
> still reads bits of the screen as it's going up or down. I tried to
> type fast enough to not get any speech but couldn't do it. It almost
> speaks immediately when I press the key or fast enough I can't tell
> the difference.

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?

> the libespeak library as reported by ldd is:
> 
> libespeak.so.1 => /usr/lib/x86_64-linux-gnu/libespeak.so.1 (0x00007f6298

That is not precise enough, that has never changed since the espeak
times. The last version of espeak-ng I'm aware of is 1.50.

Samuel

  reply	other threads:[~ UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 So, where'd the volume controls get to? Kirk Reiser
 ` Chime Hart
 ` Samuel Thibault
   ` Alexander Epaneshnikov
     ` Chime Hart
   ` Kirk Reiser
     ` Samuel Thibault
       ` Kirk Reiser
         ` Gregory Nowak
           ` Gregory Nowak
       ` Gregory Nowak
         ` Kirk Reiser
           ` Karen Lewellen
             ` Samuel Thibault
               ` Karen Lewellen
                 ` Samuel Thibault
                   ` Karen Lewellen
                     ` Tyler Spivey
                       ` Didier Spaier
     ` Flushing issue (was: So, where'd the volume controls get to?) Samuel Thibault
       ` Kirk Reiser
         ` Samuel Thibault [this message]
           ` Flushing issue Tyler Spivey
             ` Samuel Thibault
           ` Flushing issue (was: So, where'd the volume controls get to?) Kirk Reiser
             ` Samuel Thibault
               ` Kirk Reiser
           ` Gregory Nowak
             ` Chime Hart
             ` Samuel Thibault
               ` Samuel Thibault
                 ` Samuel Thibault
                 ` Gregory Nowak
                 ` Gregory Nowak
     ` So, where'd the volume controls get to? Chime Hart
 ` Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201010235355.uqqvyyjqxupfw5qw@function \
    --to=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).