linuxaudio.org

--_3036ee44-a9e1-4200-a989-336b5c16d4e4_

Content-Type: text/plain; charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable
> there are some very cool synths starting to appear for the iPad too=2C

quoted text
> but this is precisely the market that *cannot* (for technical reasons)

> be catered to on Android. its very sad. would i consider an Ardour

> port to an Android that had a reasonable audio subsystem? i would

> definitely look into it. but on android as is: why would anyone bother

> to build synths=2C whether historical replicas or things like

> supercollider=2C or DAWs or FX units etc. on this platform? there just

> isn't any reason.I agree with Fons that it is largely for toys=2C I think=

 that subject came up beforebut hey=2C we are all big kids really.

If you are sequencing then the latency is a non-issue=2C well=2C unless you=

 wantflashing LEDs in step to the music. As long as the different tracks ar=

e in steptheir is not a big problem with lag. FX processing is out of the q=

uestion=2C  andmost live work as you cannot play 42ms of latency.

quoted text
> From: ralf.mardorf@alice-dsl.net

> I did some research. Android on an iPad seems to be something that soon

> or later will be available for everybody.

Alien Android. Man=2C this harks back to the days when people were claiming=

 that the i386 emulator on Mac systems was actually faster than a PC. Dalvi=

cis FOSS and yes=2C it is being ported onto the iPad=2C PlayBook and other =

systems.There are some issues though. If the app uses the JNI then the back=

end libraries are going to be ELF but are there not going to be some linkin=

g problems at run time from the differences between Darwin and Android?

Regards=2C nick. 		 	   		  =
--_3036ee44-a9e1-4200-a989-336b5c16d4e4_

Content-Type: text/html; charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable
&gt=3B there are some very cool synths starting to appear for the iPad=

 too=2C&gt=3B but this is precisely the market that *cannot* (for techn=

ical reasons)&gt=3B be catered to on Android. its very sad. would i con=

sider an Ardour&gt=3B port to an Android that had a reasonable audio su=

bsystem? i would&gt=3B definitely look into it. but on android as is: w=

hy would anyone bother&gt=3B to build synths=2C whether historical repl=

icas or things like&gt=3B supercollider=2C or DAWs or FX units etc. on =

this platform? there just&gt=3B isn't any reason.I agree with Fons that it is largely for =

toys=2C I think that subject came up beforebut hey=2C we are all=

 big kids really.If you are sequencing then=

 the latency is a non-issue=2C well=2C unless you wantflashing L=

EDs in step to the music. As long as the different tracks are in step=

their is not a big problem with lag. FX processing is out of the quest=

ion=2C &nbsp=3Bandmost live work as you cannot play 42ms of late=

ncy.&gt=3B From: ralf.mardorf@alice-dsl.net&g=

t=3B I did some research. Android on an iPad seems to be something that soo=

n&gt=3B or later will be available for everybody.Alien Android. Man=2C this harks back to the days when people were =

claiming&nbsp=3Bthat the i386 emulator on Mac systems was actual=

ly faster than a PC. Dalvicis FOSS and yes=2C it is being ported=

 onto the iPad=2C PlayBook and other systems.There are some issu=

es though. If the app uses the JNI then the backend libraries&nbsp=3B=

are&nbsp=3Bgoing to be ELF but are=

 there not going to be some linking problems at run&nbsp=3Btime from the differences between Dar=

win and Android?Regards=2C nick. 		 =
=
--_3036ee44-a9e1-4200-a989-336b5c16d4e4_--