Subject: Re: [linux-audio-dev] LADSPA Hosting
From: ian (deviant_AT_custard.org)
Date: Wed Apr 16 2003 - 23:03:00 EEST
the simplest way to determine if an algorithm is likely to be an effect or
not is just to count the number of audio input and audio output ports.
e.g. if you just want to do single channel effects, you might want to
limit your app to using plugins with one audio input and one audio output.
you can find out this info from the ladspa descriptor by stepping through
all the plugin ports and counting the required types. the plugin sdk has
example code for all of this, and can be found at www.ladspa.org.
there's not much else you can do to find out how a plugin works inside.
personally i don't think it's necessary to limit things any more than that
- you might be stopping the user from doing something cool! and if it
doesn't sound good the user can just move on to the next plugin.
ian
On Wed, 16 Apr 2003, Nick Tsocanos wrote:
> I got my app to host plugins, but I am having problems figuring out how
> to filter plugins out that won't work in my app. I only need F/X
> processors. If a plugin does not process an audio stream, or is used
> only for synthesis, or has peculiar controls that are not defined in the
> hints, than I want to ignore them.
>
> Is it possible? How can I find out how a plugin is used? I am reading
> the API header but it's not entirely clear what properties determine how
> a plugin is used or how I can tell if a plugin won't work for my app.
>
> Thanks
>
>
>
This archive was generated by hypermail 2b28 : Wed Apr 16 2003 - 23:10:50 EEST