- This topic has 6 replies, 2 voices, and was last updated 10 years, 10 months ago by .
-
Posts
-
SaveThatWave wrote a date to the filename, if I’m right. Is that the time of writeout success?
If so, then if that date is earlier than hypothesis callback timestamp, I can safely suppose that they’re paired (the wave file with a given hypothesis)?
Should I stop my saveThatWaveController on every detectFinishedSpeech/stopListening/suspendRecognition, or it will be stopped automatically (so the wasSaved will be invoked on every case )?
Sorry for this many question, but that wavWasSaved holds really no information about the content in it.
If so, then if that date is earlier than hypothesis callback timestamp, I can safely suppose that they’re paired (the wave file with a given hypothesis)?
I would expect this assumption to be correct. It is difficult to imagine a circumstance under which a hypothesis will return before the wav is able to be written out. But you won’t always have a matching hypothesis for a WAV because not every hypothesis has content. You can decide what you’d like to do about those cases since it will vary from project to project.
Should I stop my saveThatWaveController on every detectFinishedSpeech/stopListening/suspendRecognition, or it will be stopped automatically (so the wasSaved will be invoked on every case )?
You should just leave it running; it will only do something when it has speech to save.
Sorry for this many question, but that wavWasSaved holds really no information about the content in it.
The only thing it knows about is the timestamp, since it isn’t bound to recognition, which is a positive thing because it means you can run it with recognition turned off in order to use OpenEars as a voice activity detector, or with n-best recognition on (many hypotheses for a single utterance, some of which are null) or when a null hypothesis is silently returned such as happens for the majority of hypotheses when using Rejecto. Although SaveThatWave works well with hypotheses, it saves all detected speech, not all non-null hypotheses.
That would definitely be my expectation. Since this is the first time I’ve heard of this use, it would be great if you could let me know if that expectation is correct, but I’d be pretty surprised if it weren’t.
If you are worried that a recognition might sometimes take less time than a file write (I’m not sure I would worry about this in practice), you can keep an int property that is the number of WAV writeouts and another that is the number of returned hypotheses and do something special when a hyp returns and the number of hyps is larger than the number of WAV writeouts. It is also a good way to test whether I’m right.
- You must be logged in to reply to this topic.