[Olympus developers 181]: Re: problem with apollo

[Aasish Pappu]

Hi Thomas,

If you are using Olympus 2.5, then it uses sphinx VAD(I presume) for
endpointing. If not, then you may want to see if the IMCore.cpp has any
magic configuration (precisely Pause Threshold and other thresholds )
written inside the code. I know that Ben wanted to put that magic
configuration out of the code into AudioServer.cfg, but I am not sure if it
is the case.

-Aasish

On 17 February 2010 16:09, Thomas Harris <thomas at edalytics.com> wrote:

> I'm having an endpointing issue with the olympus trunk on an application
> built with mostly meetingline configs. Everything is getting prematurely
> endpointed. It looks like a bug in Audioserver or its configuration. Has
> anyone seen this, or better yet (not seen it with some particular version
> and config).
>
> From Pocketsphinx:
> [STD at 15:55:47.691 (10909)] Processing command: engine_begin_utt 000 6070
>
> From Apollo, 40ms later:
> [WAR at 15:55:47.731 (10951)] Too much time since last partial result arrived
> (4381>2000),endpointing here, regardless of VAD.
>
> I'm finding it hard to say much in 40ms :)
>
> Thanks,
> -Thomas
>



-- 
Aasish Kumar Pappu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20100217/6f9c5183/attachment.html