Currently we use a selector that retains which preset we chose. But that implies "current selection" retains valid, which is not true.
The presets API in AudioPluginInstanceAPI for most plugin formats implies that it is only to load a preset whose content can be edited just as usual, without making the original preset data dirty.
The API is good, but by showing the mere selector it kind of perceives that current selection of preset means something, especially that it can be transferred to MIDI-CI clients for current preset selection.
This should be changed.
Currently we use a selector that retains which preset we chose. But that implies "current selection" retains valid, which is not true.
The presets API in
AudioPluginInstanceAPIfor most plugin formats implies that it is only to load a preset whose content can be edited just as usual, without making the original preset data dirty.The API is good, but by showing the mere selector it kind of perceives that current selection of preset means something, especially that it can be transferred to MIDI-CI clients for current preset selection.
This should be changed.