if I hook up the "xOff, yOff and factor" to outputs of "iterator
Variables" (or its descendants) the image kernel runs faster than
the "Image Texturing Matrix". If I use some passed in values (from
parent) as input variables, performance drops down to the level of
crap -er- crop :)
I would like to understand why that is so and how I can remedy that.
In your picture, the first "Core Image Kernel: Default Kernel" has
constant inputs for all iterations, so its result gets cached by
Quartz Composer, while this is not the case in the other kernel
(depends on Math <- Iterator Variables), therefor the difference in
performance.
