- Edited
Some observations:
I started assuming that effects store an input value that was the knob's input after mapping from 0-1 to the input domain -- I cared because I want to send that value to the UI, as the controls are absolute. I didn't see that being the case after attempting to "wire" a pointer to an internal effect param to fetch its value to send back to the UI. And inverting the stored param value to the original input looked not easy in many cases. I dealt with it by storing the mapped input value in each of a Knob object, and never looking inside the effect. But now OSC and hardware knobs might not play nice together.
What was the other thing? I already mentioned linear vs log. Well, maybe it was that it would be nice to read the layout file and generate code that could be dropped into a C++ project to provide objects to talk to using a small support library that is prepared for the generated code.