25 Jan
2004
25 Jan
'04
8:43 a.m.
On Sun, 25 Jan 2004, Mike Rawes wrote:
Thank you, this is just what i was searching for :))
Is this a way that is portable between hosts?
If it is, i guess i have to have a closer look at lrdf...
Tom
So once more
(I know this has been talked over before on this list):
Wouldn't it be very cool if all LADSPA hosts spoke the same language
with respect to effects presets?
There already is, in the form of liblrdf (http://plugin.org.uk/lrdf).
This provides a way of:
* Arranging plugins into a hierarchy (Simulators/Reverbs, Time/Delays,
Frequency/Filters/Low Pass and so on)
* Defaults and Presets
* Labelling of port values (as in the TAP Reverb Presets port)
Host support of the hierarchy is fairly extensive, but the other featues
aren't AFAIK.
An example of how that Preset port could be expressed:
<ladspa:ReverbPlugin rdf:about="&ladspa;2412">
<dc:title>TAP Reverberator</dc:title>
<ladspa:hasPort>
...
</ladspa:hasPort>
<ladspa:hasPort>
<ladspa:InputControlPort rdf:about="&ladspa;2142.7"
ladspa:hasLabel="Presets">
<ladspa:hasScale>
<ladspa:Scale>
<ladspa:hasPoint>
<ladspa:Point rdf:value="0" ladspa:hasLabel="AfterBurn
(Short)" />
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="1" ladspa:hasLabel="AfterBurn
(Long)" />
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="2" ladspa:hasLabel="Drum
Chamber"
/>
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="3" ladspa:hasLabel="Garage"
/>
</ladspa:hasPoint>
...
</ladspa:Scale>
</ladspa:hasScale>
</ladspa:InputControlPort>
</ladspa:hasPort>
</ladspa:SimulatorPlugin>
A host could read in each of the Point values, and present them in a
drop-down list for example.