In the performance monitor I have a whole bunch of nodes across my project being cooked without being pulled. It’s costing me a lot of fps and I cant work out why. Above each it says ‘Cook operator to update parameter dependencies’. Anyone know what this means and how to prevent it? Been having this issue for a while.
(My project is split into scenes. I have two scenes selected, but the nodes cooked are also in other scenes. I have midi inputs which control everything)
Thanks 
Hi @rpsomerville,
hard to say just from the message what might be causing it to cook. A nice overview of what causes cooks is listed in the article on our documentation here:
But if you could provide an example, that might be helpful.
cheers
Markus
Heres a few examples, for context all the A1,2,3…B1,2,3… etc are all containers, each a different visual to select. Only two are selected at a time, so the rest should not be cooking.
This one says ‘propagating changes to other nodes’, coming from a pattern CHOP in container A3 and causing cooking across a whole bunch of other containers that I don’t need to cook.
Here it says ‘Cook operator to update parameter dependencies’, coming from another pattern chop in another container. As you can see there’s a whole bunch of these in the performance monitor from a load of different containers:
I also get it from movie file in TOPS across the board and unsure why as i am not asking these to be shown:
Could it be to do with the input midi? Changes in the input midi forcing changes further downstream? as they are all connected to this midi input.
Thanks for your help!
Hi @rpsomerville,
it could be the Midi or I see you are also using an Audio Analasys in there. If you can trace it back to these sources, we could maybe suggest some approaches that prevent cooking.
cheers
Markus
