After a very intense development months since the last 1.0 release, the CLAM crew is glad to announce that CLAM 1.1 is ready to download. It comes with many new features and code clean up. Most important improvements are found in the Visual Prototyping front: new 3D-looking widgets, new data viewers and control surface; and a simplified way to bind controls between the user interface and the processing network.
This release has been cooked-up under the umbrella of the Interactive Technology Group at the UPF lead by Josep Blat. So we thank their support! It also features the work from contributors such as Zach Welch; as well as the first patches from Google Summer of Code program —for example LADSPA and FAUST support and some work on Annotator widgets.
A summarized list of changes follows. See also the CHANGES files for details. New audio related widgets were added to be used on the NetworkEditor and the Prototyper. Such widgets include data views such as the BarGraph which can display LPC’s, MFCC’s. Nice control widgets were also added. The ControlSurface, for instance, to control two scalar parameters by moving a point. Some widgets were gathered from the LAC community, such as PkSampler PovRay generated widgets, and nice knobs we enhanced from QSynth and Rosegarden. Thanks to the developers of those projects for making them GPL and being so supportive while integrating them in CLAM. With all those widgets, users now can visually build more appealing applications such as the new examples we include with Prototyper: A real-time gender change, or real-time spectral effects.
The TonalAnalysis (Chord extraction) now takes advantage of fftw3 performing 4 times faster! The KeySpace visualization was also optimized so now tonal analysis runs even on very slow computers.
NetworkEditor and Prototyper usability have been enhanced. They exploit the new in-control bounds parameters to automatically set up bounded control senders widgets. Also, NetworkEditor have proper multi-processing selection features.
On different fronts, the code-base has been reduced by getting rid of Fltk and Qt3 modules since we are now focusing on Qt4, and the documentation have been restructured and now it offers new programming how-tos.