I have encountered this inexplicable behavior for the second time in a project. This time, the issue arises with a TopToChop node, but I previously experienced the exact same issue with the Blocktracker TOP.
There are two TopToChop nodes in my project, located in different places. Both need to convert a TOP with a resolution of 360x1 pixels, using a 16-bit float RG format. The download type is set to ‘Next Frame (fast).’
When both nodes are cooking, one has a cook time of approximately 9ms, while the other has a cook time of around 0.08ms. However, when I disable the node with the 9ms cook time, the issue shifts to the other node.
How should I interpret this, and how can I solve it?
When i disable them both my total cooktime drops to ~8ms instead of ~25ms so you would think it is not a gpu overload?
See attached screenshots.