AAX Init Behavior
-
I know AAX has issues with not initializing component values properly, but I'm wondering if anyone knows how it handles function calls on init?
I have 2 inline functions that run on init and only one seems to be running. The setup is like this:
reg p1 = 0; inline function f1(p1) { //the stuff in here is not running } inline function f2() { p1 = 1; f1(p1); } f2(); p1ValueLabel.set("text", p1);
The p1ValueLabel reads "1" when the plugin initializes, so f2 must be firing, but f1 is apparently not firing despite being called from within f2.
Any ideas?
-
@ally What does f1 do?
-
@d-healey It hides a panel and un-bypasses a module based on a flag, p1. The panel was not showing but the module was bypassed, which is a mismatch. I ended up figuring out that f1 was firing after all and the issue was solved by explicitly setting the panel's starting visibility in the script before the functions run. All other hosts were showing it (it was visible when I compiled) but PT hid it. Still not totally sure why, and there's definitely some difference in how something is handled, but what I described specifically was a false alarm!