From: Mark Peveto <southernprince73@gmail.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: problem with speechd-up and Pico
Date: Mon, 23 Jan 2017 14:32:14 -0600 (CST) [thread overview]
Message-ID: <alpine.LNX.2.20.999.1701231431370.1393@purrwurr> (raw)
In-Reply-To: <daa49384-196c-687a-7b55-56acce618dca@manuelcortez.net>
Hmm, I'm gonna have to find my vinux flash drive and try it. I got it working for a while, but I don't remember how. I'll try it otmorrow. I just
came off chemo today.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Mon, 23 Jan 2017, Manuel Cortéz wrote:
> Hello all,
>
> I'm running speakup with speechd-up in Debian Stable. Speech Dispatcher
> is configured to use pulseaudio, pulse starts in system mode and
> everything seems to be OK if you're going to use espeak. However if I
> want to use another voice, for example Pico (pico-generic.conf in spd's
> modules), it doesn't work. I have mate installed and if I use spd-say
> from the normal user it works and I can see pico in the output modules,
> but I can't get it to work in speechd-up. I have changed everything as
> needed in the root directory (I had to configure spd for root and allow
> pulse to give access to this user in order to get speechd-up to work,
> maybe I did something wrong here?), but it seems it doesn't matter what
> I change, it just doesn't work.
>
> If I change the default-language in spd (in the root user's settings) it
> works, but nothing about modules.
>
> Does someone know how to make speechd-up to work with other synths?
>
> Thanks in advance.
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Manuel Cortéz
` Mark Peveto [this message]
` Manuel Cortéz
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.LNX.2.20.999.1701231431370.1393@purrwurr \
--to=southernprince73@gmail.com \
--cc=speakup@linux-speakup.org \
/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).