Funny,
I was imagining exactly that, for the user to be able to set some deep behaviours of the synth.
I thought about these to be defined in the config file:
- When the settings are different than the physical control, one could choose between pass-through or direct snap to value
- voices allocation; I saw here that there was different way of doing it and that some preferred the og way, other were accustomed to other methodologies, and I think I heard George in some YT video explaining he took a fair amount of time designing the voice allocation strategy, so this could also be choosen via the config file.
- Chorus types / delay types maybe?
- Envelopes ramps types
I still do not have my SG, but am sure using it will bring more ideas :-).
@udo-audio , what do you think about this? would it be feasible? I mean this requires the synth to read an ascii file at boot, and choose according to the set key-values between several algorithms, that, hence, need all to be present in the compiled firmware… Do we have enough room for this in the firmware?