public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Mark Peveto <southernprince73@gmail.com>
To: Samuel Thibault <sthibault@debian.org>
Cc: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>,
	debian-accessibility@lists.debian.org
Subject: Re: [HEADS-UP] Please test Re: Speech overlapping with espeak-ng
Date: Mon, 23 Jan 2017 14:22:24 -0600 (CST)	[thread overview]
Message-ID: <alpine.LNX.2.20.999.1701231419510.1393@purrwurr> (raw)
In-Reply-To: <20170123122103.GG1283@var.bordeaux.inria.fr>

Samual,
I don't have a lot in the way of technical knowledge, but I can try to help you test.  What do you need?  I don't use brltty, so if that's what you're
lookin for I might not be much help.


Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!

On Mon, 23 Jan 2017, Samuel Thibault wrote:

> Hello,
>
> Could people really please test these brltty and espeakup packages?
>
> In short: if I don't get feedback very soon, I'll have to revert them to
> espeak for Stretch, which would be very sad.
>
> If there is something preventing from doing the tests, please tell, I
> can't guess it.
>
> Since the migration to espeak-ng poses strong problems, we *have* to
> fix them before the release. If people don't actually test the fixes,
> there's no way we can be sure that things are alright. I did test these
> packages, but since I'm no speech user, I can't have a good idea of what
> *sounds* right.
>
> We have to decide very soon what to do for the next Debian release,
> Stretch. The full freeze is 5th February, we can't introduce big
> changes after that date, plus the 10-day migration period, it basically
> means we have to decide by 25th January. If I don't get reports saying
> that brltty 5.4-5 and espeakup 0.80-4 are now good, I'll revert to
> espeak by 25th January.
>
> To make testing yet easier, I have uploaded the packages to be tested
> (brltty 5.4-5 and espeakup 0.80-4) into experimental. They are now
> already available with:
>
> deb http://incoming.debian.org/debian-buildd buildd-experimental main
>
> Please test!
>
> Samuel
>
>
> Samuel Thibault, on Sun 15 Jan 2017 15:57:48 +0100, wrote:
> > I have uploaded to
> >
> > http://people.debian.org/~sthibault/tmp/
> >
> > a version of espeakup which introduces a 150ms delay after the cancel.
> > This should be small enough to keep reactivity, but long enough to
> > clearly separate speech. You can tune this value with the additional -c
> > parameter.
>
> Samuel Thibault, on Sun 15 Jan 2017 16:19:55 +0100, wrote:
> > I have uploaded brltty packages on
> >
> > http://people.debian.org/~sthibault/tmp/
> >
> > too. The delay can be changed with the cancel_pause espeak parameter,
> > e.g.:
> >
> > /sbin/brltty -S cancel_pause=150 blabla...
> >
> > or
> >
> > speech-parameters es:cancel_pause=150
> >
> > Could people give a try to these packages, and see which value of the
> > cancel pause they prefer?
>
> Samuel
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

      parent reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Samuel Thibault
 ` Samuel Thibault
 ` Hart Larry
 ` [HEADS-UP] Please test " Samuel Thibault
   ` Samuel Thibault
     ` Samuel Thibault
       ` [HEADS-UP] Please test?Re: " Tom Fowle
         ` Samuel Thibault
     ` [HEADS-UP] Please test " Øyvind Lode
     [not found]       ` <20170123134123.gxnmb3spvq45ymrk@Kraftkrust>
         ` Øyvind Lode
         ` [HEADS-UP part 2] " Samuel Thibault
           ` Al Sten-Clanton
             ` Samuel Thibault
               ` Al Sten-Clanton
     ` [HEADS-UP] " Kirk Reiser
       ` Samuel Thibault
   ` Mark Peveto [this message]

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=alpine.LNX.2.20.999.1701231419510.1393@purrwurr \
    --to=southernprince73@gmail.com \
    --cc=debian-accessibility@lists.debian.org \
    --cc=speakup@linux-speakup.org \
    --cc=sthibault@debian.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).