Easy Optimization Tricks in TouchDesigner - TouchDesigner Tutorial 060

[@outsandatv]

Working on a huge project, i was desperate until i viewed this. THANK YOU SO MUCH

[@TheInteractiveImmersiveHQ]

Really glad to hear it! Thanks for watching :)

[@valentinsiltsenko]

The last optimization tip is a gem! Hopefully this functionality will be builtin in TD someday.

[@andresactis7435]

i do this just by changing my null to "selective" type of cooking . i don´t know if it is the same result though

[@spencersterling1565]

@@andresactis7435 Came here to say this. It should have the exact same result

[@TheInteractiveImmersiveHQ]

Thanks! It's a nice one to keep in the back pocket!

[@TheInteractiveImmersiveHQ]

@@spencersterling1565 You could use selective cooking, but often times I find if I can be in control of a specific process, I prefer that to relying too much on behind-the-scenes magic. Both could work but I've never been a huge fan of Selective Cooking, although a few of my peers swear by it :)

[@4i20]

amazing

[@TheInteractiveImmersiveHQ]

Thanks!

[@danrowan-smith399]

Ah wish I knew that thing about the switch last week! Great video thanks

[@venjsystems]

the f-string thing at the end was gold!

[@TheInteractiveImmersiveHQ]

Those are possibly my favourite new Python feature!! So easy to make strings quickly!

[@DAMAGR]

Can we get some more network/project optimization videos?

[@mstnmtz]

amazing- you saved my career literally

[@TheInteractiveImmersiveHQ]

Glad to hear it was helpful :)

[@fabiankunz5619]

For the last example with the OSC in chop, isn't it much easier and also more performant than using python to just change the cook type setting in the null to selective?

[@TheInteractiveImmersiveHQ]

We're not aware of the performance difference between the two having been thoroughly tested. Elburz is in the mindset of having things be explicit versus implicit -- so even if the CHOP Execute takes slightly more resources, you know exactly how and when it's functioning. If you were to use the Selective mode on the Null CHOP, you're at the mercy of code that you can't see/control/monitor if you have to debug issues later. Hope that helps!

[@deadmusik9969]

good stuff here!!

[@TheInteractiveImmersiveHQ]

Thanks for watching :)

[@lucastemmer3113]

Hi, if I want to have a slider in my project, that makes my texture very blurry, how would I do this to make it smooth and efficient? Pre shrink goes up in steps, so that makes it not smooth. :)

[@TheInteractiveImmersiveHQ]

Unfortunately, the pre-shrink parameter can't be adjusted smoothly, so an option here would be to crossfade between an unfiltered and a blurred version of the texture. Hope that helps!

[@giovanniiacovella7992]

Having a bit of problems in setting the script up, it should work on mac as well right?

[@TheInteractiveImmersiveHQ]

Is that the Python script at around 11 minutes? That one should work, if you're having issues double check everything is typed in exactly as my example although you might need to change your operator names based on your project. What kind of error are you seeing printed in the textport?

[@afrosymphony8207]

so wait you tellin me every touchdesigner is some kind of chef cause we cookin stuff? woah, awesome

[@TheInteractiveImmersiveHQ]

Nailed it!

[@Woolookologie]

I tried out the very helpful trick with the switchchop for a network with multiple heavy scenes inside comps. Sadly they still seem to render everything despite the cables not appearing to cook... I have the viewers turned off but in the performance monitor they still take up a lot of ressources. Any ideas? Thanks for your content! Edit: to be more exact I'd need a way to completely turn off a comp using a midi controller while in perform mode...

[@TheInteractiveImmersiveHQ]

It's possible to turn off a COMP's Cooking flag with Python via op('COMP Name').allowCooking = False, but you'll likely see frame drops whenever you start or stop cooking, so this is generally not a recommended technique. One important thing to consider is that different types of content might require a slightly different approach to optimization. Is the content found within the COMPs mostly 3D renders, 2D or both? Are you playing back videos? A reference worth checking out is the sceneChanger component which you can find in the Palette -> Tools, which accomplishes a similar outcome and is optimized for high performance.

[@Woolookologie]

@@TheInteractiveImmersiveHQ very useful insights, thank you so much!!

[@stijnvandenbogaard]

The switch top doest stop unused inputs from cooking. Does anyone know that i do wrong?

[@TheInteractiveImmersiveHQ]

This can happen when the viewer for the operators connected to the unused input are turned on. If you click the “Viewer” button in the top left of those nodes, they should then stop cooking. Hope that helps!

[@dianedouglas210]

@@TheInteractiveImmersiveHQ Oh my god I thought I was going insane. I was doing exactly what you were doing with the switch and it looked for all the world like all inputs were still cooking until I saw this comment and turned off the viewers. Thank you!!!!

[@Noah-kf9vw]

same problem here, even with all the Input OPs viewers turned off, they are all still cooking...

[@SkywalkerVisualStudio]

hey mate, can you please copy your simple code here, I would really much appreciate it, as vj suffering with cooking.

[@TheInteractiveImmersiveHQ]

Do you mean the code that is in the last trick? If so, you can put the code from the comment below into the valueChange function:

[@TheInteractiveImmersiveHQ]

update_op = op('constant3').par target_param = f'value{int(channel.index)}' setattr(update_op, target_param, val)

[@sildereuver]

@@TheInteractiveImmersiveHQ This is great! Is there an easy way to copy the channel names as well?

[@sildereuver]

update_op = op('constantOSC').par target_param = f'value{int(channel.index)}' target_name = f'name{int(channel.index)}' setattr(update_op, target_param, val) setattr(update_op, target_name, channel.name)

[@TheInteractiveImmersiveHQ]

@@sildereuver If you plug your CHOP into a Constant CHOP and then in the parameters of the Constant CHOP there's a button called Snap which will copy all the inputs to the Constant CHOP including the names of the channels.