I have been porting my music production app to Android, and some features
CAN NOT BE IMPLEMENTED without lower latency, period. This includes any
feature where a dynamic sound is to be generated by user interaction. Some
people have said "well, there is this piano-application that has low
latency", but those apps are not generating a continuous stream of audio,
dynamically...  So I can't do what they do.. We need to have audio stream
objects with short buffers, basically.. It feels sad when I know what I
could do if someone just got their a** out of bed one day!

There seem to be people who have patched Android to get low latency, like
this: http://arunraghavan.net/2012/01/pulseaudio-vs-audioflinger-fight/

With pulse audio we are talking almost ten times faster latency than stock
Android AudioFlinger! And the work is open source! I sure wish Google would
just lift that and make the AudioFlinger wrapper as suggested! Or just fix
AudioFlinger, if they wanna invent the wheel again... I don't care about
how they do it, JUST DO IT already!

     /Anton

On Mon, Dec 12, 2011 at 4:44 PM, RLScott <[email protected]> wrote:

> Could you please summarize the current state of audio latency and
> which applications are hurt by the current latency?
>
> On Dec 11, 5:48 pm, Bh1 <[email protected]> wrote:
> > Hi,
> >
> > Recently there have been discussion on the andraudio list about the
> > perplexing lack of progress for low latency audio on the android
> > platform over the past three years.
> >
> > We have kicked around a few possible options like reworking and
> > testing the stack on CM7/9, modifying TinyALSA to allow an API for low
> > latency, adding JACK support or lobbying the developers of the
> > existing audio stack to sort this problem out. Others have suggested
> > that the real solution is to fix AudioFlinger and AudioHAL layers and
> > get that merged upstream.
> >
> > However the real question is after three years of constant development
> > why has audio latency got worse across the board instead of better? Is
> > it even worth anyones time to try to get something better in place as
> > there appears to be an agenda to make sure that android is not
> > suitable for pro audio requirements.
> >
> > Without any information from the people who are responsible for the
> > current state of the audio stack we are all just guessing as to how we
> > can fix this problem or if it is even possible or desired by the
> > Google team.
> >
> > --
> > Patrick Shirkey
> > Boost Hardware Ltd
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to