RE: [linux-audio-dev] LADSPA Update, New Project (CMT) & Help Requested

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: RE: [linux-audio-dev] LADSPA Update, New Project (CMT) & Help Requested
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Fri May 05 2000 - 03:45:28 EEST


I think ladspa.h is more-or-less alright as a reference document but rather
complicated as a tutorial/introduction - we need documentation that
actually gives a developer a concrete sense of what is going on.

Ooo. Good point about memory management and descriptors - the assumption
I've been working with is that the plugin library will handle all the
required memory access (i.e. the structures will probably be allocated once
globally). The plugin examples do this, however this behaviour isn't in the
API explicitly, merely being implied by the fact that ladspa_descriptor()
returns a const * pointer - I probably should add some comments to the
SDK. Hopefully your concerns about counting are reduced by this. [Hmm. Do I
need to worry about this?]

I'll check out dlsym() more carefully.

-- Richard

-----Original Message-----
From: Juhana Sadeharju [SMTP:kouhia_AT_nic.funet.fi]
Sent: Friday, May 05, 2000 1:05 AM
To: linux-audio-dev_AT_ginette.musique.umontreal.ca
Subject: Re: [linux-audio-dev] LADSPA Update, New Project (CMT) & Help
Requested

>From: "Richard W.E. Furse" <richard_AT_muse.demon.co.uk>
>
>((3) LADSPA needs better user and development documentation.)

Yes. The comments in the plug-in are not enough for developers.
I will check if I learn anything worth of documenting while writing
LADSPA support to my software.

 -*-

I noticed that both analyseplugin.c and applyplugin.c doesn't free the
descriptor structures. It could be a good to make a proper cleaning in
these examples.

If I just want to know how many labels the plug-in has, do I really
need to get every descriptor (plenty of mallocs and frees)?

It would be nice to have a function which tells how many there are,
or have the ladspa_descriptor(unsigned long Index) return the number
of labels when Index == -1.

 -*-

A minor thing: dlsym() on error seems to need more code than written
in example hosts. See dlsym() manual page. My code is following:

  func = dlsym(dlhandle,"ladspa_descriptor");
  if (func == NULL) {
    /* check if we really got an error */
    error = dlerror(); /* save because next call to dlerror() returns NULL
*/
    if (error != NULL) {
      /* my error code deleted */
    }
    /* else the NULL is a valid function address */
  }

Juhana


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Fri May 05 2000 - 04:24:04 EEST