From: "Nick Stockton" <nstockton@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Which hardware synthesizer to buy?
Date: Fri, 10 Apr 2009 15:46:35 -0700 [thread overview]
Message-ID: <30152AF4D1A949B395C54C238437D5FF@golly> (raw)
In-Reply-To: <20090410212552.GA15942@clearwire.net>
If you want a new hardware synth, your choices are: the DoubleTalk LT for
$200, the TrippleTalk USB for $500 or the DecTalk USB for $700.
The DoubleTalk and TrippleTalk both use the same RC8650 chipset and they
should sound like your LiteTalk.
Since speakup doesn't support USB connections to the synth, if you get a
TrippleTalk USB or DecTalk USB you will need to run the synth in serial mode
and connect it to the computer using a serial cable.
I wouldn't go with the DecTalk USB unless you really like DecTalk speech.
The DecTalk is very pricy and the DoubleTalk and TrippleTalk synths are more
responsive and tend to be better supported by speakup.
Kerk will have to comment here but I think I remember him saying he was
using a TrippleTalk.
Nick Stockton
----- Original Message -----
From: "Gaijin" <gaijin@clearwire.net>
To: "SpeakUP Mailing List" <speakup@braille.uwo.ca>
Sent: Friday, April 10, 2009 2:25 PM
Subject: Which hardware synthesizer to buy?
> So, which synthesizer works with speakup these days. It sounds
> like my LiteTalk serial and Mike's Apollo are no longer viable, and the
> DecTalk still requires special software to work. Which model out there
> still works without a hitch, or which synthesizer is Kirk using? I
> figure if something crops up with Kirk's synthesizer, I figure it'll be
> the first one to get the "Oops! Better not do that," treatment. Anyone
> know which squeaky wheels are getting the grease, or is speakup
> gradually losing it's "from power-up to shutdown" capability with the
> software synth? I have enough set aside to get another synthesizer, and
> would rather drop the LiteTalk. Maybe then I can work with the newer
> kernels. How about it, Kirk? Which hardware synthesizer do you use?
>
> Michael
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ Information from ESET Smart Security, version of virus
> signature database 3994 (20090407) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
Gaijin
` Nick Stockton [this message]
` Gaijin
` Kirk Reiser
` John covici
` al Sten-Clanton
` Gregory Nowak
` William Hubbs
` John covici
` William Hubbs
` John covici
` Gregory Nowak
` William Hubbs
` Chris Brannon
` Gregory Nowak
` Chris Brannon
` Gregory Nowak
` Alex Snow
` virtualization, was: " Gregory Nowak
` Alex Snow
` Gregory Nowak
` Gaijin
` Garrett Klein
` Janina Sajka
` Gaijin
` William Hubbs
` Tony Baechler
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=30152AF4D1A949B395C54C238437D5FF@golly \
--to=nstockton@gmail.com \
--cc=speakup@braille.uwo.ca \
/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).