Thinking about it, it probably would be a good idea if the vamp host was developed separately from the PluginHost. Particularly for the purposes of GSoC, I think projects should stay a manageable size.
The important thing is that the two project teams (VampPlugins, PluginHost) communicate with each other so that we retain the possibility to merge the vamp host code into the generalised plugin host at some later stage if it seems appropriate.
Jamie
On Sun, 2008-03-16 at 12:59 -0400, Hans-Christoph Steiner wrote:
It sounds like a very worthwhile project. It doesn't sound too small to me. If you really are able to get everything working that quickly, then you could spend the extra time polishing everything so that it works really easily, then also making sure that there are docs for it.
.hc
On Mar 16, 2008, at 8:29 AM, Georg Holzmann wrote:
Hallo!
I just have come over the vamp plugins (http://www.vamp- plugins.org) again. It is a plugin system for feature extraction, audio analysis and is used by the Sonic Visualizer, Ardour, Audacity and others ... There already exist many plugins (see http://www.vamp-plugins.org/download.html and the features listed there) and it would be definitely nice to have them in pd.
However, it's also not so straight forward to implement a host, because some plugins need data in frequency domain or in a specific blocksize ...
I made a GSoC page where I described it in more details (http://puredata.info/dev/summer-of-code/VampPlugins) and would be definitely interested in implementing this for GSoC. Anyhow, I don't know if this project might be too small ... maybe it can be also combined with something else ?
LG Georg
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Access to computers should be unlimited and total. - the hacker ethic
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev