Hi, I would like to use Constant CHOP for some sort of “on-demand data storage” (utilizing its snap parameter to capture current input data). This works nicely, however it keeps cooking at all times as its input is also cooking. I would like to eliminate unnecessary downstream cooking, but adding Selective Null CHOP seems like an overkill in this case.
I would like to ask if it wouldn’t be reasonable to stop cooking Constant CHOP when it isn’t really doing anything? I totally understand it must cook on pulse of snap parameter, but I guess it doesn’t have to cook only because its input is cooking, right?
If I am missing something and this isn’t a good idea, please what would be your go-to solution for such “on-demand data storage”? I have been also thinking about Record CHOP, but it doesn’t have pulse parameter that I could just click to save input channels… Thanks!
constant.1.toe (3.5 KB)