Where should I put Synth.deferCallbacks(true)?

[A Former User]

@d-healey Actually I don't know what you mean with MIDI processors, but In my Project's "Scripts > ScriptProcessors" folder there are 2 scripts, Interface and a Delay Compensation script processor. (I am making an fx plugin by the way)

Other scripts are .js files that I am attaching seperately and they are one up directory (in "Scripts" folder)

[d.healey]

@Steve-Mohican

Yeah I should have said script processor, but they generally are MIDI processors.

[ulrik]

@d-healey so if I have a lot of GUI stuff happening, paint routines and animated knobs etc, is it the best way to put them in a new script processor that has

Synth.deferCallbacks(true);

?

[ulrik]

@d-healey I'll show you what I mean.
This is an LFO and I want to draw the curve while playing and having the LFO active, so it will be possible to find the right curve for the occasion.

I also want the "fadein", "fadeout" & "Intensity" parameters to be reflected visually

[d.healey]

@ulrik There is no point putting GUI stuff in any script other than the main Interface since this is the only one a user will ever see. So that's the place where you would most likely use defer callbacks.

[ulrik]

@d-healey Ok, I understand, but the curve calculations then, should I have them placed in another script processor and defer the main Interface? Will there be any benefits doing that?

[d.healey]

@ulrik deferCallback is only useful when you are doing things in the realtime callbacks. So if your curve calculation is happening in on note on for example then it might be beneficial to use deferCallbacks if you don't need the calculation to be done on the audio thread.

[ulrik]

@d-healey Thanks! :)

[ustk]

@d-healey aren't all interface scripts already deferred by default anyway?

[d.healey]

@ustk Nope

[ustk]

@d-healey I'm keeping to ask this redundantly... I need to tape that in once for all! :)