From: Jacob Schmude <jschmude@adelphia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Flite and different voices
Date: Fri, 7 May 2004 12:41:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0405071237110.10807@beavis.screwball> (raw)
In-Reply-To: <20040507154643.GE422@lnx3.holmesgrown.com>
Hi
Well, actually... there is a very ugly way to get speech
dispatcher to use the kal16 voice. It works, but is by no means anywhere
near the best way to accomplish it. What you have to do is move the 8K
voices out of the way, to somewhere that isn't in your linker path. Then,
symlink all the 8K filenames to their 16K equivalents. Since they use the
exact same functions and symbols, speech dispatcher doesn't know the
difference, and you get the 16K voices. Again, this is a very ugly
and ineligant way to do this, but if you're desperate for flite's 16K
voices, it does work.
HTH
On Fri, 7 May 2004, Steve Holmes wrote:
> Alas, after doing all that, I still get the shitty 8-bit voice! I've
> run out of ideas at the moment.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
speakup and cepstral? (fwd) Cheryl Homiak
` Cheryl Homiak
` Hynek Hanke
` speakup and cepstral? Steve Holmes
` Cheryl Homiak
` Cheryl Homiak
` Cheryl Homiak
` Steve Holmes
` Cheryl Homiak
` speakup and Flite 16 Bit Voices Richard Wells
` Steve Holmes
` Richard Wells
` speakup and cepstral? Steve Holmes
` nick G
` Steve Holmes
` Flite and different voices (was: Re: speakup and cepstral?) Hynek Hanke
` Flite and different voices Steve Holmes
` Cheryl Homiak
` Steve Holmes
` Jacob Schmude [this message]
` Hynek Hanke
` Steve Holmes
` Hynek Hanke
` Steve Holmes
` nick G
` speakup and cepstral? Garrett Klein
` Chuck Hallenbeck
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=Pine.LNX.4.58.0405071237110.10807@beavis.screwball \
--to=jschmude@adelphia.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).