<div>Hi Thomas,</div><div><br></div>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.<div>
<br></div><div>-Aasish<br><br><div class="gmail_quote">On 17 February 2010 16:09, Thomas Harris <span dir="ltr"><<a href="mailto:thomas@edalytics.com">thomas@edalytics.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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).<br>
<br>From Pocketsphinx:<br>[STD@15:55:47.691 (10909)] Processing command: engine_begin_utt 000 6070 <br><br>From Apollo, 40ms later:<br>[WAR@15:55:47.731 (10951)] Too much time since last partial result arrived (4381>2000),endpointing here, regardless of VAD.<br>
<br>I'm finding it hard to say much in 40ms :)<br><br>Thanks,<br><font color="#888888">-Thomas<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Aasish Kumar Pappu<br><br><br>
</div>