From: mikster4@msn.com
To: speakup@braille.uwo.ca
Subject: Re: festival
Date: Thu, 10 Mar 2005 17:18:35 +0000 [thread overview]
Message-ID: <cone.1110475115.578991.1730.0@slax> (raw)
In-Reply-To: <033201c5258d$26e58680$0601a8c0@kasil>
I don't see any reason festival would do this. I think in the past I
have compiled festival on slackware and not had any problem with
hardware synths. If you are unsure then you can use the RPM's with
the rpm2tgz tool, I know this works.
Mike
Kyrath. (AKA Rob) writes:
> In the course of reading various documentation, I came across a warning that compiling festival, or perhaps some other program that requires festival, can potentially kill a hardware synth.
>
> Is this a true risk?
> I'm looking to compile festival on a slackware 10.1 system with a doubletalk synth.
>
> -- Rob
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
festival Kyrath. (AKA Rob)
` mikster4 [this message]
` festival jim grimsby
` festival Kenny Hitt
` festival Kyrath. (AKA Rob)
` festival jim grimsby
-- strict thread matches above, loose matches on Subject: below --
festival Joseph C. Lininger
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.1110475115.578991.1730.0@slax \
--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).