For the quick & dirty method I mentioned on 3/15, feedback the audio output into the audio input, record the signal to a file using a separate computer, and generate an impulse. Open up the recording file with an audio analysis app such as Audacity or similar. The time between successive peaks is a rough approximation of the sum of input and output latencies. Note that this method does not isolate the individual input & output components, nor does it distinguish the various kinds. For that you need to use one of the more accurate methods mentioned.
On Apr 13, 10:50 pm, Jackie <jackie...@gmail.com> wrote: > On Mar 15, 11:05 pm, Glenn Kasten <gkas...@android.com> wrote:> For more > accurate measurements of audio output latency, one method is > > to send an impulse through audio out at same time as a known low > > latency path (for example a level change on a GPIO parallel output > > pin), and compare the times to see the audio impulse out and the level > > see the audio impulse out ? How can I do this with high accuracy. You > know, I can not depend on my ear. And I just have a Nexus S, and no > hardware access. > Is it possible to get following data with high accuracy by API/ > software? > 1. cold output latency > 2. warm output latency > 3. continuous output latency > 4. cold input latency > 5. continuous input latency > > > change. A similar method, in reverse, could be used for audio input. > > > On Mar 14, 12:20 pm, "David O." <ave...@gmail.com> wrote: > > > > Is there a standardized/preferred method for validating the section > > > 5.3 Audio Latency requirements? It's not clear to me if CTS covers > > > audio latency testing. > > > > Thanks, > > > David- Hide quoted text - > > > - Show quoted text - -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
