Steve Harris wrote: Ah, thanks for the .png. That is very helpful. Well, I'm going to try to use it to prove the point that no GUI is needed at all. :) I'll see what I can get it to do. I'm also thinking of using it as a model for a stripped down, simpler version. Probably with a single Osc->Dist->Filt->Delay->Out signal path to start. ^ | LFO I figure that will make debugging some issues easier. Who knows, I might even come up with something useful to others. At the very least it will be a good learning experience. When I first heard about your xml build system for lasdpa plugins I thought it sounded like a crazy idea. Now that I've actually looked at a number of the .xml files and compared them briefly with the generated .so.c I realize I was simply ignorant. It looks like this system significantly lowers the bar for getting into DSP programming. Previously I thought it would be several years more before I knew enough about programming before I would be able to start contributing. With your xml system and LADSPA it appears I might be able to dig in and start off focusing on learning about and comprehending the core DSP algorithms. I can learn all the housekeeping, gui and systems programming stuff more gradually. DSP programming is really what I'm most interested in. The rest of it seemed like a lot of dull drudgery I would have to learn first before I got around to the fun stuff. Using ecasound as my host I avoid a whole layer of GUI issues, too. Of course there is still the midi CC interface, but a GUI host would have to handle that as well and ecasound's implementation allready seems to work fairly well. At least for now, I'm not concerned about note events. In short, I'm pretty excited. :) Thanks Steve, Eric Rz.

Steve Harris wrote: forgot to ask ... did you do that diagram with dia? -Eric Rz.

On Wed, Sep 15, 2004 at 10:06:50AM +0100, Steve Harris wrote: great, thanks. -Eric Rz.