18 Jan
2009
18 Jan
'09
12:06 p.m.
Luis Garrido schrieb:
So far no one has. If we want to get this going it should be simples as the rest
of ladspa. I think the format I proposed is so simple that one can parse/write
it without pulling additional dependencies into projects (see the attached example).
> i would
like to know if somebody has already thought about a (unified)
> way to save or export the settings of ladspa plugins (or vst,lv2..)
I gave it some thought for a project of mine which sleeps the dream of
the just until I get some motivation to finish it.
I would love to see that too. I would say its
enough to agree on the conventions
(format and place in filesystem) and add them as a comment to the ladspa header.
Ah, but that's a big, hairy, controversial "enough", unfortunately.
Some will swear for RDF turtle, some will kill in the name of a xml
dialect and some will argue the merits of no-nonsense ini files.
Then someone will come up with an abstraction layer to rule them all,
and in the darkness bind them.
That we should avoid.
I guess this will be in a state of flux until a dominant project sways
enough number of users to become widely adopted, probably Ardour, so
brush your shells and learn to dance the turtle.
Luis
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
GStreamer Preset
1.0
GstSimSyn
beep
cut-off=0.65000000000000002
decay=1.5606100000000001
wave=2
volume=0.81999999999999995
filter=2
resonance=5.5600000000000005
default
cut-off=0.80000000000000004
decay=0.25
wave=3
volume=1
filter=1
resonance=0.80000000000000004
sharp
comment:säge
cut-off=0.80000000000000004
decay=0.25
wave=1
volume=1
filter=1
resonance=20.625999999999998
sine
comment:piep
cut-off=0.80000000000000004
decay=0.68083000000000005
wave=0
volume=1
filter=1
resonance=3.859