Subject: Re: [linux-audio-dev] GLAME supports LADSPA now.
From: David Benson (daveb_AT_idealab.com)
Date: Tue May 23 2000 - 17:48:47 EEST
> Well, with this proposed scheme you would be unable to provide host
> specific additions to the plugins/structure. With XML we could define
> a standard base and let hosts provide additional information. I think
> the XML approach is more flexible than just another C-API.
>
> Richard.
i think pbd was saying we ought to have both,
and what the hell, we all *will* need a c-api to it.
and i'm not sure we'll all agree on gnome-xml (is that what you meant?).
of course, the best alternate (expat) is a sax-parser so it's
more annoying ...
the api should make the choice equivalent.
(omitting the provite data the api would look something
like this...)
here's roughly the .h file i've been considering.
struct _LadspaControlData {
char* control_name;
unsigned input : 1;
unsigned output : 1;
unsigned control : 1;
unsigned audio : 1;
};
struct _LadspaData {
char* plugin_name;
char* author;
char* copyright;
int num_controls;
LadspaControlData* controls;
};
LadspaDatabase* ladspa_database_new (const char* fname);
LadspaData* ladspa_plugin_data_find (LadspaDatabase* db,
const char* name);
LadspaData* ladspa_plugin_data_find_by_id (LadspaDatabase* db,
unsigned long unique_id);
/* user-defined key => string maps. */
const char* ladspa_plugin_data_get_named_key(LadspaData* data,
const char* key);
/* user-defined key => xmltree maps. */
const xmlNode* ladspa_plugin_data_get_subtree (LadspaData* data,
const char* key);
void ladspa_database_destroy (LadspaDatabase* database);
i can implement this in glib + gnome-xml in like 15minutes,
is this the right api?
- dave
This archive was generated by hypermail 2b28 : Tue May 23 2000 - 18:36:13 EEST