From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: festival
Date: Sun, 13 Mar 2005 12:12:10 -0600 [thread overview]
Message-ID: <20050313181210.GB20633@blackbox> (raw)
In-Reply-To: <001101c525dd$a8d5a120$220110ac@jim>
Hi.
There is a bug that can trash your hardware synth on com 1, but it should
only be a problem once. It only happens when you first set up
Gnopernicus for a new user.
Basically: when you select "enable screen reader" in the assistive
technology dialog in desktop preferences, the defaults for Gnopernicus
will be switched to ones that include a braille display connected to com
1. Just go into the startup preferences dialog of Gnopernicus and
disable braille support to get Gnopernicus to stop messing with the com
port. After you do this, you can switch to a text console and get the
synth back.
To get the synth back, just change the speakup default to none, power
cycle the synth, and then return the speakup default to the hardware
synth.
The bug has been reported, and it should be fixed "soon". Like I said,
it only happens when you first set up Gnopernicus, it won't happen again
and it won't happen on a system that just runs Gnome without
Gnopernicus.
Hope this helps.
Kenny
On Thu, Mar 10, 2005 at 05:57:12PM -0800, jim grimsby wrote:
> Hi, no
> The problem is when you run gnome whith the screen reader for gnome both of
> them as far as I know it kills your speech device because it only
> understands that a Braille display is on the serial port. Hth
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of Kyrath. (AKA Rob)
> Sent: Thursday, March 10, 2005 8:21 AM
> To: Speakup
> Subject: festival
>
>
> In the course of reading various documentation, I came across a warning that
> compiling festival, or perhaps some other program that requires festival,
> can potentially kill a hardware synth.
>
> Is this a true risk?
> I'm looking to compile festival on a slackware 10.1 system with a doubletalk
> synth.
>
> -- Rob
>
> _______________________________________________
> 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: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
festival Kyrath. (AKA Rob)
` festival mikster4
` festival jim grimsby
` Kenny Hitt [this message]
` festival Kyrath. (AKA Rob)
` festival jim grimsby
-- strict thread matches above, loose matches on Subject: below --
festival Joseph C. Lininger
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=20050313181210.GB20633@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).