10 Mar
2010
10 Mar
'10
7:34 a.m.
On Tue, Mar 09, 2010 at 11:31:38PM -0500, frank pirrone wrote:
On 03/09/2010 11:12 PM, Ken Restivo wrote:
Ladspa plugins don't have any code to save presets, the host
has to do this. For Ardour, look at
$HOME/.ladspa/rdf/ardour-presets.n3
Ciao,
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
On Tue, Mar 09, 2010 at 08:41:09PM +0000, Gordon
JC Pearce wrote:
/usr/share/ladspa/rdf On Tue, 2010-03-09 at 12:22 -0800, Ken Restivo
wrote:
Wait... what?
Meaning, every LADSPA plugin can save its presets in a totally different place?
That's insane.
How do I transfer the presets between different machines? How can I put them into a
version-control system?
Auugh.
-ken
I'm trying to Git-ify everything in my music
setup. So far so good, except I can't figure out where LADSPA presets get saved.
After poking around through the Ardour sourcecode, it looks like the presets don't
get saved by Ardour itself; it calls a function in the plugin itself (IIRC,
plugin->save_preset() or something like that). Where the plugin actually saves its
state is a mystery to me.
Any hints?
AFAICT it's implementation-dependent.