Home › Forums › OpenEars › openears/ps speed

Tagged: 

This topic has 2 voices, contains 1 reply, and was last updated by  Halle 183 days ago.

Viewing 2 posts - 1 through 2 (of 2 total)
Author Posts
Author Posts
November 17, 2011 at 5:51 pm #8093

ecret

Hello folks

I am newer to openears but a longtime sphinx user. I am trying to optimize for the iphone and was hoping if anyone had some experience on this.

I initially tried a custom AM that I made, but to compare with you all, I tested with hub4wsj and voxforge.

But after updating to pocketsphinx 0.7, hub4wsj did not seem to work with openears. I did not spend serious time yet debugging this. So I am testing with voxforge.

I can tune the beams and limit the states but the best I roughly get on my ipad is a 3-5RT speed. I am doing ps_decode_raw to test.

Has anyone encountered the hub4wsj AM not working with openears after following the instructions to update to 0.7 and, any idea why its so slow with voxforge? I made sure it was working with FIXED_POINT but a bit stumped. I intend to spend time this weekend and will provide my results to the above questions as well.
November 17, 2011 at 7:39 pm #8094

Halle

Has anyone encountered the hub4wsj AM not working with openears after following the instructions to update to 0.7

For this, just turn on the debugging output as described in this post and it will probably tell you exactly what the issue is: http://www.politepix.com/forums/topic/install-issues-and-their-solutions

Why specifically do you want to use .7? Is it due to a particular bugfix for an issue in .61 which is included in .7 or a generalized interest in the new version? Because I haven’t yet seen .7 doing faster or more accurate recognition with OpenEars than .61.
Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.