SaveThatWave: how to avoid truncation – Politepix /forums/topic/savethatwave-how-to-avoid-truncation/feed/ Tue, 23 Apr 2024 14:44:10 +0000 https://bbpress.org/?v=2.6.9 en-US /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017100 <![CDATA[SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017100 Wed, 01 May 2013 05:13:58 +0000 gman Hello,

I am testing the demo version of SaveThatWave. It works well, but the file are truncated. The last .5 second or so of the utterance is missing from the saved wave. Changing pocketsphinxController.secondsOfSilenceToDetect does not help (not surprisingly).

I did not fins any other property to adjust in the docs. How can I avoid the issue?

Thank you.

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017101 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017101 Wed, 01 May 2013 06:39:02 +0000 Halle Winkler Welcome,

Is this on the Simulator?

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017110 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017110 Thu, 02 May 2013 05:12:59 +0000 gman Yes, this is in the simulator. I did not have the opportunity to ty on a device yet. Should I expect a different behavior?

 

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017112 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017112 Thu, 02 May 2013 06:46:41 +0000 Halle Winkler It’s possible. The issue with the Simulator is that it just hosts your own desktop or laptop audio devices. Since it would be a huge, unbounded job for Apple to try to address every possible audio hardware combination in a computer (including external hardware) and really simulate iPhone audio sessions with it, they don’t try — the Simulator doesn’t actually emulate audio session code and that means (for instance) that your audio equipment might even be recording at a different sample rate than an iPhone would, among other possible differences like default buffer size or latency. For those same reasons, I also don’t put a lot of time/energy into trying to make OpenEars and its plugins behave identically on the Simulator as on the device because there will always be a new scenario to fix and it’s work that won’t improve the enduser experience of your OpenEars-enabled app. So OpenEars has a much simpler audio driver on the Simulator and it won’t always work as well as the device driver, which is much more strenuously tested.

If you’re still seeing this behavior on the device, definitely let me know!

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017115 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017115 Thu, 02 May 2013 15:13:56 +0000 gman Thanks for the explanation – makes sense.

I did a quick test on a device (iPhone 5) and I seem to observe the same behavior on some of the recorded files but not all. This is using a headset with mic to record. I’ll do longer test within a day or two and report back.

 

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017116 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017116 Thu, 02 May 2013 15:21:02 +0000 Halle Winkler OK, if you find truncation on the device let me know about it along with the Xcode version, iOS version, and device so I can replicate (also what kind of headphone we’re talking about if it isn’t the one which ships with the device). It’s also very useful to get some idea of what the input speech was like.

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017117 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017117 Thu, 02 May 2013 15:22:56 +0000 Halle Winkler BTW, is this in a new app made using the tutorial, or is it added to an existing app? It’s possible that other aspects of an existing app can have an effect on the audio session, so let me know if there is anything special about the app.

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017119 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017119 Fri, 03 May 2013 05:32:02 +0000 gman I did more testing, and I verify the behavior is identical on devices.

Here is the setup. I tested on an iPhone 5 and iPad 3, both running IOS 6.1.2. I remove all headsets and used the built-in mic.

Truncation occurs on both devices. The symptom is that the last 200 to 500ms  are cut out. The input is typically two or three words, and it sounds like the last syllable or so is missing. I tried with longer sentences, and the problem is identical no matter how long the input is. The portion of recording between the start and the truncation sounds fine.

The truncation occurs on each recording and is perfectly reproducible.

This is in an app which opens an audio session for playback only. For these tests, I turned off playback, although the audio session is still opened. I have been testing PocketSphynx for some time in this app with audio playback on with problems.

Aside from being embedded in the app the code is taken directly from the tutorial. It is largely unchanged, except that the model is usually changed between utterances. Whether the model is changed or not does not affect the truncation behavior.

wavWasSavedAtLocation:(NSString *)location doesn’t do anything else then logging the location.

pocketsphinxDidReceiveHypothesis calls a new delegate method which triggers an animation if the recognition is successful. Presumably that happens after the recording is save and does not interfere with the saving of the input.

I tried setting pocketsphinxController.processSpeechLocally = FALSE and interestingly that does not work. wavWasSavedAtLocation does not get invoked anymore, and the log shows a continuous loop of “Pocketsphinx is now listening.” instead of just one when it’s set to true.

Will purchase if we get it to work, let me know if I can provide more info.

Thanks!

 

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017123 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017123 Fri, 03 May 2013 07:55:40 +0000 Halle Winkler Can you elaborate on this:

This is in an app which opens an audio session for playback only

How does the app set the audio session?

]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017125 <![CDATA[Reply To: SaveThatWave: how to avoid truncation]]> /forums/topic/savethatwave-how-to-avoid-truncation/#post-1017125 Fri, 03 May 2013 08:46:19 +0000 Halle Winkler (To clarify, I’m not disagreeing with or doubting your observation of the behavior, I just have a bit of a backlog so I’m trying to get all my ducks in a row before getting into this issue — it’s already entered as a bug and will get looked at).

]]>