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
Save presets #287
Comments
For LV2 plugins, no problem. It could be done easily... So, if implemented, it would be inconsistent across engines. I mean, only LV2 engines would have this feature implemented ... |
Something is better than nothing 😁. Some non-LV2 could be done |
That's why I'd advocate building on the existing snapshot saving, just peeling off the individual instrument parameters and saving them in a dedicated instrument level folder. They wouldn't blend in with the rest of the presets but they could be named and called up to be re-used in other sets. Or maybe just do that in the non-lv2 plugs and use the same interface but save the lv2 patches in native format. |
Mmmmm! Interesting approach ... perhaps we could have a "preset snapshot" format that we could show merged in the same view with the native presets. Users doesn't need to know about these details. Let me think about it ... ;-) |
Hi jofemodo ! Thanks ! |
Closing this issue and tracking in #614. |
Is your feature request related to a problem? Please describe.
After editing synth parameters I would like to be able to save it as a new preset.
Describe the solution you'd like
Option to save current synth engine parameters as a new preset which will appear in the list of presets. Ability to name preset.
Describe alternatives you've considered
Editing an existing preset then saving as a snapshot may be similar but the preset retains its original name and it is not easily browsable.
Additional context
An example is to edit amsynth to create a cool lead mono synth sound. I want to save this in the preset list as "Killer mono lead". Maybe user presets could / should be stored in their own bank. Ability to edit name in webconf may be sufficient but it would be good to be able to do so in the Zynthian itself.
The text was updated successfully, but these errors were encountered: