CHOP execute cooking on every change

Hi,

I’m using a chop execute that is set to “Off to On” and “On to Off”.
I use it to optimize performance and to turn off cooking of a Bloom Base.


I notice that this DAT is cooking on every change of constant4.
I understand that a change of constant4 is making the DAT dirty, though I’d expect it only to cook when going from 0 to +0 or from +0 to 0 since nothing is really asking for it’s data?
It also seems like it takes quite some cooktime.

Cheers

Additional question:

Is it a good idea to connect the parameter of a base together with the cooking flag?
For example, I have my midi controller control constant1 (0 to 1).
I reference this constant1 to a base that has effects inside and with a custom parameter that goes from unvisible(0) to very intense(1).
I also reference this constant1 to a chop execute that turns off cooking when the custom parameter is 0 (unvisible).

Thanks!