>gordon@spot.Colorado.EDU (GORDON ALLEN R) writes:
>According to my interpretation, "klatt" will produce files with the
>following extensions: .xgr, .dat and .au. Only files of extension
>.au are playable on sparc stations. And the .xgr and .dat files
>are binary files which contain the entire waveform produced by the
>synthesizer. If you found that the .xgr's and .dat's non-readable,
>you can try to extract the waveform by yourself by looking into
>the content of the short integer array "iwave" in the source file
>"klatt.c". In "klatt.c", the content of "iwave" are compressed
>(using mu-law) and the results will be placed in a character array
>called "plabuf".
>Cheers!
>Yu Wai-Leung
>Dept of Computer Science,
>Chinese University of Hong Kong
>e-mail: yu030@cs.cuhk.hk
Thanks,
The .au file was not written. Examination of the code in klatt.c revealed that
the code segment that created the header and wrote the data to the .au file
was in a #if FALSE .... #endif conditional. Removal of this conditional,
then allowed for the creation of the file, which is an audio data file
(according to file). However, playing the test file hello.par produces sound
which is unintelligble. It is identical to playing back the audio file
hello.au. Furthermore, something that wasn't clear in my original note was thatwhile hello.xgr file could be displayed with xplot, the plot really didn't
look like speech. Similarly for hello.dat.
What am I missing here? I'll check the short array iwave to see if I can find
anything else. However, as I read klatt.c, iwave is filtered through
audio_s2u to produce plabuf. The ascii files hello.xgr and hello.dat are
produced from audio_u2s(plabuf). Shouldn't this be the same as iwave, then?
The file hello.au is essentially plabuf with an audio header.
--
Allen Gordon *If the folly of but one of us was changed to*
Research Associate *intelligence, and divided amongst a thousand*
gordon@tramp.colorado.edu *toads, each would be more intelligent than *