From: Hynek Hanke <hanke@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speech-dispatcher beta 1, no speech
Date: Mon, 16 Jul 2007 11:21:31 -0700 [thread overview]
Message-ID: <1184610092.5275.11.camel@chopin> (raw)
In-Reply-To: <20070716061244.C1E4E6BE@pop15.mta.everyone.net>
On Mon, 2007-16-07 at 09:12 -0400, Guy Schlosser wrote:
> Hi all, I installed the speech-dispatcher 0.6.4 beta 1 today, and
> have a few problems. Not sure if they are a problem with the beta or
> something on my system, but if someone could help me sort it out, it
> would be greatly appreciated. When I rebooted my computer after
> install, and recompiling the python bindings, I get no speech. I
> then got orca back to a speakable state, and found the following
> problems when I examined /var/log/speechd.log, I see the message "bad
> syntax from module Espeak.
Anyway, I believe that why you get no speech is because your version
is not build with ALSA support and Speech Dispatcher has now switched
its default settings to ALSA. You can either switch the settings for the
modules that interest you in each of their settings file to OSS or NAS
or you need to install ALSA including its developement packages.
Further, look at speechd.conf (option DefaultModule) and set it to your
prefered synthesizer.
In case your problems persist, could you please send me the full log
(since start of speech-dispatcher) with priority 5
(see /usr/local/etc/speech-dispatcher/speechd.conf, option LogLevel).
Have a nice day,
Hynek
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Guy Schlosser
` Hynek Hanke [this message]
Fwd: " Guy Schlosser
` Michael Whapples
` Guy Schlosser
` Jonathan Duddington
Michael Whapples
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=1184610092.5275.11.camel@chopin \
--to=hanke@brailcom.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).