Ingen

A connection between two ports. Graphs have a set of arcs which define how its component blocks and ports are connected.

A signal processing block, which is typically either a plugin instance, or a graph. A block MUST have at least one lv2:prototype property which is a subclass of lv2:Plugin. When there are many such properties, an applications SHOULD use the most specific class it understands.

The end of an undo transaction.

The start of an undo transaction.

A collection of Blocks connected together. A Graph can itself be a Block within a parent Graph, and so on.

An internal 'plugin'

An element of a Graph. A Node always has a valid path and symbol, with the possible exception of the root graph which may not have a symbol depending on context. Ingen uses restricted paths and/or URIs built from valid lv2:symbol components, so the symbol of a Node may be inferred from its URI if no explicit lv2:symbol property is given.

A class which can be instantiated into a Block. A plugin has a set of input and output "ports". In practice this class is semantically equivalent to lv2:Plugin, it only exists to allow the ingen ontology to be useful for "plugins" that aren't semantically LV2 plugins. See the LV2 specification for details about the required properties (rdf:type, doap:name, doap:license, and lv2:port).

A request to undo the previous change.

Transient activity. This property is used in the protocol to communicate activity at ports, such as MIDI events or audio peaks. It should never be stored in persistent data.

An arc contained in this graph.

Signifies a graph contains some block.

Whether or not the port's value or activity should be broadcast to clients.

The X coordinate of an item on a canvas.

The Y coordinate of an item on a canvas.

Signifies the block is or should be running.

The file a Graph was loaded from.

The destination/receiving/sink port of this arc

A special property used to describe any arc incident to a port or block. This is never saved in graph files, but is used in the control protocol to completely disconnect a Block or Port.

Whether or not a bundle is loaded into Ingen.

Lowercase, hyphenated switch for long command line argument.

The maximum fraction of a cycle spent running DSP.

The average fraction of a cycle spent running DSP.

The minimum fraction of a cycle spent running DSP.

Signifies this node should be replicated when it is part of a polyphonic graph. The amount of polyphony (i.e. the number of voices) is determined by the polyphony property of the containing graph. This is a boolean property which defines whether the parent can access each voice individually: All nodes within a graph are either polyphonic or not from their parent's perspective. An Node may itself have "internal" polyphony but not be polyphonic according to this property, if those voices are mixed down.

The amount of polyphony in a Graph. This defines the number of voices present on all :polyphonic children of this graph. Because a Graph is also a Block, a Graph may have both :polyphony and :polyphonic properties. These specify different things: :polyphony specifies the voice count of the Graph's children, and :polyphonic specifies whether the graph is seen as polyphonic to the Graph's parent.

The object which this block is an instance of, or derived from.

Single character switch for short command line argument.

Whether or not the graph has a "sprung" force-directed layout.

The source/sending port of this arc

Whether or not the block's GUI is embedded.

The current value of a port.

Ingen is a modular audio processing environment. This vocabulary describes an Ingen configuration, and is used in both the control protocol and saved files. Conceptually, Ingen represents a tree of objects, each of which has a path (like /main/in or /main/osc/out) and a set of properties.

The context for externally visible Graph properties, that is, properties which apply to the Graph when viewed as a Block within its parent Graph and should be saved in the parent's description.

Template for all Ingen graphs. Saved Ingen graphs always set this as their lv2:prototype. When Ingen is installed, a bundle is installed which included the Ingen LV2 binary and a description of GraphPrototype which links to it. This way, Ingen graphs can be loaded by LV2 hosts without including binaries or symbolic links in saved Ingen bundles.

The Ingen patcher interface.

The context for internally visible Graph properties, that is, properties which are only relevant inside the graph and should be saved in the Graph's description.