Back To School? Explore DSP & MIDI DIY with Blue Cat's Plug'n Script 3.2!
-
- KVRist
- 302 posts since 28 May, 2011
Seems like it's
- processBlock
- updateInputParametersForBlock
- computeOutputData
At least positionInSamples is the same for processBlock and following updateInputParametersForBlock call.
I don't mind this order, can it be different in different DAWs?
- processBlock
- updateInputParametersForBlock
- computeOutputData
At least positionInSamples is the same for processBlock and following updateInputParametersForBlock call.
I don't mind this order, can it be different in different DAWs?
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- Topic Starter
- 5821 posts since 8 Sep, 2004 from Paris (France)
I think it depends on the DAW and the context. In some particular cases you may be called on updateInputParametersForBlock before AND after processBlock, so it's hard to tell. Why do you need to know the precise sequence? I'd rather not rely on that - just expect that they are called when necessary.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- Topic Starter
- 5821 posts since 8 Sep, 2004 from Paris (France)
What do you mean by "flickering"? Do you want it to be disabled upon load (so that the right value is set?). If that's the case, have a look at the language_extensions folder: there is a template in there that I use to do exactly that: if I remember well, it uses the window.loaded parameter to trigger the animation only when the window is already loaded.