public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: festival unknown voices
Date: Thu, 2 Jan 2020 11:55:47 -0500	[thread overview]
Message-ID: <alpine.NEB.2.21.2001021152460.7636@panix1.panix.com> (raw)
In-Reply-To: <alpine.NEB.2.21.2001021148060.19526@panix1.panix.com>

I would have used espeak-ng on archlinux but can't find documentation on
how to have that package start at boot.  The speech-dispatcher system
works with espeak-ng in that spd-say will speak but if I can't have
espeak-ng replace espeak and espeakup this won't help since I mostly run
in command line and rarely run in graphical so I use startx to start up
graphical when needed.

On Thu, 2 Jan 2020, Linux for blind general discussion wrote:

> Date: Thu, 2 Jan 2020 11:50:56
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: festival unknown voices
>
> When trying to run speech-dispatcher against festival with pulse or alsa
> in test mode using spd-conf I'm getting no speech from spd-say and these
> errors.   I've installed festival-us package on the system which has
> voices in it and it's these festival is claiming are unknown.
> SIOD: unknown voice cmu_us_slt_cg
> SIOD: unknown voice cmu_us_slt_cg
> SIOD: unknown voice cmu_us_awb_cg
> SIOD: unknown voice cmu_us_awb_cg
> SIOD: unknown voice cmu_us_rms_cg
> SIOD: unknown voice cmu_us_rms_cg
>
>
> How do I clear these festival errors?
>
>
>

-- 


      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion [this message]

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=alpine.NEB.2.21.2001021152460.7636@panix1.panix.com \
    --to=blinux-list@redhat.com \
    /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).