UltraJv wrote:People are working on it - Pulseaudio API (One for the devs) looks promising, quoted as down to 20ms :
http://arunraghavan.net/2012/01/pulseau ... ger-fight/
http://pulseaudio.org/
Low latency audio in Android 4 (Ice Cream Sandwich)
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
Back to the relevant info :
-
- Banned
- 3946 posts since 25 Jan, 2009
True. You have gone straight and I am admittedly the villian now.UltraJv wrote:Back to the relevant info :
UltraJv wrote:People are working on it - Pulseaudio API (One for the devs) looks promising, quoted as down to 20ms :
http://arunraghavan.net/2012/01/pulseau ... ger-fight/
http://pulseaudio.org/
I just though you might were ready for some more entertainment....you know; us trolls in between
But fair enough. Good luck walking the line then.
Peace
-
- KVRist
- 485 posts since 21 Jun, 2010
Android's weakness in real-time audio is the reason why I bought overpriced iPhone 3GS instead of some 2-3x more powerful Android phone. it's a great phone tho, so i'm not complaining + iMachine is fabulous!
-
- KVRist
- 73 posts since 28 Jul, 2010
i'm in exactly the same boat. as soon as theres a version of amplitube or ampkit for android then i'll immediately ditch my iphone.Tehnik wrote:Android's weakness in real-time audio is the reason why I bought overpriced iPhone 3GS instead of some 2-3x more powerful Android phone. it's a great phone tho, so i'm not complaining + iMachine is fabulous!
i'm waiting for android4 to fix this latency issue - otherwise i'll regrettably be upgrading to an iphone 4S.
ive actually used my 3GS as an emergency amp(sim) in sudden live situations.
-
- KVRian
- 1122 posts since 12 Mar, 2005
Did you just buy it recently? The 3Gs and the original Droid (which I had) were out around the same time, and the performance was pretty much the same.Tehnik wrote:Android's weakness in real-time audio is the reason why I bought overpriced iPhone 3GS instead of some 2-3x more powerful Android phone. it's a great phone tho, so i'm not complaining + iMachine is fabulous!
- KVRian
- 1498 posts since 21 Nov, 2005 from The Netherlands
Got android 4.0.3 today, my transformer tf101 tablet is now really fast and music apps are somewhat more responsive!
Notice less latency while hitting notes, not perfect but definitely better then before.
Caustic still shows the same latency, but i'm happy with this update.
Notice less latency while hitting notes, not perfect but definitely better then before.
Caustic still shows the same latency, but i'm happy with this update.
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
Recently got a Galaxy Nexus with ICS. Just tried Caustic demo on it. It reports 89 ms latency. From how it feels I'd guess it's even more. (Though how much of that is on the GUI side is hard to say.) I'm also guessing this figure reflects the buffer size Caustic is pushing to android.media.AudioTrack, which could very well have further buffering after it that's transparent to the app.)XGmode wrote:Got android 4.0.3 today, my transformer tf101 tablet is now really fast and music apps are somewhat more responsive!
Notice less latency while hitting notes, not perfect but definitely better then before.
Caustic still shows the same latency, but i'm happy with this update.
I'll be following this one closely, there's no good reason why latency performance should be so poor. Even if they gave apps the ability to request shorter buffers, that would do it. (And a proper callback function for the audio process, instead of pushing and blocking until the buffer is ready for more.) Then you could tweak latency to what the particular hardware is capable of, just like in the desktop/laptop world. If the hardware can't keep up, oh no, dropouts. We're all already used to that. But to the semi-pro audio uninitiated, I could see them thinking that's failure, thus they might hard code in unnecessarily long buffers. This is exactly why for so long Windows needed a 3rd party driver format, ASIO, in order to do low latency audio before WDM came on the scene and finally caught up/surpassed that performance. Unfortunately, I don't think there's such thing as installable drivers for these phones. (At least not without rooting the thing, replacing the entire OS, and voiding the warranty. Obviously not an option for anyone hoping to widely market an app.)
By the way, this issue has been pushed to #11 on Google's bug list! http://code.google.com/p/android/issues ... ry%20Stars
Keep hitting that star folks! (On this page. http://code.google.com/p/android/issues/detail?id=3434 ) Maybe we can make this problem #1.
-
- KVRer
- 1 posts since 2 Mar, 2012
And you know what it's the #2 defect on the list. I think seeing as how it's defect is next to the Nexus Battery life it's should be getting some attention. The android team has already said they know about the issue. Hopefully they are working on it, they said they were hopeful it would be in ICS but we know it's not.
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
Someone (Windows X) has been working on 5ms - 10ms latency on Samsung Nexus S :
http://forum.xda-developers.com/showthr ... ?t=1621914
Maybe others will follow...
http://forum.xda-developers.com/showthr ... ?t=1621914
Maybe others will follow...
Last edited by UltraJv on Fri May 11, 2012 6:05 pm, edited 1 time in total.
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
I don't see hacking the OS as a viable solution. We need a sanctioned way to do this so we can sell products to everyone. Not just those willing to tinker.UltraJv wrote:Someone has been working on 5ms - 10ms latency on Samsung Nexus S :
http://forum.xda-developers.com/showthr ... ?t=1621914
Maybe others will follow...
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
Its a start, it could end up in sanctioned Android code or it could end up as ASIO4ALL did.AdmiralQuality wrote:I don't see hacking the OS as a viable solution. We need a sanctioned way to do this so we can sell products to everyone. Not just those willing to tinker.UltraJv wrote:Someone has been working on 5ms - 10ms latency on Samsung Nexus S :
http://forum.xda-developers.com/showthr ... ?t=1621914
Maybe others will follow...
-
- KVRist
- 185 posts since 18 Jan, 2011 from Brisbane, Australia
To test, load up a music app, press a key and listen for delay. (?)Sujatha wrote:Can anyone tell me how to test Audio low latency on Android 4, ICS ??
it will be of great help to me
If you want a measurement, you can install Caustic and look in the menu. The app's buffer size is converted to milliseconds and displayed as latency. Note that this does not account for Android's internal mixer buffers or touch latency, there's no easy way to measure that.
You could record audio using an external recorder. The test would be to tap the screen "loudly" and measure the time between the screen tap and the audio coming out of the device.
-
- KVRist
- 55 posts since 14 Mar, 2011 from WI
golemus wrote:I think that is pretty interesting. I have Samsung Galaxy S II which is supposed to be one of the most powerful smartphones out there and I have also Caustic installed. When I play the subsynth screen keyboard there is a clear latency. For comparison I put VST synth to Ableton live, delay behind it and tried to adjust the delay so that both sound to have the same delay. Witch such method I estimate the delay/latency of Caustic to be 150-200ms.UltraJv wrote:No way of measuring it. When I play with the keyboard on Caustic, its instant. My guess is less than 10ms.Sascha Franck wrote:Can you please be more specific? What are the exact numbers?UltraJv wrote: I have it on my LG GT540, it flies as its compiled for performance and latency isnt a problem.
- Sascha
No Cyanogenmod, Gingerbread 2.3.5 and a lot of apps installed.
Samsung devices are the worst in regards to latency. Try a Motorola Device, their response time is really, really good. I used to have a Droid I, and even playing drum pad apps it "felt" really low latency. Now I have a Galaxy Nexus (Samsung) and the latency is terrible. So it depends on what manufacturer you go with. It's not just and "android" OS problem.
