-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recreating LV2 presets deletes sym-linked files #37
Comments
Previously the GUI explicitly called remove_preset() before saving a plugin-preset. This functionality is now moved into the backend. This fixes a case when a user tries to save/replace factory presets and works around lv2/lilv#37
Also may be related: lsp-plugins/lsp-plugins#120 |
Previously the GUI explicitly called remove_preset() before saving a plugin-preset. This functionality is now moved into the backend. This fixes a case when a user tries to save/replace factory presets and works around lv2/lilv#37
I don't think the linked commit (which only removes fewer files) is the root of this, or that it's related to the above LSP issue. Deleting state then saving it again like this can not work, because plugins can save files when their state is saved (which happens at It may also be true that linked things get weird, but it doesn't matter. I'm not yet sure what the correct way to do this is yet, though. |
Closing this as a PEBKAC, since, as explained above, there is no way lilv could possibly make what Ardour was doing work. It only happened to work before, sometimes, if plugins didn't save files. Please open any follow-up state bugs clearly, for example: From a clean state, I do this and this, and get this:
and I expect this:
|
In Ardour, saving a preset first deletes the current presets, and then re-creates it.
This worked fine before c9a54e0, however recent liblilv unlinks all the external resource in
lilv_state_delete()
, and for some reason they are not re-created.Since creating presets works correctly, it looks as if the files are still assumed to be mapped and hence the symlinks not re-created.
Related to lsp-plugins/lsp-plugins#119 (comment)
The text was updated successfully, but these errors were encountered: