An update on Android's audio latency
android-developers.googleblog.com
An update on Android's audio latency
1–10 of 171 posts
Re: An update on Android's audio latency
#2More 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.
Re: An update on Android's audio latency
#3Re: An update on Android's audio latency
#4As the article says, there is room for improvement, so I guess it's good to see that the long term goal is 10ms round trip.
Re: An update on Android's audio latency
#5"Popular smartphone" list only samsung smartphone.
Samsung
Redmi
Oppo
Huawei
Vivo
Which probably account for the majority of Android smartphone sales.
Re: An update on Android's audio latency
#6Andrew Huang recently made a YouTube video [0] that provides some insight from the perspective of a music producer and someone who recently created a music production app. It's not overly technical, but it highlights some of the challenges one might face. As the article says, there is room for improvement, so I guess it's good to see that the long term goal is 10ms round trip. [0] https://youtube.com/watch?v=-sPbcTcU…
But then the video takes a strange turn and starts talking about "Stability" of mac vs PC, and I had to turn it off. It made the argument that "I haven't seen any professional producers use anything except macs" as its main argument.
It would have been nice to hear some more technical information like mentioning core-audio, or something else.
Regarding the article itself. I'm excited that Android is target less than 20 ms round-trip latency. I'm hoping that this work can be brought back to the Linux Desktop. Messing around with Jack and dealing with xruns is something I wish I could stop doing.