alt Hacker NewsI am a little confused. I think you the mean reverse of the usual mapping: (a) from the surface to the plugin GUI (b) the plugin GUI is drawn to look like the surface. Right?
Interesting idea, but creates a bit of a coding conflict: the plugin developer writes the plugin GUI (typically feeling they've lavished a lot of love on it); they're not in control of the layout of a control surface (and indeed, may have no way to know what it is). So a job that would really be the job of the control surface manufacturer can't be done because that's the domain of the plugin developer.
It's fairly easy to imagine a single control surface offering this for a tiny subset of all possible plugins, but getting beyond that seems pretty much impossible to me. There was a protocol that Digidesign/AVID bought back in the mid-oughts which did maybe 60-70% of this, in the sense that it provided negotiation between the plugin and the host/surface. Problem was, it was so complex that almost no 3rd party plugin developer or control surface developer was willing to get involved.
Yeah I'm not explaining myself very well. I don't have a lot of knowledge around the inner workings of how the GUI aspect is specified on a VST but it seems to be incredibly diverse which is why while I'd love to see something like this - I just don't think it's really feasible.
It's all for the love of physical dials - that tactile ability to play with a synth is such an underrated thing.
I've got tons of VST recreations of older synths like the Minimoog Model D, Prophet 5, etc. but it's just not the same fiddling with controls using a mouse...