On 02/26/2011 06:45 PM, Stefano D'Angelo wrote:
Something like
100k-200K could be fine in my case, at the condition that adding
LV2 support provides a real benefit in terms of functionality.
This depends on what you are using it for and how. Being decentralized
& extensible, you could also use it to make coffee. :-)
Heh :) Well, right now, I'm more wondering about what ui:AndroidUi could be.
Aside, in the ui ext docs there's this example which contains ui:binary, but I
can't find any reference documentation about this binary property on the page:
http://lv2plug.in/ns/extensions/ui/
I don't
want to wake up old trolls, but last fall, when I had a sound engineer
intern working on the topic, we ended up thinking that integrating LADSPA would
really be straightforward. No such overhead, great portability, and plenty of
plugins.
So most logically, when time comes to add plugin
support, I will start with
LADSPA. LV2 will maybe come afterwards. But this could change if there suddenly
is a enthusiastic mood about LV2 on Android, and that LV2 plugin packages arrive
on the Android Market.
I respect your choice and understand the rationale. Also, all of this
changes won't happen by tomorrow (my guess is 2/3 months, based on
feeling more than facts), so if you "need effects soon", you should
probably go that route.
Effects are not the top priority. I've done quite a lot of research on it
because it was a good topic for my intern to work on. I have other basic
features to add first. And the schedule that you mention makes sense to me.
However, in the long run, I would avoid LADSPA for two
reasons: 1.
lack of extensibility, etc., 2. LADSPA plugins can run into LV2 hosts
without explicit support through the NASPRO bridges (which will be
able to work by default with SLV2 starting from the next SLV2 release,
otherwise you can grab the current svn SLV2 already).
Hmm, I've been wandering in google yesterday about such LV2-LADSPA bridge.
I am discovering the NASPRO project. That's interesting. It seems like it may
consume a lot of brain-time diving into all this when compared to LADSPA. But
I'm nevertheless a bit worried about adding support for LADSPA, as it's getting
old and somehow obsolete. But IIUC correctly you are about to add some sort of
LADSPA backward compatibility, which in any case, sounds very good and was
clearly missing.
So it turns out it depends on how long you want to
wait, or rather if
you would consider giving some help, and what you want to do with LV2.
What kind of help would you need?
Also, are you/is there anyone on the list who is interested in releasing audio
plugins for Android? Feel free to write me personally if needed.
--
Olivier