> point... so... yes. :-)

[snip a load of guff...]

The apps should still work with float as they would on any platform.
LV2 nor LADSPA are going to add much overhead as they do not
manipulate floats.

> All those needless conversions don't settle right with me.

Then don't do them. The apps should process floats. The ARM
softfloat overhead is not that great and the coding required to get
access to the GPUs is suitable that developers will implement them
for optimisations.

> > Yes, but I don't think it has to be that big. The bigger
> > issue is why the hell would you want to do it, integrate
> > LV2 and LADSPA on to this platform?
>
> Why would we? Because they're mature technologies. Why
> reinvent the wheel?

I think Android is trying to avoid wheels altogether, wheels are very old hat.
Android is not Linux and you need to understand the difference between
an app and an application.

> > Don't you think it is more likely that people who are interested will run
> > Linux as a replacement for Android on the ARM tablets rather than have
> > the apps ported over?
>
> Maybe today, with tablets. But not their phones.

So are you suggesting the people who have phones, who don't want to contend
with installing Linux on them, will still want to contend with trying to gets apps to
interoperate with LV2 or LADSPA? Apps don't do much interoperation so you
are looking at one humongous can of worms and all that for very little gain when
there are ready made apps that provide a lot of that combined functionality.

Linux, LV2, LADSPA, plugins, disposable audio interfaces are all for people who
are up for a challenge. The app model was designed for all the hundreds of millions
of handset owners who for the very, very largest part have zero interest in being
confronted with this level of complexity. Why do you want to introduce it? For the
tiny minority who are interested in doing this on handsets/tablets then native Linux
ports are the probable attractive option.

Regards, nick