I am not sure but I thought the Switch TOP only allows cooking for the two selected inputs. Perhaps the CHOP and etc stuff routed into your non selected bases still cooks idk!
It runs a .tox file in a self-contained instance of TouchEngine. More info on that here: th-cam.com/video/Fau61Cz80iY/w-d-xo.html Now that I'm running my patches in Engine COMPs, they spin up much more smoothly, but they seem to run less efficiently overall, so I'm a little torn on the whole concept. 🤔
@@PermianStrata It is less efficient to run an engine comp as it runs in its own dedicated thread. If they spin much more smoothly in the engine comp, it is mostly that there is room for optimisation in said engine comp. I usually use engine comps only for full on python scripts that run continuously, which would stop the main TD thread from working, or when you are running certain actions or processing that is hard to kill on demand. It is also quite good for light but very frequently repeated operations to run them in a separate thread. Also, the viewer of each nodes in TD necessitates an heavier processing time when powered on. Turning off the viewers generally gets a couple of fps for free. I think it is not relevant when in perform mode or out of a concerned container
@@lainchanzzzzzz It's possible that I wouldn't be facing this dilemma if the patches were better optimized. But I've already cut corners and trimmed the fat as much as I can without severely compromising quality, so I'm not sure there's much more that can be done to that end.
Enjoyed, thank you
Thank you for watching!
this is really fascinating! I'm very new to TD but want to keep learning more. I'll have to come to one of these meetups since I'm in the city!
Thank you for watching! TD has a steep learning curve, but it's definitely worth it.
I am not sure but I thought the Switch TOP only allows cooking for the two selected inputs. Perhaps the CHOP and etc stuff routed into your non selected bases still cooks idk!
I've heard that too. But if I disable the script, the frame rate tanks, so idk 🤷♂
What’s an engine comp? :O
It runs a .tox file in a self-contained instance of TouchEngine. More info on that here: th-cam.com/video/Fau61Cz80iY/w-d-xo.html
Now that I'm running my patches in Engine COMPs, they spin up much more smoothly, but they seem to run less efficiently overall, so I'm a little torn on the whole concept. 🤔
@@PermianStrata It is less efficient to run an engine comp as it runs in its own dedicated thread. If they spin much more smoothly in the engine comp, it is mostly that there is room for optimisation in said engine comp. I usually use engine comps only for full on python scripts that run continuously, which would stop the main TD thread from working, or when you are running certain actions or processing that is hard to kill on demand. It is also quite good for light but very frequently repeated operations to run them in a separate thread. Also, the viewer of each nodes in TD necessitates an heavier processing time when powered on. Turning off the viewers generally gets a couple of fps for free. I think it is not relevant when in perform mode or out of a concerned container
@@lainchanzzzzzz It's possible that I wouldn't be facing this dilemma if the patches were better optimized. But I've already cut corners and trimmed the fat as much as I can without severely compromising quality, so I'm not sure there's much more that can be done to that end.