Re: [Jack-Devel] JACK on mobile

Patrick, with the greatest respect, I think that you are totally barking up
the wrong tree here. And I mean, really the wrong tree. Everything you are
talking about doing seems to add up to a set of band-aids that all fail to
address the core problems with audio on Android. Audio on Android is just
fine unless you care about latency. None of these proposed integrations
with PA are going to make it a platform that can begin to compare with iOS
for music/pro-audio apps.

Ironically, I was talking to a guy at Google who was trying to hire me
yesterday and I (mostly joking) said "the only thing I'd want to do at
Google is fix audio on Android". He then tried to convince me that he could
make that happen.

--p



On Tue, Oct 15, 2013 at 3:27 PM, Patrick Shirkey <[hidden]
> wrote:

> Hi,
>
> Recently there have been discussions about the viability of getting
> official JACK support into the mobile audio stack. Currently JACK is left
> out of the mix and Pulse Audio is the default audio system layer.
>
> For most consumer mobile use cases this is not a problem but when it comes
> to professional audio and some specific cases with very hard time limits
> for the audio graph JACK can actually be preferable over the PA API and
> logic.
>
> A few things have been identified that make it hard to just drop JACK into
> the mobile audio stack at this point.
>
> 1: Bluetooth support especially for hands free audio
> 2: "Murphy" system daemon support
> 3: Dealing gracefully with apps that use the PA api
>
> On the PA mailing list we have identified several optimisations that can
> be done to PA that would allow PA and JACK to coexist peacefully and cause
> minimal system disruption from the developer/user perspective.
>
> However, they are mostly required to allow JACK to run and that is not a
> core priority for the PA developers. On the other hand it seems that JACK
> developers are not going to be interested in spending time on optimising
> PA.
>
> So this leads to a slight issue. Is it likely that JACK will be able to
> support both the Bluez and Murphy API's in order to be a drop in
> replacement for PA while it is running on a mobile OS? Or is it better to
> put the time into optimising PA so that we don't have to double up on
> development efforts considering that the PA developers already provide
> Bluez and Murphy support and are funded to work on that part of the audio
> layer?
>
> The optimisations that would enable PA to work better with JACK are not
> trivial and will require some pretty heavy thought and a fair sized chunk
> of time commitment to make them happen.
>
> Its possible that we could get some assistance from the Linux Foundation
> for the development process if we have a good plan and they agree that it
> is an important project. In addition several of the PA developers work at
> Intel and Ubuntu so there might be some support from those areas to
> provide a fully professional and highly optimised audio stack for Linux
> based mobile OS's.
>
>
>
> --
> Patrick Shirkey
> Boost Hardware Ltd
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>

1381867409.6388_0.ltw:2, <CAFa_cKn-uowTB97y36_OAqA5YbAsoGpYXDOazd+3FudQY3xK5w at mail dot gmail dot com>