Is there a way to stop COMPs from cooking. Being able to trigger COMPs from cooking can help me optimize, save space while performing.
better practice is to figure out why its cooking (i.e. what is pulling it that is causing a render), and bypass that when it isn’t in use. I’ve recently been adding an ‘Active’ parameter to my scenes that gets enabled when i fire that scene, and disabled on exit. if there is always cooking data, like noise Chops driving something, or an external MIDI/Tempo source, I’ll create dummy channels in a constant, and use a switch to bypass the data that cooks my scenes when they aren’t in use
2 Likes
How can I use a button to trigger the cook flag
You can make a button execute this code:
op('opname').allowCooking = 1
or
op('opname').allowCooking = 0
will turn it on or off respectively
This single line is a ‘trick’ that will toggle it:
op('opname').allowCooking = 1 - op('opname').allowCooking
If you specifically want to use a Button COMP, connect a Null CHOP to the output of a Button COMP, change the Button COMP to ‘Momentary’, create a CHOP Execute DAT, point it to the Null CHOP, turn on the ‘Off to On’ setting, and one of the above three lines to the def onOffToOn section of the DAT. Thus, pressing the button will make the line of code fire.
1 Like
This ^
Using cook flags for turning things on and off will invariably lead to frame drops when you turn them back on. We avoid using the cook flag for any ‘live’ part of a project.
is there anyway to watch cooking status with dat or chop?
You can attach an Info CHOP to any operator and it will give you cook information. Is that what you meant?
Yes but it is not solution because info chop does not give me cooking status real time.
Could you explain what you mean by ‘cooking status’?