Quote:
Originally Posted by JD Young
Hi Tunca,
I've had this issue as well. I have not really looked into it, but I've noticed that if you initialze a parameter with an int or enum this weird behaviour can occur with the ISwitchControl in ProTools; depending on the exact number of switches/frames in the control/bitmap. If you initialize your parameter as a regular double though, the issue is gone. Altough I'd like to get to the bottom of this rather sonner than later, this quick fix should do the trick.
|
I have an 11-step knob control, using an enum parameter (with my fork), works fine.
But that problem with AAX params sounds familiar with wdl/ol master—that only double params worked right. I fixed it in my fork. Which are you using?
I'm using double, int, and enum parameters in my plugin, and they work correctly with Pro Tools automation.