Flite and different voices

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes! That should do it.  In the flite sources, there is as a default
two voices: the cmu_us_kal that you are using and cmu_us_kal16 for the
16-bit voice.  I will try changing this and see what the dispatcher
will sound like.  The next easiest thing might perhaps be to add a
configure option that one could use to select flite voice but that
would still be a compile time option.

My version of flite is 1.2-release from the usual site at CMU and that
includes the kal16 voice.  I'm under the impression one could hook in
the new Cepstral voices into flite as well; not sure though.

On Fri, May 07, 2004 at 12:44:33AM +0200, Hynek Hanke wrote:
> This is a bit of problem with Flite, because in the module I have to call
> different C functions for different voices. As I wasn't aware there are more
> than one voice and it seemed there won't be any in near future, I hardcoded
> here only the one that came with my distribution of Flite.
> 
> I'm interested in where can I get kal16 for Flite?
> 
> It seems I'll have to somehow make this configurable if there are more voices
> for Flite now. As it is now, you have to edit the source code. If you want
> to play around with it a little bit, it's src/modules/flite.c in you Speech
> Dispatcher source directory, some line around l.95. Now it reads:
> 	flite_voice = register_cmu_us_kal();
> and you would probably want to change it to
> 	flite_voice = register_cmu_us_kal_16();
> or something like that. Then recompile and make install. I don't know
> the exact function name, maybe you could ask the Festival guys about
> it and write us back. This kind of help is always appreciated.
> 
> Best Regards,
> Hynek Hanke

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAmyVVWSjv55S0LfERAtgeAKC+RLdZp+VXFT0Zq+DX955mfvXDzwCfTDzH
KHAQdUXZ6QBLWKsliXRFfKM=
=kquT
-----END PGP SIGNATURE-----