From: "Rob Hudson" <captinlogic@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speech-dispatcher problem
Date: Mon, 17 Sep 2012 18:16:39 -0500 [thread overview]
Message-ID: <73BFE0C6C5804F5BB5D5722C2F4A1FEC@fred> (raw)
In-Reply-To: <5057A75F.2030802@yahoo.com.br>
I did manage to fix it. It appears the debian package was broken, because
once I installed from tarball and ran the spd-conf command, and then:
speech-dispatcher -C /usr/local/etc/speech-dispatcher
it worked fine. I now have it running with speechd-up and I am fixing to
make an initScript.
With the debian package, it couldn't find my audio device and failed to
initialize for some reason. i have no idea how to fix it, so I did
apt-get purge speech-dispatcher
and then started all over again from source.
----- Original Message -----
From: "Cleverson Casarin Uliana" <clever92000@yahoo.com.br>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, September 17, 2012 5:42 PM
Subject: Re: speech-dispatcher problem
> Hi, I'm also interested in this question. AFAIC, to be able to use other
> voices than ESpeak, you need a piece of software called Speechd-up.
> However, last year (2011) when I asked whether it was available for Gentoo
> users, it got an answer that it was broken. I asked recently whether it's
> still broken, with no answer til now. I'd also like to use it, in case
> it's functional.
>
> Cheers
> Cleverson
>
> Em 16/09/2012 16:34, Rob Hudson escreveu:
>> I'm trying to get speakup working with speech-dispatcehr and voxin.
>> However it won't connect and, in speechd.log, I see this:
>> I am running speech-dispatcher 0.7.1 and Debian Squeeze, with Voxin-0.42.
>>
>>> From /var/log/speech-dispatcher/speech-dispatcehr.log
>> [Sat Sep 15 04:14:50 2012 : 525783] speechd: Speech Dispatcher Logging to
>> file /var/log/speech-dispatcher//speech-dispatcher.log
>> [Sat Sep 15 04:14:50 2012 : 525903] speechd: Initializing output module
>> ibmtts with binary /usr/lib/speech-dispatcher-modules/sd_ibmtts and
>> configuration /etc/speech-dispatcher/modules//ibmtts.conf
>> [Sat Sep 15 04:14:50 2012 : 525916] speechd: Output module is logging to
>> file /var/log/speech-dispatcher//ibmtts.log
>> [Sat Sep 15 04:14:50 2012 : 526228] speechd: Module ibmtts loaded.
>> [Sat Sep 15 04:14:50 2012 : 526393] speechd: ERROR: Bad syntax from
>> output
>> module ibmtts 1
>> [Sat Sep 15 04:14:50 2012 : 526466] speechd: Initializing output module
>> dummy with binary /usr/lib/speech-dispatcher-modules/sd_dummy and
>> configuration (null)
>> [Sat Sep 15 04:14:50 2012 : 526480] speechd: Output module is logging to
>> file /var/log/speech-dispatcher//dummy.log
>> [Sat Sep 15 04:14:50 2012 : 526744] speechd: Module dummy loaded.
>> [Sat Sep 15 04:14:50 2012 : 531115] speechd: LINE here:|304 CANT LIST
>> VOICES|
>> [Sat Sep 15 04:14:50 2012 : 531140] speechd: Module dummy started
>> sucessfully with message:
>> ---------------
>> Everything ok so far.
>> ---------------
>> [Sat Sep 15 04:14:50 2012 : 531408] speechd: Configuration has been read
>> from "/etc/speech-dispatcher/speechd.conf"
>> [Sat Sep 15 04:14:50 2012 : 531436] speechd: Speech Dispatcher Logging to
>> file /var/log/speech-dispatcher//speech-dispatcher.log
>> [Sat Sep 15 04:14:50 2012 : 531458] speechd: Speech Dispatcher will use
>> local unix socket:
>> /var/run/speech-dispatcher/.speech-dispatcher/speechd.sock
>> [Sat Sep 15 04:14:50 2012 : 533528] speechd: Speech Dispatcher started
>> and
>> waiting for clients ...
>> Any idea what's happening here? I also noticed that, using the say tool
>> in voxin's source tree, I have to do aoss ./say in order for the "hello
>> world" message to be spoken. Could this be the problem?
>> _______________________________________________
>> 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: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Rob Hudson
` Cleverson Casarin Uliana
` Rob Hudson [this message]
` covici
` Bohdan R. Rau
` Bohdan R. Rau
` Bohdan R. Rau
` Cleverson Casarin Uliana
` covici
-- strict thread matches above, loose matches on Subject: below --
Hoa Nguyen Dang
` Tyler Spivey
` Kirk Reiser
` Kirk Reiser
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=73BFE0C6C5804F5BB5D5722C2F4A1FEC@fred \
--to=captinlogic@gmail.com \
--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).