*Saving* plugin presets programmatically - Lua, MIDI, OSC?

[sciurius]

The are added to the file-selector’s recent list just fine. That is a feature of the gtk file-dialog, unrelated to the plugin-state. I just checked it works here.

They are added with the file’s date, which means that they appear at the very bottom of the list and hence immedeately get lost if some other file dialog takes place. Shouldn’t they be added with the date the file was used instead?

You could create presets of that plugin. Those do include the soundfont.

Interesting… However the presets seem to be saved in the project and they cannot be used in other projects.

[x42 (Robin Gareus)]

However the presets seem to be saved in the project and they cannot be used in other projects.

Check again, plugin presets are shared between all sessions and can be used in other projects. LV2 presets even in other applications.

PS. Do you have a writable LV2 preset folder? on GNU/Linux usually $HOME/.lv2/

[sciurius]

That’s what I would expect.

I have a writable .lv2 folder, and it contains subfolders like a-Fluid_Synth_Airfont340GS.lv2 with appropriate content. But when I start a (new) ardour session, and add the a-Fluid_Synth to a track, it doesn’t have any presets.

Update: It turns out that $HOME/.lv2 needs to be added to the LV2_PATH.