From: "Keith Hinton" <keithint38@CommSpeed.net>
To: <speakup@braille.uwo.ca>
Subject: Software speech opinions
Date: Tue, 19 Jun 2007 12:54:06 -0700 [thread overview]
Message-ID: <000c01c7b2ab$984096f0$6401a8c0@YOUR3ADE1B78A3> (raw)
Hi Kirk and all at the Speakup mailing list.
I wanted to express my opinions on Speakup's actual design itself and with
software speech.
First, I hope that Speech-Dispatcher and SpeechD-up (wich are free open
source projects) continue to receive bugfixes in CVS, as much as possible,
and that at some point all SMP related issues are solved. What if some users
need Speech-Dispatcher Hynek eaven after the TTS API provider has been
created and works? I suggest still keeping the project around and improving
it. Not with features, (Speech-Dispatcher is already cool as it is) but that
bugfixes and updates of that type can still be maintained for those who
still wish to use it.
Now, regarding Speakup itself,
I believe Hardware speech is going to be a thing of the passed; especially
with computers becoming USB-connection based, and having nno serial ports.
My new Gateway desktop is a perfect example. Also, most Linux LiveCD's
refuse to use anything but a speakup hardware module, and therefore I wonder
if softsynth should be really the approach here? I have to SSH most Linux
installations from a working software-enabled Speakup machine here on my
network anyways.
So there is still a use for old technology, however
I wonder if Speakup could be patched to work with USB/firewire/newer
synthesizers, and rewrite it's interface so that it uses drivers like
softsynth?
BTW Kirk, where is the documentation for softsynth itself and how that
works? It is not well documented, and I have been wanting to play with
writing my own drivers, and do not have a clear API for Speakup/Sftsyn.
Regards, --Keith
Skype: skypedude1234
next reply other threads:[~ UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton [this message]
` Jan Buchal
` Doug Sutherland
` Gaijin
` Doug Sutherland
` C.M. Brannon
` Travis Siegel
` Glenn Ervin
` Doug Sutherland
` Gaijin
` Gregory Nowak
` Gaijin
` Doug Smith
` Doug Sutherland
` Gaijin
` Glenn Ervin
` Doug Sutherland
` Glenn Ervin
` Steve Holmes
[not found] ` <20070626042409.GA25331@cm.nu>
` Glenn Ervin
` John Heim
` Albert E. Sten-Clanton
` John Heim
` Glenn Ervin
` Scott Berry
` John Heim
` Scott Berry
` Albert E. Sten-Clanton
` Doug Sutherland
` Doug Sutherland
` Glenn Ervin
` John Heim
` Butch Bussen
` John Heim
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='000c01c7b2ab$984096f0$6401a8c0@YOUR3ADE1B78A3' \
--to=keithint38@commspeed.net \
--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).