Festival Speech Synthesis System: - Speech Resource Pages

Windows95 or if you don't ask for them to be set globally under NT you need to run
vcvars32.bat
See the VC++ documentation for more details.
Once you have the source trees with VCMakefiles somewhere visible from Windows, you need to copy
`peech_tools\config\vc_config-dist' to `speech_tools\config\vc_config' and edit it to
suit your local situation. Then do the same with `festival\config\vc_config-dist'.
The thing most likely to need changing is the definition of FESTIVAL_HOME in
`festival\config\vc_config_make_rules' which needs to point to where you have put festival.
Now you can compile. cd to the speech_tools directory and do
nmake /nologo /fVCMakefile
and the library, the programs in main and the test programs should be compiled.
The tests can't be run automatically under Windows. A simple test to check that things are probably OK is:
main\na_play testsuite\data\ch_wave.wav
which reads and plays a waveform.
Next go into the festival directory and do
nmake /nologo /fVCMakefile
to build festival. When it's finished, and assuming you have the voices and lexicons unpacked in the right place,
festival should run just as under unix.
We should remind you that the NT/95 ports are still young and there may yet be problems that we've not found yet.
We only recommend the use the speech tools and Festival under Windows if you have significant experience in C++
under those platforms.
Most of the modules `src/modules' are actually optional and the system could be compiled without them. The
basic set could be reduced further if certain facilities are not desired. Particularly: `donovan' which is only
required if the donovan voice is used; `rxp' if no XML parsing is required (e.g. Sable); and `parser' if no
stochastic paring is required (this parser isn't used for any of our currently released voices). Actually even
`UniSyn' and `UniSyn_diphone' could be removed if some external waveform synthesizer is being used (e.g.
MBROLA) or some alternative one like `OGIresLPC'. Removing unused modules will make the festival binary
smaller and (potentially) start up faster but don't expect too much. You can delete these by changing the
BASE_DIRS variable in `src/modules/Makefile'.
[ < ] [ > ] [ > ] [Top] [Contents] [Index] [ ? ]
6.3 Site initialization
Once compiled Festival may be further customized for particular sites. At start up time Festival loads the file
`init.scm' from its library directory. This file further loads other necessary files such as phoneset descriptions,
duration parameters, intonation parameters, definitions of voices etc. It will also load the files `sitevars.scm'
and `siteinit.scm' if they exist. `sitevars.scm' is loaded after the basic Scheme library functions are
loaded but before any of the festival related functions are loaded. This file is intended to set various path names
before various subsystems are loaded. Typically variables such as lexdir (the directory where the lexicons are