Watch for param value changes

marc_boule · November 28, 2023, 6:07pm

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.

github.com

MarcBoule/ImpromptuModular/blob/master/src/ImpromptuModular.hpp#L124


      
          };
          
          
          struct RefreshCounter {
          	// Note: because of stagger, and asyncronous dataFromJson, should not assume this processInputs() will return true on first run
          	// of module::process()
          	static const unsigned int displayRefreshStepSkips = 256;
          	static const unsigned int userInputsStepSkipMask = 0xF;// sub interval of displayRefreshStepSkips, since inputs should be more responsive than lights
          	// above value should make it such that inputs are sampled > 1kHz so as to not miss 1ms triggers
          	
          	unsigned int refreshCounter = (random::u32() % displayRefreshStepSkips);// stagger start values to avoid processing peaks when many Geo and Impromptu modules in the patch
          	
          	bool processInputs() {
          		return ((refreshCounter & userInputsStepSkipMask) == 0);
          	}
          	bool processLights() {// this must be called even if module has no lights, since counter is decremented here
          		refreshCounter++;
          		bool process = refreshCounter >= displayRefreshStepSkips;
          		if (process) {
          			refreshCounter = 0;
          		}