Support for LADSPA, LV2, Nyquist, VST and Audio Unit effect plug-ins; Effects written in the Nyquist programming language can be easily modified in a text editor – or you can even write your own plug-in; Experimental modules that extend the functionality of Audacity; Analysis. Spectrogram view mode for visualizing and selecting.
LADSPA is the Linux Audio Developer Simple Plugin API. It enables audio effects to be reused across several host applications such Ardour, Audacity, Sweep, Amarok...CLAM can be also LADSPA host but this page just explains how to build a LADSPA plugin using CLAM.
LV2 is an extensible open standard for audio plugins. LV2 has a simple core interface, which is accompanied by extensions that add more advanced functionality. Many types of plugins can be built with LV2, including audio effects, synthesizers, and control processors for modulation and automation. Extensions support more powerful features, such. Download Ladspa Plugin Pack For Audacity Free Satana (Saturation Analogique) is a LADSPA pluginwhich can be used with any compatible host, such asAudacity,MPlayer, orArdour(¹).It tries hard to simulate an analogue saturation device, like a magnetic taperecorder whose VU meters are stuck in the red, or a tube amplifier's push-pullstage. This plugin generates an output audio stream by scattering short `grains' of sound from an input stream. It is possible to control the length and envelope of these grains, how far away from their source time grains may be scattered and the density (grains/sec) of the texture produced.
Notice: Features explained in this page are not available in CLAM 1.2 or earlier versions.
Using NetworkEditor to generate LADSPA
CLAM NetworkEditor has a new menu command to generate a LADSPA plugin given a network definition. We recommend to use it unless you need to provide the source files, not just the final binary. You might also need to wrap just a processing object instead a network or to join several plugins in a single library.
The techniques explained below are the ones used by the NetworkEditor that you can do by hand.
SConstruct
All the examples here can be built by using the same template of SConstruct file that is presented in Building a processing library section just by changing the line:
by:
Remember also to change the 'libname' on the top of the SConstruct file.
Exporting a processing
If you want to export a given processing (CLAM::AudioAmplifier in the example) as a LADSPA plugin, the following code will do the trick.
This will map:
- CLAM input and output ports in the processing as LADSPA audio ports, and
- CLAM input and output controls in the processing as LADSPA control ports.
The extra parameters are the numeric id, the maker and the copyright.Label is built by prepending 'CLAM_' to the processing class name and the descriptive name is built by prepending 'CLAM '. In this example, 'CLAM_AudioAmplifier' would be the label and 'CLAM AudioAmplifier' would be the text string shown to the user by the plugin host.
Exporting a network
Networks can be compiled as LADSPA plugins doing the following mapping:
- CLAM AudioSources/Sinks in the network as LADSPA audio ports, and
- CLAM ControlSources/Sinks the processing as LADSPA control ports.
Networks require that you specify more metadata than for a single processing: the numeric id, the string label, a name to present the user, the maker and the copyright.
Caution: The network file path specified in the CLAM_EXTERNAL_FILE_DATA macro, is relative to the build working dir not to the source file that contains the macro as it could seem natural. So be carefull if you are not placing the sources in the same folder than the SConstruct file.
Building more than one plugin in a single library
You can pack more than one plugin in a given dll. Not by duplicating the ladspa_descriptor function, which is to be defined only once in a given dll, but by adding more LadspaProcessingExporter's and LadspaNetworkExporter's like in the following example: