Welcome to the development pages of the Python Ladspa host project. This is a new (aka pre-alpha) project written by a starving college student in his not-so-spare time. I'm striving for the "publish early, publish often" heuristic, which is a fancy way of saying these web-pages and the source code are quite rough drafts.
The sourceforge project page is here.
The best documentation for the API is found in the python doc-strings. Browse the API.
Documentation! Also, the web-site needs more context; what is ladspa? python? why this project? etc...
The structural elements of the code are complete. It is possible to browse ladspa plugin information from python. Actually processing audio through a plugin in python has yet to be tested.
I'm not certain how to handle audio buffers in python in a way that works with ladspa, yet offers the most efficient and flexible interface in python. And of course, nothing should crash. Here's an unfinished page on the subject. The main gist of it is that I need to research what other python-audio projects are doing.
Currently, the low-level _ladspa module is implemented in several C source files: one for the module, and one for each type, as well as some header files which declare pointers to "global" stuff. I'd like to maintain separate source-files, yet prevent all symbols except one used by python (the "init_ladspa" module initializer function) from being exposed to outside code.
I'm not sure if this is possible in C, which sucks. If it's not, I'll either prefix all exposed symbols with a unique name, or clump everything into one massively ugly C file.
I'll bet other python hackers have experience with this problem. I'll seek out a large built-in module's source to see how they handle it.