public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: Sean McMahon <smcmahon@usgs.gov>,
	"Speakup is a screen review system for Linux."
	<speakup@braille.uwo.ca>
Subject: Re: Testing my software synthasezer and switching to it.
Date: Thu, 10 Mar 2005 11:11:21 -0600	[thread overview]
Message-ID: <20050310171121.GA12473@blackbox> (raw)
In-Reply-To: <000801c524ee$126c48f0$77ac7682@azwaterDOM.wr.usgs.gov>

Hi.
You can build your synth modules into the kernel and change to a specific synth by echoing it's name to /proc/speakup/synth_name.  For example:

echo sftsyn >/proc/speakup/synth_name

would tell speakup to use the softsynth a2 default.

Hope this helps.
          Kenny
	  On Wed, Mar 09, 2005 at 02:22:05PM -0700, Sean McMahon wrote:
> One question,  If you have your modules for synths builtin and you try to load
> the softsynth module, can you make speakup work?  Can I have a special boot
> option to load nothing for my synth and then try to load speakup_sftsyn?
> Sean
> ----- Original Message ----- 
> From: "David Bruzos" <david@bruzos.org>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Wednesday, March 09, 2005 11:21 AM
> Subject: Re: Testing my software synthasezer and switching to it.
> 
> 
> > Hi there:
> > I think you should use "flite", because it is written in C and it is faster
> and more responsive than "festival".  However,
> > if you like "festival" better, there is nothing wrong with that...
> >
> > To test the synths do:
> >
> > 1. $ flite -f /path/to/file
> > 2. $ festival --tts /path/to/file
> >
> > Where /path/to/file is the path to some text file that you want flite/festival
> to speek.
> >
> > To get speakup working with software speech you will need some other
> applications.  They are:
> > 1. speech-dispatcher
> > 2. speechd_up
> >
> > I think you can get speech-dispatcher from your apt-get repos.  Speechd_up you
> will have to download from its website.  I
> > don't remember what that is.  Someone else can tell you that or google it...
> > Remember to look at the speech-dispatcher configuration if things are not
> working...
> >
> > To test speech-dispatcher do:
> > $ speech-dispatcher
> > $ spd-say "some text"
> >
> > Where "some text" is just some text you want it to speek.
> >
> > Now, you have to create the device /dev/softsynth with numbers 10/26.  Use the
> command:
> > $ mknod /dev/softsynth c 10 26
> >
> > After you have done all of this, run speech-dispatcher:
> > $ speech-dispatcher
> > Load the "sftsyn" speakup module into memory:
> > $ modprobe speakup_sftsyn
> > and run speechd_up:
> > $ speechd_up
> >
> > Note: you must remove the current speakup_xxxx module from the kernel before
> loading the speakup_sftsyn module.  Do
> > something like:
> > $ rmmod speakup_xxxx
> > Trying to load both modules at the same time, could crash your box.
> >
> > You should have a software speech enabled system at this point.  I am writing
> a howto on how to do this, but it has taken
> > me rediculously long to finish it!  I guess life/baby/school/etc has gotten in
> the way.
> >
> > David B.
> > On Wed, Mar 09, 2005 at 08:44:39AM -0800, jim grimsby wrote:
> > > Hi, well the time has come yep the moment I have been waiting for.  I have
> > > flite and festable installed on my system.  The sound card works I tested it
> > > out by doing this
> > > Apt-get install saytime saydate aumix
> > > After setting the volume with aumix by the way is this the best tool to use
> > > for this function?
> > > I ran saytime and saydate sound came out of the sound card with no problem.
> > >
> > > Then I did a search for the speech synthesizer by doing this
> > > Apt-cache search speech
> > > I found the packages I wanted by using speakups review commands and the mark
> > > and cut and paste command like this
> > > Apt-get install then the paste command.
> > > It installed vestable
> > > Then I issued the command
> > > Apt-get install flite
> > > Flite was installed.  Now I need to test these software synthesizers out and
> > > then switch speakup to one of them.  First question how should I go about
> > > testing them to make sure they work.  Second how do I switch speakup to one
> > > of them and witch one to choose.  Thanks
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  parent reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Suggestion: Speakup settings with sysctl Trevor Astrope
 ` Kirk Reiser
   ` Testing my software synthasezer and switching to it jim grimsby
     ` David Bruzos
       ` jim grimsby
         ` Farhan
         ` David Bruzos
           ` Hart Larry
       ` Sean McMahon
         ` David Bruzos
           ` mikster4
         ` Kenny Hitt [this message]
           ` jim grimsby
             ` Kenny Hitt

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=20050310171121.GA12473@blackbox \
    --to=kenny@hittsjunk.net \
    --cc=smcmahon@usgs.gov \
    --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).