-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to extend the default dictionary? #19
Comments
You have to recreate the files in $FLITEDIR/lang/cmulex using your new dictionary. |
One more question. Is the "lexicon.out" file represents the new lexicon file, and the content in the file follows the format "word pronounciation"? |
Yes lexicon.out is your new or extended lexicon and has to be build on the format of words pronunciation ie their phonetic representation. You can take help from festival/lib/dicts/cmu/cmudict.out |
Thanks for your quick reply. Your answer has helped me solve the question, so i close this issue. |
Sorry, I've met another problem when i tried to extend the dict. "Also place your lexicon and allowables files in this ‘lex’ directory" in the tutorial, so which files should i exactly put into the lex directory? .out file, allowbles file and more? And how can i generate these files? |
Just 2 files lexicon and allowable. |
I've tried as guided, it can't work and the error info is as follows:
|
The issue is in the build_lts file in which heap value is not declared. |
I remove '--heap HEAP' and re run it, it seems slow. How long it will take to finish the process? |
It should not take long |
I've got it and the process can successfully finish. Thanks very much. |
I've run through the whole process. However, the result seems wrong. With the new dictionary, not only the new word is wrong, but also the original word. What may be the reason? By the way, when run "bulid_lts test", almost all words are failed, is this normal? |
Is there 0 and 1 added with the phonemes in lexicon thats created in lts_scratch ? |
I've checked "lts_scratch/lex_entries.out" and "allowables.scm",some fragments are like below:
and I think they are consistent, how do you think about it? |
Check the log files where there are the unalignments check that the failed ones. |
However, I only add one new word to the original festival cmudict and use the same allowable as cmudict, but the new results become wrong. It's strange for me. |
Your system is not reading the lexicon and falling back to lts rules.
Did you made sure the allowables are not re made an yu commented that line
in build_lex.
Secondly did you replaced the data_raw file with data compressed as
mentioned in the tutorial.
…On Tue, Mar 12, 2019, 9:37 AM attitudechunfeng ***@***.***> wrote:
However, I only add one new word to the original festival cmudict and use
the same allowable as cmudict, but the new results become wrong. It's
strange for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AcqkWFHvpwXe5q9lZUaY6hwY5BG9hh29ks5vVy8VgaJpZM4bG7k->
.
|
I have commented the line "./build_lts make_allowables_smt" in build_lex and replaced the data_raw file with data compressed as mentioned in the tutorial. |
Hi there, I'm following your conversation to expand the dictionary in my system as well. My objective is to upgrade the default CMUdict-0.4 to 0.7b in flite-2.2. Btw, this tutorial is greatly helpful. Regards, |
Hi, |
It's ./build_lts align that takes the longest. What's worse is I've got failed for several words, like: Thanks, |
Ye, I also found the process of "./build_lts align" is too slow. @boredomed @ZhenheZhang Could you share me with the generated files? |
oh, I found the allowable generated from ./build_lts make_allowables_smt is ver large. |
As the title, if I want to add more words which are not included in the default dictionary, what should I do?
The text was updated successfully, but these errors were encountered: