From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Using sftsyn
Date: Thu, 31 Mar 2005 00:56:44 -0600 [thread overview]
Message-ID: <20050331065643.GB29827@blackbox> (raw)
In-Reply-To: <000c01c535bd$189f6ec0$220110ac@jim>
Hi.
What kernel are you using? Do you know that the softsynth module was
included in your kernel?
Do you know how to find out?
When you can answer these questions, I bet you will know your problem.
Hope this helps.
Kenny
On Wed, Mar 30, 2005 at 10:44:26PM -0800, jim grimsby wrote:
> To answer a prevuis message I am aware that using the decpc would not
> provide me with speech using software it was a test to see if the device
> it self would change it did.
> How ever when I change it to sftsyn the device does not change.
> So like I said this should mean that I do not have the driver installed
> as a module or in the kernel. Is this corect. Also what is the easyist
> way to remady this sitchuation before going on. Speech dispatcher is
> working fine with all synthasizers installed flite at the moment is the
> default I thought I would get it working with it before moving on to the
> dectalk the dectalk is working using dtk-generic as a output module.
> The devices have been maid as described in the speakup how to and the
> users guide. Both very nice documents. I think I will update the
> install file here for speechd-up to include the other packages I had to
> install to get it working.
> Thanks for all the help so far!
>
>
>
> _______________________________________________
> 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: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
jim grimsby
` Kenny Hitt [this message]
` jim grimsby
` Kenny Hitt
` jim grimsby
` Kenny Hitt
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=20050331065643.GB29827@blackbox \
--to=kenny@hittsjunk.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).