LV2 subproject with meson
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
David Robillard 882b9446cb Format all code with clang-format 2 years ago
..
README.txt Order book chapters in build script rather than by bundle name. 8 years ago
amp.c Format all code with clang-format 2 years ago
amp.ttl Fix translations 6 years ago
manifest.ttl.in Improve documentation 6 years ago
waf Order book chapters in build script rather than by bundle name. 8 years ago
wscript Simplify plugin building and set up source tree run environment 3 years ago

README.txt

== Simple Amplifier ==

This plugin is a simple example of a basic LV2 plugin with no additional features.
It has audio ports which contain an array of `float`,
and a control port which contains a single `float`.

LV2 plugins are defined in two parts: code and data.
The code is written in C, or any C compatible language such as C++.
Static data is described separately in the human and machine friendly http://www.w3.org/TeamSubmission/turtle/[Turtle] syntax.

Generally, the goal is to keep code minimal,
and describe as much as possible in the static data.
There are several advantages to this approach:

* Hosts can discover and inspect plugins without loading or executing any plugin code.
* Plugin data can be used from a wide range of generic tools like scripting languages and command line utilities.
* The standard data model allows the use of existing vocabularies to describe plugins and related information.
* The language is extensible, so authors may describe any data without requiring changes to the LV2 specification.
* Labels and documentation are translatable, and available to hosts for display in user interfaces.