Nasty timing bug I think.....
-
OK so for a couple of my plug-ins they are not setting back-end modulators to their correct values - on LOAD.....not on compile, or preset changing thats all fine...
So what seems to be happening is the plug or HISE are still loading and setting up the modulators whilst the init call back is executing, and thus when init finishes - one of the control call backs - that sets a modulator value (like say intensity) isnt getting acknowledged and executed correctly....
..any one else seen this?
I have an (ugly) work around that calls a timer in the init, which executes just once and sets the modulator value correctly.. this works fine - with say a time of 500 ms..
So I'm asking that HISE NOT call the init processing until all the back-end elements are correctly in place.
Actually spoke too soon - the work around works in HISE but not in the compiled plug-in....
-
But the onInit callback (and actually every script compilation is already deferred until the module tree has been loaded (otherwise you could not get references to any module at all). There must be something else wrong here.
Also don‘t do stuff like this with a deferred timer - if the host does not open the plugin interface it will not be executed.
-
@Christoph-Hart said in Nasty timing bug I think.....:
Also don‘t do stuff like this with a deferred timer - if the host does not open the plugin interface it will not be executed.
Christoph, Do you mean Deffercallbacks can affect The macro modulators?
-
No, that's unrelated.
-
@Christoph-Hart dont want to Hijack the thread
But is this normal That Macro modulators Makes the Ui A Little laggy?
In a All Svg Project?
-
@Christoph-Hart - OK so I have no idea what is going on then.
I load the project in HISE - and (without this "hack") the modulator does not get set by its (preset enabled) slider.... I "touch" the slider and it is set correctly, I load a preset and the modulator is set correctly...
What do you suggest I do now?
-
@Lindon said in Nasty timing bug I think.....:
What do you suggest I do now?
Can you recreate the issue in a minimal snippet?
-
@d-healey no.
-
@Lindon -- hmm., very odd the modulator I am using is a Sample Start Constant
its named the default "Constant1", but it might be fixed by naming it something else...seems ot fix it in HISE - checking in the compiled version...
-
@Lindon - damn it nope....its fixed in hiSE but failing in the compiled plugin....grrrr......
-
@Lindon -- fixed it I think. renaming the constant seems to help...very very odd.
-
@Lindon That is (unfortunately) not the first time names are causing issues. The parser might take them as code or something...
In the same fashion, never use the word "system" in any name. Or at least not in project names or you'll have some surprises too...
-
@ustk - noted thanks.
