| Re: Re: Re: Re: Re: Re: Problem with a Source dire
Feb 11 2013 on content Simon |
Ah, I forgot it's named "sphinxtrain.exe" - that's the one I mean.
And, no I can not give you my .kde directory as it *really* wouldn't help for many, many reasons which include "I'm using Linux", "all the paths would be wrong" and "I don't have a Simon setup that would help you in the first place". |
|  | | Re: Re: Re: Re: Re: Re: Problem with a Source dire
Feb 10 2013 on content Simon |
Weird. I can take your configuration folder, download and extract it and build the model *just fine* with your configuration.
Most likely this is either a problem with the packaged version of SPHINX or the way it is packaged.
Checking your permissions would actually be a good idea at this point. If you're using a restricted user account, try to run Simon as an administrator.
What would also be great is, if you could try to manually compile the model that fails when building through Simon.
For example, let's pick the one I tested (appears to be your latest one):
Open the command line again and navigate to "%appdata%/.kde/tmp-FERNANDO-PC/simond/default/compile/sphinx/default{58d70da8-c481-4899-96a4-51ffb08a84}"
Then, execute the following (I don't have a Windows installation in front of me so maybe you'll have to fudge the file names / paths a little bit but it should be straightforward changes if there are any at all): "C:\Simon\bin\python.exe C:\Simon\bin\SphinxTrain"
After this finishes executing, open up the default{...}.html file in this folder. This is the log of the model compilation process.
It will still contain the log of the earlier invocation (through Simon) but will also show the new protocol at the end.
The steps are numbered and timestamped you should find the start of the new training session pretty easily.
There should be no errors *until* the last step (called "MODULE: DECODE Decoding using models previously trained"). There will be errors in that step even if everything went alright. Do you see that or do you get the same warnings as in the earlier invocation (mfc files empty or missing with a path that points to a .mfc file that is neither empty nor missing)? |
| | | Re: Re: Re: Re: Re: Re: Problem with a Source dire
Feb 8 2013 on content Simon |
Oh, also, can you please run in a command line ("cmd" in the windows run dialog) the following command and paste the full output?
C:\Simon\bin\sphinx_fe.exe \
-c c:/users/fernando/appdata/roaming/.kde/tmp-fernando-pc/simond/default/compile/sphinx/default{3375fa4e-64e0-4c9e-bbe3-649e97b9704d}/etc/default{3375fa4e-64e0-4c9e-bbe3-649e97b9704d}_train.fileids \
-part 1 \
-npart 1 \
-di c:/users/fernando/appdata/roaming/.kde/share/apps/simond/models/default/samples/ \
-ei wav \
-do c:/users/fernando/appdata/roaming/.kde/tmp-fernando-pc/simond/default/compile/sphinx/default{3375fa4e-64e0-4c9e-bbe3-649e97b9704d}/feat \
-eo mfc \
-nist no \
-raw no \
-mswav yes \
-samprate 16000 \
-nfilt 40 \
-lowerf 133.3334 \
-upperf 6855.4976
Best regards,
Peter
Ps.: If the output is too long for the scrollback buffer, you can redirect it to a file ("command > outputfile"). |
| | | Re: Re: Re: Re: Re: Re: Problem with a Source dire
Feb 8 2013 on content Simon |
You upload the folder containing Simonds temporary files.
This does not include training data which is to be found in c:/users/fernando/appdata/roaming/.kde/share/apps/simond/models/default/samples/
Could you please upload those, I'm curious now...
Best regards,
Peter |
| | | Re: Re: Re: Re: Re: Re: Problem with a Source dire
Feb 7 2013 on content Simon |
Interesting. In your error log, SPHINX complains about missing / corrupt audio samples. That might be the root cause of all this.
Specifically, these three samples are mentioned:
LINK_CLICK_S1_2013-02-06_21-02-56.0
LINK_CLICK_S1_2013-02-06_21-30-10.0
LINK_CLICK_S1_2013-02-06_21-35-01.0
Those are not all your samples, are they?
(The log also tells that your *whole* trainings corpus is about 46 seconds long - WAY too little for a sensible model, obviously)
Can you check out these samples (main window > Manage training data) and see if you find anything odd about them?
Did you by any chance manipulate some samples directly (file system) instead of through Simon? Are you using a remote Simond server?
Btw. if you are planning for a larg(er) scale deployment and are looking for professional consulting, my colleagues at Simon Listens (http://simon-listens.org) will surely be happy to receive your inquiry.
Best regards,
Peter |
| | | Re: Re: Re: Re: Re: Re: Problem with a Source dire
Feb 5 2013 on content Simon |
Okay; So I've looked at your archive and everything in there is *fine*.
Both models completed as successfully as possible - but I saw that you've only recorded a total of 4 training samples.
For an improved adapted model, I'd say you need *at least* 50 times as much.
I also tried rebuilding the model from your input files and that worked as well. I then tried to adapt a model on Windows and that was fine too (I normally test on Linux).
So two questions:
1. If it gives you trouble: Do you need an adapted model? Why? Have you tried the Voxforge English model (with the matching scenarios) if HUB4 is not accurate enough?
2. If you absolutely need to do this, please run another round of training (at least 20 samples) and write down everything you do and everything that Simon does (every message, every error, whatever) - make sure you include any "additional information" (or "details") if Simon provides some.
Best regards,
Peter |
| | | Re: Re: Re: Re: Re: Problem with a Source director
Feb 5 2013 on content Simon |
The message that the source directory does not exist is a symptom of a failing model compilation.
If you still get this, I need the full build log that is a .html file to be found in c:/users/fernando/appdata/roaming/.kde/tmp-fernando-pc/simond/default/compile/sphinx/default{<current id>}/ where "<current id>" refers to the model id (should be visible in the error message Simon shows you).
Please post it somewhere and provide the link here. |
| | | Re: Compiling Simon 0.4.0 under Windows
Feb 5 2013 on content Simon |
I seriously recommend using the provided installer.
If you don't want that, uninstall cygwin (important), set up emerge according to the instructions here techbase.kde.org/Getting_Started/Build/Windows/emerge and run "emerge simon".
Be warned, though, there will likely be a couple of tough hurdles to solve before you can successfully compile Simon on Windows. |
| | | Re: Re: Re: Problem with a Source directory existe
Jan 28 2013 on content Simon |
Again, please try installing Simon to a space-free prefix. |
| | | Re: Problem with a Source directory existence
Jan 28 2013 on content Simon |
Hm, SPHINX seems to have trouble with spaces in paths. I thought I caught and fixed all of those but apparently, I missed some in the final tarball.
Could you try if installing Simon to C:\Simon instead of C:\Program Files\Simon fixes the problem?
Best regards,
Peter |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
