What's the equivalent latency on an iPhone?
The most common results on this page indicate that it varies with buffer size, but could be 9-11 ms for iPhones. https://superpowered.com/latency
An update on Android's audio latency
21–30 of 171 posts
Re: An update on Android's audio latency
#22Too little, too late, I'm afraid. The improvement is great, but I think the audio professionals jumped ship long ago to Apple, and they're not going back. I know of several music professionals plugging into their Macbooks or iPads as part of the pre-amp, but I don't know if any using Android. Google sat on this for way too long while Apple courted the creative professionals, and for any that have already made the upf…
Perhaps. Though I wonder if every musician afford Macbooks or iPads. These things are not cheap, especially if you consider earnings of non-US based musicians, etc.
Disclaimer: Googler, but opinions are my own.
Re: An update on Android's audio latency
#23Too little, too late, I'm afraid. The improvement is great, but I think the audio professionals jumped ship long ago to Apple, and they're not going back. I know of several music professionals plugging into their Macbooks or iPads as part of the pre-amp, but I don't know if any using Android. Google sat on this for way too long while Apple courted the creative professionals, and for any that have already made the upf…
Perhaps. Though I wonder if every musician afford Macbooks or iPads. These things are not cheap, especially if you consider earnings of non-US based musicians, etc. Disclaimer: Googler, but opinions are my own.
This is where Apple's far superior product lifecycle comes in: Buying a four year old Apple product is affordable, still runs the current OS, unlike Androids that old, and has the audio performance down.
Re: An update on Android's audio latency
#24The figure of most interest to someone playing an electronic instrument is "tap-to-touch latency". The article indicates a minimum of 43 ms for that (28 round trip latency - 5 audio input latency + 20 touch latency). That's like ten times what you'd hope for.
deleted
Re: An update on Android's audio latency
#25It'd be nice if something was done about the extra 100-200ms (!!) of latency that Bluetooth headsets can add[1]. I understand this is largely a problem from the manufacturer problem, but I'd love to see Google lead the way with some sort of certification program, or even make their own low cost BT chipset for 3rd party headphones to use, to improve the situation.
Of course Android is already world's better than desktop, where 200ms is seemingly closer to average than an outlier.
It is also kind of cool that perusing that chart, it seems headsets connected to Android have, on average, lower latency than when connected to iOS!
https://www.rtings.com/headphones/tests/connectivity/bluetoo...
Re: An update on Android's audio latency
#26It'd be nice if something was done about the extra 100-200ms (!!) of latency that Bluetooth headsets can add[1]. I understand this is largely a problem from the manufacturer problem, but I'd love to see Google lead the way with some sort of certification program, or even make their own low cost BT chipset for 3rd party headphones to use, to improve the situation. Of course Android is already world's better than deskt…
There are low latency bluetooth protocols, if you sort by latency on rtings for aptx-LL you can see some headsets are down below 40ms. Of course, this relies on both the host and the headset having support for the protocol and being engineered well. SBC and aptX just aren't designed for low latency, and low latency is something that can't be hacked into every codec after the fact.
Re: An update on Android's audio latency
#27Earlier quoted context omitted.
That was a strange video. It seemed like he started talking about latency between Android and IOS devices, which makes sense given that this article talks about response time of just under 40 ms like you said. The article says this is "well within the range required for real-time applications" if you define real-time applications as non-pro-audio stuff. If you're playing an instrument and it takes 40 ms for you to he…
Linux audio can be real bad but the one thing that could possibly make it worse is taking anything from Android. Android is the only computing platform I have ever used that was unable to play a simple audio file through without the audio dropping out at least once (I had the same experience on multiple devices, 5+ years apart). Have you looked at Pipewire?
I've started to. But I haven't done enough research on how all the other applications I use ( Carla, Ardour, soft synths, etc ) will play along with Pipewire instead of jack.
Re: An update on Android's audio latency
#28It'd be nice if something was done about the extra 100-200ms (!!) of latency that Bluetooth headsets can add[1]. I understand this is largely a problem from the manufacturer problem, but I'd love to see Google lead the way with some sort of certification program, or even make their own low cost BT chipset for 3rd party headphones to use, to improve the situation. Of course Android is already world's better than deskt…
There are low latency bluetooth protocols, if you sort by latency on rtings for aptx-LL you can see some headsets are down below 40ms. Of course, this relies on both the host and the headset having support for the protocol and being engineered well. SBC and aptX just aren't designed for low latency, and low latency is something that can't be hacked into every codec after the fact.
apt-x is designed for ransom extraction via "intellectual property" licensing.
Re: An update on Android's audio latency
#29Usually, "an update on [blank]" is euphemism for said product getting cancelled. More to the point, one of PulseAudio's claims was that they consumed less CPU than Android's audio pipeline. With the recent hyped PipeWire, I wonder how that compares to Android's Oboe.
That's actually the joke here, which got a chuckle out of me. The idea is that excessively large audio latency itself has gotten cancelled.
I haven't played with it myself (it's been a few years since I was actively involved in Android audio latency), but from what I've seen, AAudio is pretty good, probably close to what the hardware is capable of. I'd very much encourage people to do empirical measurements against, for example, PipeWire (which also looks good). Do keep in mind that constraints are different on mobile, and things like power management can and do get in the way of down-to-the-wire latency.
Re: An update on Android's audio latency
#30Earlier quoted context omitted.
Perhaps. Though I wonder if every musician afford Macbooks or iPads. These things are not cheap, especially if you consider earnings of non-US based musicians, etc. Disclaimer: Googler, but opinions are my own.
This is where Apple's far superior product lifecycle comes in: Buying a four year old Apple product is affordable, still runs the current OS, unlike Androids that old, and has the audio performance down.
This is a valid point, but it’s hard to place the blame on Google/Android. I think the challenge is less of Android itself but a refusal of the OEMs to support newer OS versions. This makes business sense, but sucks for consumers.
I think Google is doing a better job with their Pixel devices. I honestly hope they try to lead the Android industry more with them.