public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Michael Whapples" <mwhapples@aim.com>
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 17:49:48 +0100	[thread overview]
Message-ID: <003b01c7c7c9$535f7ff0$706b030a@Mikelaptop> (raw)
In-Reply-To: <20070716073813.C1E4E2CE@pop15.mta.everyone.net>

If you want alsa support, you will need the dev alsa packages as well 
(probably something like libasound2-dev).

Also you may want to install the latest version of espeak if you are using 
the espeak specific module (the module called espeak, not espeak-generic) as 
earlier versions don't support changing the espeak voice through 
speech-dispatcher.

Also try disabling any modules you don't actually want, while it doesn't 
solve the problem being there in speech-dispatcher, it removes it for you.

So if you still get errors with modules you need, say which ones you are 
using (I suggest using the speech-dispatcher names as there the two espeak 
modules, espeak and espeak-generic, and things are different for these two 
modules).

From
Michael Whapples
----- Original Message ----- 
From: "Guy Schlosser" <guyster@buckeye-express.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, July 16, 2007 3:38 PM
Subject: Fwd: speech-dispatcher beta 1, no speech


>I forgot to mention in my previous post that I'm running Ubuntu 7.04 with 
>Espeak 1.25.  Again, thanks in advance for the help.
>
>
>
> Guy
>
>>Date: Mon, 16 Jul 2007 09:12:42 -0400
>>To: speakup@braille.uwo.ca
>>From: Guy Schlosser <guyster@buckeye-express.com>
>>Subject: speech-dispatcher beta 1, no speech
>>
>>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.  I 
>>also see some problems with module ibmtts.  The messages are: Broken pipe 
>>to module and library not compiled with alsa support.  Anyone have any 
>>suggestions?  As always, any help would be greatly appreciated.
>>
>>Thanks much in advance,
>>
>>
>>Guy
>
>
>
>
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Fwd: " Guy Schlosser
 ` Gregory Nowak
 ` Michael Whapples [this message]
   ` Guy Schlosser
     ` Jonathan Duddington
  -- strict thread matches above, loose matches on Subject: below --
 Michael Whapples
 Guy Schlosser
 ` Hynek Hanke

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='003b01c7c7c9$535f7ff0$706b030a@Mikelaptop' \
    --to=mwhapples@aim.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).