From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: properly switching synths in speakup
Date: Sun, 23 Apr 2006 19:04:58 -0700 [thread overview]
Message-ID: <20060424020458.GA14882@localhost.localdomain> (raw)
In-Reply-To: <20060423210003.GA12353@hhs48.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No need to apologize, we all make typos (smile).
I did some more testing on another system, where the bns is built-in,
and sftsyn is compiled as a module. It turns out that if I boot with
none, invoke sftsyn, then try to echo bns >/proc/speakup/synth_name,
things go bye-bye. If I first do echo none >/proc/speakup/synth_name,
before doing the echo bns command, things still go bye-bye.
However, if I boot with the bns connected, and it is detected, I can
switch between none, sftsyn, and bns as much as I want with no
problems.
Going back to the first system with the doubletalk, I then booted with
none as the synth. Once I did that, I was able to switch between bns,
dtlk, and none again as much as I wanted, both using speakwith and
manually BTW. I've also figured out why echo bns
>/proc/speakup/synth_name was simply giving back the shell prompt. It
was happening because the speakup_bns module wasn't loaded. With the
module loaded beforehand, the echo command works just fine, provided
that I didn't boot with dtlk as the initial synth of course.
Greg
On Sun, Apr 23, 2006 at 05:00:03PM -0400, Charles Hallenbeck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Thanks, Greg.
>
> I have here only the doubletalk external and speech-dispatcher to choose
> from, so switching between two hardware synths was not something I could
> test.
>
> Sorry about the typo. I will fix it pronto.
>
> - --
> The Moon is Waning Crescent (21% of Full)
> Get downloads from http://www.mhcable.com/~chuckh
> and remember, INFORMATION WANTS TO BE FREE!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQFES+rTXnuiIOyDVQURApNbAJ0azNP/IjAoov+fSRSEEBvaETcFWwCeLPbS
> JBvoZXLQdFhoLcw+MQuIUX4=
> =iSfa
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFETDJK7s9z/XlyUyARArJ3AKCTLU9HNkGjPGVpLyrWcbS/5VCZUgCfcGLK
HqjV9WRH2NBU7H6RyHRJkaQ=
=FKP0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Charles Hallenbeck
` Gregory Nowak
` Charles Hallenbeck
` Gregory Nowak [this message]
` Charles Hallenbeck
` Kirk Reiser
` Gregory Nowak
` Gregory Nowak
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=20060424020458.GA14882@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).