From: Glenn <glennervin@cableone.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: Are the days of hardware synths and speaking from boot numbered?
Date: Wed, 12 Dec 2012 09:14:12 -0600 [thread overview]
Message-ID: <D481676FF7A94DBABCAD932F8A26AF1D@your2c061f0461> (raw)
In-Reply-To: <ka97sr$r06$1@ger.gmane.org>
I am awaiting my raspberry Pi. I have a Decktalk serial, and I'm sure that
I have a USB to serial adapter around here.
I will have to find out how to get that set up.
Glenn
----- Original Message -----
From: "Jason White" <jason@jasonjgw.net>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, December 12, 2012 12:23 AM
Subject: Re: Are the days of hardware synths and speaking from boot
numbered?
Arthur Pirika <speakup@linux-speakup.org> wrote:
>I think the subject pretty much speaks for itself. With serial
>synths, and especially serial ports getting harder to find, with the
>only serials synths still being made new are the venerable doubletalks,
>should work be ramped up on getting software speech, somehow at kernel
>level?
There are very cheap Linux-based machines available now, Raspberry Pi for
example. You could buy one, install your speech synthesis software of choice
on it, add a USB to serial adapter, write a small program to process
incoming
speech commands and text over the serial port and you thereby have your own
"hardware" synthesizer. The price is probably less than what you would pay
for
a commercial product.
You could even do it via Ethernet rather than a serial port, although in
that
case you would still need something on the client side that would start as
early in the boot process as desired.
Most (all?) server and workstation boards have serial ports built in, and
there are USB to serial adapters available too, so I don't think serial
ports
should be a major issue.
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Arthur Pirika
` mattias
` deedra waters
` Gregory Nowak
` Arthur Pirika
` Tony Baechler
` covici
` mattias
` acollins
` John G. Heim
` Kyle
` Alex Snow
` Albert Sten-Clanton
` Jason White
` Glenn [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=D481676FF7A94DBABCAD932F8A26AF1D@your2c061f0461 \
--to=glennervin@cableone.net \
--cc=glennervin@gmail.com \
--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).