saving cycles by de-activating scripts

General TouchDesigner Discussion
1

hey,

Does it make any cpu cycles sense if I have a chop exporting to a text DAT’s execute
field to activate it only at certain times?

(keep in mind I would have hundreds of this when’s all said and done, so I’m asking if it would make a difference when the concept is applied to hundreds or thousands of text dats).

for example, I have a script that looks at a chop for changes. This script should only be active when the mouse is inside a given component. So I can use a panel chop (which I have to use anyway), to export to the script’s execute field ( when “inside” is 0 the script is off, otherwise the inside*2 is activating the on CHOP change mode)

Does this technique make a difference in terms of how much processing needs to take place, OR is there for example an overhead everytime a dat execute parameters is changed from off to something else (in which case it may make it worse!).

please let me know,
thanks,
dani

2

I dont think you’re saving as much by swapping the execute on CHOP to off as you would
by exporting to the ‘On ValueChange’ which effectively disables it as well, but leaves everything else in place.
There’s lots of setup in the execute DATs when setting up something new to monitor.
Cheers
Rob.