18 Jan
2009
18 Jan
'09
3:52 p.m.
Stefan Kost schrieb:
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).
Stefan's proposal is very much the design i had in my mind when i wrote
the mail. But i would like to point out two important facts:
1.It shouldn't rely on a particular plugin type. Lv2 is coming and it
should be supported as well. No big problem so far..
2.It shouldn't rely on a special library (parser,database..). Free audio
software is often used not only on linux - hydrogen (for example) is
available for linux, windows and mac os x. This makes me think that
plain text files would be a good choice for this task. Just keep it
simple..
But how shoud those files be stored ? As a subfolder in ladspa/lv2
plugin directories? Or in a seperate directory, something like
"~/.plugin-presets/" ?
(Ok, plugin-presets could lead to some confusion...)
What we really need is an agreement between the big linux audio
applications. As a hydrogen developer, i could ask the rest of the team
about this topic. Any comments from the ardour-team or other projects?
- Sebastian
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.