From: "Glenn Ervin" <GlennErvin@cableone.net>
To: <speakup@braille.uwo.ca>
Subject: Re: a bit of trivia I found interesting
Date: Thu, 19 Dec 2002 19:15:44 -0600 [thread overview]
Message-ID: <003401c2a7c5$521810e0$be00a8c0@default> (raw)
In-Reply-To: <20021219024936.GA697@romuald.net.eu.org>
I wish someone would create a Linux kernel for the BNS, as I do not like
its OS too much, and there are no drivers for external devices other
than what FS sells, like their over priced disk drives.
----- Original Message -----
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, December 18, 2002 8:49 PM
Subject: Re: a bit of trivia I found interesting
Actually, I personally think that the accent sounds like crap, and the bns
sounds wonderful. Whenever I listen to the accent, I can't help the notion
that it is better suited for speaking French instead of English.
I have known for a while that the bns used the si 263 chip. I had also
suspected that the accent used the same speech chip as the bns because of
how they both sounded on head phones, but wasn't absolutely sure.
What I think makes the difference is how the chip is controlled by the
software.
Greg
On Wed, Dec 18, 2002 at 07:55:53PM -0600, Adam Myrow wrote:
> I was just looking through files on my computer and stumbled over a README
> file from an old shareware DOS screen reader called TinyTalk. The part
> that I found interesting is that it listed several synthesizers that
> existed around 1994 and what chipset they used. It mentioned that the
> Braille 'N Speak line as well as the Accent line both use a chip called
> the SSI263. I found this interesting because the Braille 'N Speak sounds
> like crap, has terrible pronunciation, and practically no inflection.
> The Accent still sounds very mechanical, but has a lot more inflection,
> and its pronunciation is 10 times better than the Braille 'N Speak line.
> Apparently, this chipset wasn't the only piece required to produce speech.
> So, anybody know what makes such a radical difference? I know this isn't
> directly Linux related, but I figured a lot of the list members have been
> using computers for a long time and might know what makes the difference
> or where I may find such information.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` Gregory Nowak
` Adam Myrow
` Dave Hunt
` Glenn Ervin
` Dave Hunt
` shaun_oliver
` Janina Sajka
` shaun_oliver
` ccrawford
` Janina Sajka
` Gregory Nowak
` Dave Hunt
` Glenn Ervin
` Alex Snow
` a bit of trivia I found interesting and now Alex's situation Frank Carmickle
` Alex Snow
` Glenn Ervin [this message]
` a bit of trivia I found interesting Gregory Nowak
` Glenn Ervin
` Gregory Nowak
` Patrick Turnage
` Gregory Nowak
` Alex Snow
` Erik Heil
` Patrick Turnage
` Janina Sajka
` Gregory Nowak
` Alex Snow
` Gregory Nowak
` Janina Sajka
` Gregory Nowak
` Alex Snow
` Gregory Nowak
` kaare
` dashielljt
` Gregory Nowak
` Richard Villa
` Alex Snow
` Richard Villa
` dashielljt
` Chuck Hallenbeck
` Alex Snow
` Buddy Brannan
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='003401c2a7c5$521810e0$be00a8c0@default' \
--to=glennervin@cableone.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).