pass if change "force" value

[sm_jamieson]

A very useful addition to the pass if changed module, would be a retrigger value, which, when received, would cause the previous non-retrigger value to be resent, as if the "force" input was used. This would allow a single wire to control force and the data values.

There are many times when only a range of values are every used, so such a value is often available.
It would have to be considered how this interacts with the min and max parameter event properties.
Due to the nature of floating point comparisons, it would be best to have a range of retrigger values,
ie. 2 settings, retrigger min, and retrigger max.

The pass if changed multi should have a setting for each multi probably, but if too much, a single value for all would be OK.

[x.iso]

+1

[sm_jamieson]

OK, another one or this module, which I thought the "hold" time was going to do.
What the module actually does is as in the docs, i.e. "Minimum duration between two consecutive triggers".

When the "hold" is on, it would be useful to be able to set the module so that value is maintained
on the wire (i.e. "pass" is on). The setting could be a switch called "pass on hold" or something.

I think that when "pass on hold" is set, this should also cause the module to "pass" for the hold time when "force" is activated.

I would find all this useful is it can stop e.g. a fader from having its value changed for a period of time, which can be useful when a patch is being initialized. This only works for modules that continually monitor their input rather than rely on the "has changed" callback, but many Usine modules do this.

Thanks,
Simon.

[senso]

It's a good suggestion but I think that it's very specific and can be achieved with a small subpatch ? with an has-changed and a pass-flow
the pass if change is often used in most of patches. this could make all your wkp heavier for something that, most of time, we don't use?