efficiency: inadvertent synchronization of 2^n ClockDividers across modules?

[marc_boule (Marc Boulé)]

@gc3

Has anyone already worried about this, on the forum or elsewhere?

I had also thought about this a little while back, and brought it up here, which might be relevant to the discussion:

Watch for param value changes

It’s an elegant one, and I also didn’t know of args.frame, but there could be a problem once many developers use the trick, in that all the extra code guarded by the %64 will occur on the same frame for all modules, which could result in a non-trivial CPU consumption spike. In my own implementation of a process divider for Impromptu, I start the counters with a random value, so as to stagger the occurences of %N == 0, and thus balance out the extra computing load across frames.