Re: [Jack-Devel] JACK on mobile

Hi Bradley!

Its OK, I did receive your reply. AFAIK the jack-devel list is configured
so that you don't receive your own posts. To save your time I thought it
best to copy the list into my reply as I have a few questions that I think
the list would be interested in too.

What is it you are wanting JACK for Android for? I should imagine console
apps (like ecasound and nama) should be portable with any modification to
the source? Will this be the case?

Qt5 supports Android but how well and how realistic would an Android
qtractor port be? Rui says qtr is Qt5 ready so that should help.

Are you writing a qjack/patchage equivalent for Android too?

Thanks Bradley!

Dan


On Tue, Oct 22, 2013 at 4:39 AM, Bradley Justice
<[hidden]>wrote:

>
> I never received my reply to you through the JACK list, don't know what
> happened. So I am also responding to you personally.
>
> JACK on Android requires a special distro. This is primarily to permit
> real-time priorities and memory locking.
>
> Clients, however, are distributed as APKs.
>
> Brad
>
>
> On Thu, Oct 17, 2013 at 1:54 AM, Dan MacDonald <[hidden]> wrote:
>
>> V. interesting news Bradley - it seems to have totally gone over Pat's
>> head, unless he replied to you privately.
>>
>> It sounds like your Android JACK port isn't functional yet but is someway
>> towards working. Will we need to flash a custom JACK distro to use your
>> port or will it eventually be available as a regular apk for anyone to
>> install?
>>
>> Christian:
>>
>> JACK iOS is dead already? Why? There is no mention or explanation of its
>> passing on its homepage that I can see.
>>
>>
>> On Wed, Oct 16, 2013 at 6:07 PM, Bradley Justice <
>> [hidden]> wrote:
>>
>>> Very interesting comments on pro audio and mobile platforms, lots here
>>> to investigate.
>>>
>>> I have been looking at Android as a platform for pro audio applications.
>>> I am also convinced that true low latency audio on mainstream Android is
>>> not an achievable goal. Google priorities, e.g. maintaining call quality
>>> and  low power consumption, render it so. What is achievable is the more
>>> modest goal of an Android distribution specifically instrumented for pro
>>> audio applications. This is still a worthy goal, especially if you consider
>>> Android as an embedded system that can run on a low cost dedicated device.
>>>
>>> I have a functional prototype of a pro audio Android distribution
>>> running on the Nexus 7. At the end of round 1 of the latency wars I am
>>> reliably running Simple Client using USB audio at 96k with buffers set at
>>> 512 X 2. To accomplish this, JACK and its clients run in native space
>>> directly on top of ALSA with client user interfaces running as standard
>>> Java Android activities. I am currently finishing up work on client
>>> installation and configuration; I hope to return to the latency issue soon.
>>> There are approaches I have yet to explore, such as application of the
>>> real-time patches.
>>>
>>> This work highlights the critical difference between Android and iOS:
>>> with iOS you are restricted to what Apple decides to provide in terms of
>>> hardware and system software. With Android, if there is a problem that
>>> needs corrected, such as audio drivers, you have the ability to do so.
>>>
>>> I do have a question regarding iOS and audio latency. Does anyone on
>>> this list have reliable metrics? I have seen some low figures reported on
>>> Internet postings. However, figures I have encountered from individuals who
>>> actually measured it seem out of range for pro audio.
>>>
>>> Brad Justice
>>>
>>> 
>>> Jack-Devel mailing list
>>> [hidden]
>>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>>>
>>>
>>
>

1382434027.459_0.ltw:2, <CANOoOjscOEPjAH7PEoZRtRizj2t_X_0O30=7_podbz5+TSzKXw at mail dot gmail dot com>