presets
type: Project
license: isc
name: LV2 Presets
shortdesc: Presets for LV2 plugins.
created: 2009-00-00
developer: me
release:
  revision: 2.8
  created: 2012-10-14
  file-release: lv2-1.2.0.tar.bz2
  blame: me
  changeset:
    item: Use consistent label style.
    item: Add preset banks.
release:
  revision: 2.6
  created: 2012-04-17
  file-release: lv2-1.0.0.tar.bz2
  blame: me
  changeset:
    item: Add pset:preset property for describing the preset currently applied to a plugin instance.
    item: Remove pset:appliesTo property, use lv2:appliesTo instead.
    item: Merge with unified LV2 package.
release:
  revision: 2.2
  created: 2011-11-21
  file-release: lv2-presets-2.2.tar.bz2
  blame: me
  changeset:
    item: Update packaging.
    item: Improve documentation.
release:
  revision: 2.0
  created: 2010-10-04
  file-release: lv2-presets-2.0.tar.gz
  blame: me
  changeset:
    item: Initial release.
documentation: This is a vocabulary for LV2 plugin presets, that is, named sets of control values and possibly other state. The structure of a pset:Preset is deliberately identical to that of an lv2:Plugin, and can be thought of as a plugin template or overlay. Presets may be defined in any bundle, including the plugin's bundle, separate third party preset bundles, or user preset bundles saved by hosts. Since preset data tends to be large, it is recommended that plugins describe presets in a separate file(s) to avoid slowing down hosts. The `manifest.ttl` of a bundle containing presets should list them like so: :::turtle eg:mypreset a pset:Preset ; lv2:appliesTo eg:myplugin ; rdfs:seeAlso <mypreset.ttl> .

Preset
documentation: The structure of a Preset deliberately mirrors that of a plugin, so existing predicates can be used to describe any data associated with the preset. For example: :::turtle @prefix eg: <http://example.org/> . eg:mypreset a pset:Preset ; rdfs:label "One louder" ; lv2:appliesTo eg:myplugin ; lv2:port [ lv2:symbol "volume1" ; pset:value 11.0 ] , [ lv2:symbol "volume2" ; pset:value 11.0 ] . A Preset SHOULD have at least one lv2:appliesTo property. Each Port on a Preset MUST have at least a lv2:symbol property and a pset:value property. Hosts SHOULD save user presets to a bundle in the user-local LV2 directory (for example `~/.lv2`) with a name like `<Plugin_Name>_<Preset_Name>.preset.lv2` (for example `LV2_Amp_At_Eleven.preset.lv2`), where names are transformed to be valid LV2 symbols for maximum compatibility.

value
documentation: This property is used in a similar way to lv2:default.

preset
documentation: Specifies the preset currently applied to a plugin instance. This property may be useful for saving state, or notifying a plugin instance at run-time about a preset change.