Quote:
Originally Posted by fundorin
That's your choice. I think that format should definitely have controller type, index number of the parameter, offset, range, short and long names, so they could be edited manually and universal aliases, by which the surface could address those parameters directly. But, let's see what would be your approach to this.
|
Actually, after having done the previous maps much in the spirit of your suggestion, the goal on this project will be to go in the opposite direction.
I believe the code I posted is already a fairly good guess as to what's in the FX map format:
VST plugin name
WidgetName1 VSTParamName1
WidgetName2 VSTParamName2
WidgetName3 VSTParamName3
...
That's it !
As far as universal aliases, the whole thing is based on GUID's which are, in effect, universal aliases.
Thanks for the input, please keep it coming.
Everyone else, don't be shy, jump in