public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mikster4@msn.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: festival and speech dispatcher FC6
Date: Thu, 12 Oct 2006 10:00:27 +0100	[thread overview]
Message-ID: <cone.1160643627.166912.4776.0@layla> (raw)
In-Reply-To: <200610112007.00633.garycramblitt@comcast.net>

Don't forget to start festival as a server (the --server option, or have 
festival start as a server on startup, if using a rpm package it probably 
comes with the start script). 

Any way I would suggest espeak rather than festival.

From
Michael Whapples

Gary Cramblitt writes:

> On Wednesday 11 October 2006 18:20, Guy Schlosser wrote:
>> 	Hey all, the sound problem is fixed.  I have a question though, and
>> it has to do with Festival and Speech-dispatcher.  I installed S-D
>> 0.61 from yum, using the method Hynek outlined in a previous message,
>> and when I do spd-say "hello", I get an error message that says
>> "connection refused."  Do I have to put festival in some kind of
>> daemon mode or something?  If anyone has had this issue and can give
>> me some pointers for solving it, that would be awesome.  I think I'm
>> gonna install Espeak, and see if I can't get it working with
>> that.  Thanks in advance for the help.
> 
> From the Speech Dispatcher INSTALL file:
> 
> ----
> Installing Festival Speech Dispatcher interface:
> ================================================
> 
> You need to install the new version of festival-freebsoft-utils (0.3
> or higher).
> 
> Please make sure that Festival server_access_list configuration
> variable and your /etc/hosts.conf are set properly. server_access_list
> must contain the symbolic name of your machine and this name must be
> defined in /etc/hosts.conf and point to your IP address. You can test
> if this is set correctly by trying to connect to the port Festival
> server is running on via an ordinary telnet. If you are not rejected,
> it probably works.
> ----
> 
> On my system (Debian), file /etc/festival.scm contains the following:
> 
> ----
> ;; Any site-wide Festival initialization can be added to this file.
> ;; It is marked as a configuration file, so your changes will be saved
> ;; across upgrades of the Festival package.
> 
> (set! server_access_list '("localhost"))
> ----
> 
> and my /etc/hosts file contains:
> 
> 127.0.0.1       localhost       newton
> 
> "newton" being my machine's host name.
> 
> -- 
> Gary Cramblitt (aka PhantomsDad)
> 
> 
> 


  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Guy Schlosser
 ` Gary Cramblitt
   ` Michael Whapples [this message]
   ` guy schlosser
 ` 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=cone.1160643627.166912.4776.0@layla \
    --to=mikster4@msn.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).