@prefix dcs: . @prefix doap: . @prefix foaf: . @prefix lv2: . @prefix owl: . @prefix pset: . @prefix rdf: . @prefix rdfs: . @prefix xsd: . a lv2:Specification ; rdfs:seeAlso <../../meta/meta.ttl> ; doap:license ; doap:name "LV2 Presets" ; doap:shortdesc "Presets for LV2 plugins. " ; doap:created "2009-00-00" ; doap:developer ; doap:release [ doap:revision "2.6" ; doap:created "2012-04-17" ; doap:file-release ; dcs:blame ; dcs:changeset [ dcs:item [ rdfs:label "Add pset:preset property for describing the preset currently applied to a plugin instance." ] , [ rdfs:label "Remove pset:appliesTo property, use lv2:appliesTo instead." ] , [ rdfs:label "Merge with unified LV2 package." ] ] ] , [ doap:revision "2.2" ; doap:created "2011-11-21" ; doap:file-release ; dcs:blame ; dcs:changeset [ dcs:item [ rdfs:label "Update packaging." ] , [ rdfs:label "Improve documentation." ] ] ] , [ doap:revision "2.0" ; doap:created "2010-10-04" ; doap:file-release ; dcs:blame ; dcs:changeset [ dcs:item [ rdfs:label "Initial release." ] ] ] ; lv2:documentation """

This vocabulary describes a format for presets (i.e. named sets of control values and possibly other state) for LV2 plugins. 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 the presets like so:

eg:mypreset
    a             pset:Preset ;
    lv2:appliesTo eg:myplugin ;
    rdfs:seeAlso  <mypreset.ttl> .
""" . pset:Preset a rdfs:Class ; rdfs:subClassOf lv2:PluginBase ; rdfs:label "LV2 Preset" ; rdfs:subClassOf [ a owl:Restriction ; owl:onProperty rdfs:label ; owl:someValuesFrom xsd:string ; rdfs:comment "A Preset MUST have at least one string rdfs:label." ] ; lv2:documentation """

A Preset for an LV2 Plugin. 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:

@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.

""" . pset:value a rdf:Property ; rdfs:domain lv2:Port ; rdfs:label "Has value" ; rdfs:comment """ Specifies the value of a Port on some Preset. This property is used in a similar way to e.g. lv2:default. """ . pset:preset a rdf:Property ; rdfs:domain lv2:PluginBase ; rdfs:range pset:Preset ; rdfs:label "Preset" ; lv2: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.

""" . n40'>40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168