Element groups for saving in presets

[gorangrooves]

Currently, when we save a preset, it saves all elements that have "save in preset" enabled. It would be wonderful to have more flexibility with what elements get saved with every preset.

I propose to have a "preset group" in addition to "save in preset." So, for example, you can assign group 1 for your sliders, group 2 for mute buttons, group 3 for comboboxes, etc. We should be able to easily name those preset groups, like: Main sliders, drum mapping, outputs etc.

When a user goes to save a preset, they have the available groups visible with checkmarks next to them.
So, they can choose to save some elements but not others with every preset they save.
This way, they can recall important presets and easily combine them.

For example, maybe they change the drum mapping and just want to save that. Or they create a new mix and would like to save only the slider values.

So, the idea is not for us to go through some complicated hackery to provide similar functionality with our factory presets but to allow the end user to save easily any portion of their setup.

What do you guys think?

[Christoph Hart]

I don't think it's a good idea. A preset is a single state that needs to be recalled on various occasions and adding another abstraction layer on top of that will lead to issues and regression problems pretty soon and the possible use cases are way too broad to be covered with a "hardcoded solution".

You can achieve this kind of customized loading / saving with the pre / post user preset callback where you could remove eg. all mixer gain values if the user chooses to do so.