VoxForge
This is my first time running through this example on Step5.
I may have saved the wav files with 32 bits instead of 16 bits. Would this have done something?
$ /usr/local/bin/HCopy -A -D -T 1 -C wav_config -S codetrain.scp
/usr/local/bin/HCopy -A -D -T 1 -C wav_config -S codetrain.scp
HTK Configuration Parameters[11]
Module/Tool Parameter Value
# NUMCEPS 12
# CEPLIFTER 22
# NUMCHANS 26
# PREEMCOEF 0.970000
# USEHAMMING TRUE
# WINDOWSIZE 250000.000000
# SAVEWITHCRC TRUE
# SAVECOMPRESSED TRUE
# TARGETRATE 100000.000000
# TARGETKIND MFCC_0_D
# SOURCEFORMAT WAV
ERROR [+6251] Only standard PCM, mu-law & a-law supported
ERROR [+6213] OpenWaveInput: Get[format]HeaderInfo failed
ERROR [+6313] OpenAsChannel: OpenWaveInput failed
ERROR [+6316] OpenBuffer: OpenAsChannel failed
ERROR [+1050] OpenParmFile: Config parameters invalid
FATAL ERROR - Terminating program /usr/local/bin/HCopy
I have made the .wav file over again. It is 16 Bit and 48KHz.
I have the same error messages. I'm using Audacity to record the WF. I'm going to try to find the error codes in the documentation. Hopefully that will lead somewhere.
>I have made the .wav file over again. It is 16 Bit and 48KHz.
>I have the same error messages.
Did you follow the Configuring Audacity Preferences section in Step 3 ( i.e. 'Channels' to 1 (Mono). and 'Uncompressed Export Format' to WAV (Microsoft 16 bit PCM))?
Thanks kmaclean. Yes I deviated from the step because it mentioned at the end saving it to a higher quality file format.
I didn't change all the settings back the way they should have been.
I have a tendancy to push the system without knowing it's limits, but that is how I learn too.
Thanks I'm sure you'll be hearing from me again. I'm trying to build a product that might be of some interest to VoxForge. Is there another e-mail that I should use to contact a representative of VoxForge or should I just use, [email protected].
Regards,
Michael V. Liguori
> Is there another e-mail that I should use to contact a representative of
>VoxForge or should I just use, [email protected].
Forum posts are preferred, but for private messages, [email protected] is fine.
Ken