[Clam-devel] Re: ladspa progress
flipy.bcn at gmail.com
Mon Mar 19 03:22:37 PDT 2007
I've forgot to add a regular CHANGELOG:
+ finished (quick and dirty) LadspaFactoryTest
+ created NetworkEditor/src/LadspaFactory.hxx
+ added ladspaFactory to ProcessingTree
- created factory
- add creators for all plugins
- set factoryID in drag object
+ made LadspaFactory a singleton
+ moved DummyLadspa to LadspaWrapper
+ created LadspaWrapperCreator
+ use CLAM::Processing
+ use hidden column 1 in ProcessingTree to store the className (or factorID)
On 3/19/07, Andreas Calvo <flipy.bcn at gmail.com> wrote:
> The last few days I've running some tests under the ladspa support for
> CLAM, based on a UnitTest (LadspaFactoryTest) that Pau gave me.
> That leaded to some big changes in the structure.
> The main problem was that the current factory was not compatible with what
> we need to wrap a ladspa plugin, so first step was to make a LadspaFactory
> (and later we'll merge it with the current factory somehow).
> On the other hand, as opposed as the current processing, Ladspa needed a
> little bit more information. So there's a new class called
> LadspaPluginExplorer which generates a structure that holds all the
> information needed and give it to the ProcessingTree to generate the
> LadspaTree (in fact, it's a use-and-trash object).
> Next we created two new classes, LadspaWrapper and LadspaWrapperCreator...
> Sure the name explains by itself, but first one it's a wrap of a ladspa
> plugin, and the second one it's called in the LadspaFactory to store objects
> with their key.
> I'll add the patches, but I think they may be very unstable.
> First add the ladspa patch, and then add the processing_tree patch.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clam-devel