I would plug the device into a computer with a reliable soundcard, an impulse
and timestamps coming from a common clock reference, together with some kind of
time filtering such as a delay locked looped, to suppress jitter/drift. This is
a bit of a complex topic. I recommend that you ask on the And
I hope to get more accurate result. I already understand your quick &
dirty method.
Since CDD section 5.3 has mentioned the accurate data, I hope to get
the exact data on my Nexus S.
How can do this?
On Apr 14, 11:00 pm, Glenn Kasten wrote:
> For the quick & dirty method I mentioned on 3/15, feed
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
On Mar 15, 11:05 pm, Glenn Kasten 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
A quick and dirty method to measure the sum of input + output latency
is to feedback the speaker output to mic input and then measure the
time from an impulse out to the time when the impulse is received back
in. Of course this does not isolate the component times, but it gives
a rough estimate of
