It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
Sub-10ms roundtrip audio latency on Android
11–20 of 50 posts
Re: Sub-10ms roundtrip audio latency on Android
#12It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
It will be useful for apps, esp. those targeting musicians. Iphone had sub-10ms latency for a long time.
Re: Sub-10ms roundtrip audio latency on Android
#13It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
It’s not for phone calls but real-time audio applications, e.g. music creation apps or games.
Re: Sub-10ms roundtrip audio latency on Android
#14It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
It's for real-time music/audio apps, like virtual pianos, etc. These can be 100% local, and excessive latency is frustrating to the user.
Re: Sub-10ms roundtrip audio latency on Android
#15It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
This latency mentioned is useful for music and VoIP apps.
Re: Sub-10ms roundtrip audio latency on Android
#16Awesome stuff. Solid to see such a nice side-by-side integration without interfering with the existing media server.
Thanks!
Re: Sub-10ms roundtrip audio latency on Android
#17It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
Not only is 10ms roundtrip latency critical to the interactive audio type applications mentioned by others -- it is critical for VR too.
Re: Sub-10ms roundtrip audio latency on Android
#18> We updated our findings with the recent improvements in Android M (Marshmallow) > opening a market of 1.1 billion devices Minor nit, but considering that google says Marshmallow is on 10.1% of devices [1], that figure is an order of magnitude too high. [1] https://developer.android.com/about/dashboards/index.html
"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.
Re: Sub-10ms roundtrip audio latency on Android
#19> We updated our findings with the recent improvements in Android M (Marshmallow) > opening a market of 1.1 billion devices Minor nit, but considering that google says Marshmallow is on 10.1% of devices [1], that figure is an order of magnitude too high. [1] https://developer.android.com/about/dashboards/index.html
"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 million devices.
I'm not saying it's not a huge number of devices. But it's not as huge as the blog states.
[1] http://superpowered.com/superpowered-android-media-server
Re: Sub-10ms roundtrip audio latency on Android
#20It often takes over 500ms to get voice through the cellular network. Worrying about 10ms in applications seems excessive.
It's not used for that. It's used for applications that need audio feedback after a trigger. In those cases 14ms+ is already way too much to the point of being unusable. For example: https://www.youtube.com/watch?v=_eE7NtK4jX8