public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Willem van der Walt <wvdwalt@csir.co.za>
To: Jonathan Duddington <jsd@clara.co.uk>
Cc: speakup@braille.uwo.ca
Subject: Re: eSpeak - Introduction
Date: Thu, 13 Apr 2006 09:03:15 +0200 (SAST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0604130852320.28756@localhost.localdomain> (raw)
In-Reply-To: <4e16ac76cdjsd@clara.co.uk>

Hi Jonathan
Thanks for a much needed useful free software synthesizer.
The clarity and accuracy of the speech is quite good.  I am interested in 
the process of creating a new language using espeak.
Where can I get more detail on that?
I think there is a bug in the espeak program when reading long text files. 
To me it is no problem as I am using speech-dispatcher which sends smaller 
chunks of text at a time, but others might be using the file feature.
The program segfaults after a time.
Thanks again for a great program.
Regards, Willem


On Thu, 13 Apr 2006, Jonathan Duddington wrote:

> I've just found this mailing list from a comment on the
> espeak.sourceforge.net forum.  It's good to see people using (or trying
> to use) eSpeak.
>
> eSpeak is not new, I originally wrote it about 10 years ago for the
> Acorn/RISC OS platform.  The Linux version is a re-write of the code
> which I've been doing over the past few months.  I'm definitely not an
> expert on Linux system programming or system administration, so I'll
> probably need to ask for help in those areas if the need arises.
>
> eSpeak uses the "sinusoidal" technique of synthesis.  Basically it
> makes vowels and sonorant consonants, eg. [r,l,m,n,w] by adding
> together the sine waves of harmonics in varying proportions.
>
> Unvoiced consonants such as [h,t,s,f,k] are simply recorded sound
> samples, while voiced consonants eg [v,z,d,g] are a mixture of these
> two methods.
>
> It should be interesting to see what are the specific needs of a TTS
> engine for use with speakup, and how eSpeak can be improved to give a
> better match to them.
>
> I've been using eSpeak on Linux mostly with the KDE TTS system (KTTS).
> I don't know anything about speakup or speech-despatcher yet, other
> than a quick look at the speakup user guide.
>
> A problem has been reported with eSpeak, where it locks up when it
> finds the sound device is already in use.  I've made a fix for this for
> the next release, which I'll probably make in a few days.  Perhaps
> there are some other changes that will be useful too.  Let me know :-)
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.
 
CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html 
 
CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html 
 
For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
HelpDesk@csir.co.za.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.



  parent reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jonathan Duddington
 ` Lorenzo Taylor
 ` Willem van der Walt [this message]
   ` Jonathan Duddington
     ` ace
       ` Jonathan Duddington
 ` Kirk Reiser
   ` Jonathan Duddington
     ` Lorenzo Taylor
     ` Kirk Reiser
       ` eSpeak - embedded commands Jonathan Duddington
 ` eSpeak -- features wish list Hynek Hanke
     [not found] <mailman.967.1144930700.625.speakup@braille.uwo.ca>
 ` eSpeak - Introduction 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=Pine.LNX.4.62.0604130852320.28756@localhost.localdomain \
    --to=wvdwalt@csir.co.za \
    --cc=jsd@clara.co.uk \
    --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).