[bloomqvist]

Halle,

Thanks for the response to the first two questions. How about the last question? Let’s say OpenEars does its job as usual, but as it is receiving audio buffers and recognizing spoken commands, we can tap in to the audio buffer event processing. Can we then observe audio buffer events, so each time a new buffer arrives we can grab a copy of the audio buffer for the app’s other purposes?

The reason I am asking this is that we cannot work with the wave file. What we are doing with the audio file requires the same level of low-latency that OpenEars provides for speech recognition (we need to process audio buffers nearly simultaneously alongside OpenEars).

Thanks

[bloomqvist]

You said it’s not possible via an API method. Is there another method?
Is there a way we can pass audio buffers directly to Sphinx recognition methods?

If this is not possible, then how about the opposite? Let’s say OpenEars insists on controlling the mic. Can we then observe audio buffer events, so each time a new buffer arrives we can grab a copy of the audio buffer for the app’s other purposes?

Thanks
Bloomqvist

[Author]

Posts