Updating patches #490
Description
Patches are stored internally as sequences of events that, when executed, configure a voice (or set of voices in a synth). You define a user patch e.g. as a sequence of Amy events each including a patch number. You can then use that patch to initialize a voice, but any changes you make to that voice subsequently do not update the patch.
If you add events to modify a synth, I think you could add the same events to the user-defined patch to keep it in sync. But then the patch would contain a history of all the changes made to the voice. With something like varying the filter frequency with a knob, this would be wasteful, since it’s only the last out of a long series of values that matters.
From experience with other synthesizers, one might expect a “set synth to patch .. modify synth .. update patch with modifications” pattern, which is intuitive, but unfortunately not how AMY works at the moment.
This is related to #488. It would be nice if the patch store mechanism were smart enough to replace subsuming events rather than keeping all of them. We don’t do that now and I’m not sure how hard it would be. It might be tricky to tell which commands are being superseded