Quote:
Originally Posted by olilarkin
Is this mode something that you would want to automate? If not then I don’t think it should be a parameter. You can still store it in state. Then your user interface control that changes the mood can trigger the resize
|
It is not automatable but should be 'translateable' between hosts. I thought that would be easier as non automatable parameters (although I might be wrong).
I know with state in reaper that reaper mangles FX state data to add in it's own things. So I can't decode it easily from another app. I wanted to swap FX state between different hosts in another situation and couldn't because of this. In that particular case I wanted to take AU state chunks from FCPX XMLs and put them in an RPP. Justin said that was impossible because of the way reaper mangles the state data before storing/retrieving it.
The idea with my FX is that it can be used in two DAWs and another tool can be used to translate between them.