Comments

Flat
HLEd error for French data set
User: amza
Date: 7/18/2010 10:23 am
Views: 4379
Rating: 16

Hi,


I was running this command to get the phones0.mlf:

HLEd -A -D -T 1 -l '*' -d dict -i phones0.mlf mkphones0.led words.mlf

but I got the error like this:

No HTK Configuration Parameters Set

Editing file: words.mlf
  ERROR [+1232]  NumParts: Cannot find word n++#!MLF!# in dictionary
 FATAL ERROR - Terminating program d:\Toolkits\htk\bin.win32\HLEd.exe

I've checked the words.mlf, and it's fine. I have no idea why it gave error like that. Btw, on the terminal, it's not "n++" but some symbol that I don't know. Is that because there's some encoding issue I have to deal with in French or something else? I'm looking forward to hearing from you.

 

Many thanks,

AmZa

Re: HLEd error for French data set
User: kmaclean
Date: 7/18/2010 12:55 pm
Views: 197
Rating: 14

>Is that because there's some encoding issue I have to deal with in French

>or something else?

Yes.

See here: Windows/Linux/Mac text file line-ending issues

Re: HLEd error for French data set
User: amza
Date: 7/19/2010 6:25 am
Views: 138
Rating: 17

Hi there,


Thanks for your reply. I had already removed the ^M at the end of every line. However, I don't think the problem is at the end of the line, but at the beginning, don't you think? because the weird symbol appears at the beginning of the line. Moreover, this problem also happened when I ran the HCopy command:

HCopy -A -D -T 1 -C config -S codetrain.scp

It gave me the same error:

ERROR [+6210]  OpenWaveInput: Cannot open waveform file ´++wav/4h-20100505-vgm

Once again, I've checked the codetrain.scp and removed all ^M symbols at the end of every line, but I still got the same error. I'm looking forward to hearing from you.

 

Many thanks,

AmZa

Re: HLEd error for French data set
User: amza
Date: 7/19/2010 6:34 am
Views: 203
Rating: 16

Problem's solved. What I did was that I created a new blank text file, then wrote the first line of the codetr.scp into that new file by hand. After that, I copied the second line until the last line of the codetr.scp into that new file, and then saved it. When I tried to run the command again, it worked!

I don't know why, but it worked!

 

And for the HLEd command, I made my own script to do exactly the same thing as what the HLEd command does. Or probably you could try the same trick as what I've done above.

 

regards,

AmZa

PreviousNext