Exactly! Take a “simple” pedal like the MXR phase 100.
All it has is a rate knob, but then also 4 (I think?) positions for different amounts of regeneration/depth. How do you make a GUI which would represent 4 knob positions and encode it so it knows what all it needs to adjust “behind the scenes” in the hidden parameters to mimic the real knob behavior ? Then on top of that, it would need to be specific for that given pedal, as that knob is behaving differently than the color switch on something like a Small Stone.
what you’d essentially need to do it create a model of every effect pedal you wanted to include and code all the controls to behave in a one to one manner, which isn’t how the blocks are set up. You’d also need to do this somewhat differently for all the different effect types, and any unique models of effect with less common parameters would also likely need additional coding and parameters.
Then it all seems a little silly because on the hardware realm, people seem to be wanting more controls. Many don’t seem to want a pedal with just one, it’s too limited, it makes like one, maybe two sounds and that is about it. Seems most new pedals are Taking classic circuits adding extra pots for more parameters, letting you change stages in a phaser, add depth and rate etc.
hardware wants to take things more advanced, more control, yet people want software to get more basic, take controls away.....go figure lol