Live data from Hacker News

Sub-10ms roundtrip audio latency on Android

superpowered.com

21–30 of 50 posts

Re: Sub-10ms roundtrip audio latency on Android

#21
post #9

How does this compare to the existing audio tunneling in some versions of Android? (The best writeup of this I've seen is https://github.com/felixpalmer/android-visualizer/issues/5 which details some of the problems that audio tunneling can cause)

A good first step is probably to read Android's own current situation page on the matter and look at the numbers.

http://source.android.com/devices/audio/latency_measurements...

Basically it has been getting and better with new versions of Android and better hardware, but it still has room for improvements.

Re: Sub-10ms roundtrip audio latency on Android

#22
post #5

What's iOS' audio latency?

About 7-12 ms. Actual benchmarks by an audio SDK maker here: http://superpowered.com/latency

And it's been like that for a long time. Last time I did mobile audio programming (2009? 2010?), the Android test devices I had (Galaxy S2?) were operating around 100ms audio latency. Glad to see they've improved!

Re: Sub-10ms roundtrip audio latency on Android

#26
post #24

Does this mean we can finally have an app that'd invert the input from the microphone and play it back on the loudspeaker effectively performing surrounding ambient noise cancellation?

Ambient noise cancellation is more complicated than that. Consider that as you changed your distance from the speaker you would be going into and out of phase with the signal, you would effectively be doubling the ambient noise at some locations, and cancelling it at others.

Also 10ms response time would definitely be too slow for such an application.

If that worked, you could just use an opamp with a sub-microsecond response time with a cheap mic and speaker for a couple of dollars, and I'm sure China would have flooded the market.

I would give anything for a working ambient noise canceller. I would point it at the leafblowers outside while I sip champagne.

Re: Sub-10ms roundtrip audio latency on Android

#28
post #18

Earlier quoted context omitted.

"We updated our findings with the recent improvements in Android M (Marshmallow), and recently released a solution for Android’s USB audio and MIDI challenges, opening a market of 1.1 billion devices for pro audio application creators." Those are two separate things: 1. Updated analysis on the latency with regards to Marshmallow. 2. Superpowered USB Audio and MIDI SDK opens a market of 1.1 billion devices.

A brief skim of the article they link regarding Marshmallow [1] provides this quote: > As readers may recall, 10ms round-trip audio latency is the threshold that must be met by Android to be considered truly 'pro audio'. This wasn't possible before Marshmallow (per aforementioned article), and therefore pro-quality audio apps are still only truly possible on 10% of Android devices. So the market is opened up for 100…

It's open to more of them the 10% that currently have it. Whether the OEM provides a build of Android Marshmallow or not plays a roll for most consumers. Quite a few consumers have the option to unlock their device and bypass the OEM to get Android Marshmallow on their device (Cyanogen et al).

Re: Sub-10ms roundtrip audio latency on Android

#29
post #25

What's iOS' audio latency?

And how about macOS?

Depends on how good your soundcard's drivers are. But I think Mac OS X is capable of something like 48 samples at a bare minimum? Therefore it depends on the sample rate you're using as well. Higher sample rates yield lower latencies but higher CPU usage. At 44.1khz that's about 1ms.
Post reply on HN