In article <50975cb1$0$291$
1472...@news.sunsite.dk>, DenverD <
Den...@invalid.dk> wrote:
> On 11/05/2012 06:20 AM,
Avoi...@gmail.com wrote:
> > Because by comparing the file sizes I could get info as to
> > why your old version works and my new version does NOT.
> > Eg. perhaps some files have not changed: are the same size.
>
> little has changed in years and years...as you can see from the tiny (if
> any) file size differences...
No I can't see, because you refused to show the sizes of the old files.
>
> so, why does yours not work?
>
Correct
> since i see you wrote earlier:
>
> [QUOTE]
> `which festival` (nill)
> [/QUOTE]
>
`which` only looks in $PATH AFAIK
I deliberately tried to install to a separate partition.
> i'd have to guess that either you used incorrect directions to install
> festival, or maybe none at all..
>
> if you answer these maybe i can help you get going:
>
Thanks, if I can have reference a working version, it helps.
> 1. which distro are you using, and what version?
>
Currently: slakware 13.
> 2. if using a desktop environment, mention that also
>
kde4 has got the <festival handbook> and IIRC it's on the <menu>,
but shows some error; besides kde4 is crap. xfce doesn't <see> it;
and basically I use blackbox for X.
> 3. in what form did you download the program (.rpm, .deb, source, what?)?
>
-rw-r--r-- 1 root root 787313 2012-08-24 15:10 festival-2.1-release.tar.gz
-rw-r--r-- 1 root root 1925748 2012-08-24 11:53 festlex_CMU.tar.gz
-rw-r--r-- 1 root root 1073401 2012-08-25 07:24 festvox_cmu_us_slt_arctic_hts.tar.gz
-rw-r--r-- 1 root root 1681999 2012-08-25 00:48 speech_tools-2.1-release.tar.gz
Initial <intro/doco> ==
-rw-r--r-- 1 root root 6453 2012-08-24 11:48 FestivalDownload.html
> 4. how did you install the program?
>
See extract of log below. "->" means <typeIn>; "=>" means <I thought/read>
> 5. show here the output of ls -hal /usr/bin/festival
> mine is:
>
> -rwxr-xr-x 1 root root 3.3M Feb 18 2011 /usr/bin/festival*
>
OK so yours is a big binary.
Perhaps you don't know, but this project is very modular, and
developed over years, and for many platforms; which explains why
my dir-tree is big and confusing. It's got lots of scripts.
The correct way to debug a problematic 'hardware related'
project is from the back/goal.
-> <aplay> *.wav == confirms speech via earphones.
The next stage would be: what format/S does festival make?
Perhaps it doesn't save the sound-files, but probably it CAN.
I'll re-read my log and paste relevant stuff here:----
-> tar zxvf festlex_CMU.tar.gz == creates dir-leaf: -/festival/lib/dicts/cmu/*
-> d/l speech_tools-2.1-release.tar.gz
=> Unpack all the source files in a new directory. The directory will
then contain two subdirectories
speech_tools/
festival/
===> ie. expand ALL*.tar.gz FROM the same dir
-> tar zxvf speech_tools-2.1-release.tar.gz == creates dir-leaf: -/speech_tools/main
-> d/l festvox_cmu_us_slt_arctic_hts.tar.gz == ok
-> tar zxvf festvox_cmu_us_slt_arctic_hts.tar.gz == creates dir-leaf: -/us/cmu_us_slt_arctic_hts
=> delay: d/l festdoc*.tar.gz == not listed in dir:"Index of /downloads/festival/2.1"
=> Configuration => See `speech_tools/INSTALL' for instructions.
-> ./configure == checking build system type... i686-pc-linux-gnu
=> "This creates the file config/config"
== see: -/speech_tools/config/config
=> Compilation
=> still from dir: -/speech_tools
-> gmake == .... <long trace>... wfst_train ols ols_test xml_parser
=> To test the system after compilation -> gmake test
== .... <long trace>...lpc script status: CORRECT...Test OK
=> Installing the system
==>All executables are linked to from speech_tools/bin and you should add
that to your PATH in order to use them.
-> PATH=$PATH:/home/Hardware/Audio/Festival/speech_tools
-> export PATH
=> Checking an installation
==> Start the system => $ bin/festival
-> which festival == na
==> ?! where IS the binary: festival ?!
--> mc: seek in:/home/Hardware/Audio for:"For details ty"
== find/S but not-applicable
=================================================
If pre-compiled binaries were found, I would have used them.
Later I 're-compiled' into another partition, and got similar
error messages in the <configLog> file. The *.h cited re. the error
wasn't in my dir-tree.
Your idea that it just works, and didn't need any further attention,
is simplistic. This is an on going research project. And the fact that
the mail-list is dead indicates some BIGGER cause, like the global
economic crisis.
> --
> DenverD
== TIA.
Here's some more doco extracts to give a flavour.
I guess yours is different because you don't need to compile.
That's why I wanted you to give the sizes of your doco-files:---
=> -/Audio/Festival/festival/INSTALL ==
This section describes how to install Festival from source in a new
location and customize that installation.
In order to compile Festival you first need the following source
packages
`festival-2.0-release.tar.gz'
`speech_tools-1.2.4-release.tar.gz'
`festlex_NAME.tar.gz'
`festvox_NAME.tar.gz'
`festdoc_2.0.tar.gz'
Currently we have compiled and tested the system under ...
(Redhat 4.1, 5.0, 5.1, 5.2, 6.[012], 7.[01], 8.0, 9, FC1 and other Linux
_GNU make_
Due to there being too many different `make' programs out there we
have tested the system using GNU make on all systems we use.
Others may work but we know GNU make does.
_Audio hardware_
You can use Festival without audio output hardware but it doesn't
sound very good (though admittedly you can hear less problems with
it). A number of audio systems are supported (directly inherited
from the audio support in the Edinburgh Speech Tools Library):
NCD's NAS (formerly called netaudio) a network transparent audio
system (which can be found at
`
ftp://ftp.x.org/contrib/audio/nas/'); `/dev/audio' (at 8k ulaw
and 8/16bit linear), found on Suns, Linux machines and FreeBSD;
and a method allowing arbitrary UNIX commands. *Note Audio
output::.
=> Unpack all the source files in a new directory. The directory will
then contain two subdirectories
speech_tools/ == na
festival/ == na
Configuration
=============
First ensure you have a compiled version of the Edinburgh Speech
Tools Library. See `speech_tools/INSTALL' for instructions.
The system now supports the standard GNU `configure' method for set
up. In most cases this will automatically configure festival for your
particular system. In most cases you need only type
gmake
and the system will configure itself and conpile, (note you need to
have compiled the Edinburgh Speech Tools `speech_tools-1.2.4' first.
==> speech_tools-2.1-rel..> 08-Nov-2010 15:11 1.6M
..[ If these are installed you can test the installation with
gmake test]
To simply make it run with a male US English voiuce it is sufficient
to install just
festlex_CMU.tar.gz
festlex_POSLEX.tar.gz
festvox_kallpc16k.tar.gz
==> If for example in
your environment you may wish the default audio output method to be 8k
mulaw through `/dev/audio' you should add the following line to your
`siteinit.scm' file
(Parameter.set 'Audio_Method 'sunaudio)
==>Once compiled and site initialization is set up you should test to
see if Festival can speak or not.
Start the system
$ bin/festival