Modulex currently checks whether effects were turned on every 32 sample
periods to amoritize the CPU load of checking the effects.  However,
every instance of Modulex in an entire project (dozens) all did it on the
same sample period, so amoritize the amoritization by fanning them out
evenly so that one or two check themselves every sample period and
avoid a CPU mini-spike.