RESOLVED: OSC Out interruption - « Cook Every Frame » off

Bugs
1

Hi !

There seems to be a problem regarding the « OSC Out » operator. When « Cook Every Frame » is off, the operator won’t cook as soon as you don’t see it in you’re network (exit my example’s container « OscOut» to see that the « oscin1 » operator stops receiving any input).

For a temporary fix, we can view the « OSC Out » operator via an « OP Viewer » in our UI so it still cooks.

Thanks for your help on this !
OscOut_BugReportExample.toe (4.23 KB)

2

Operators only cook when their data is requested in some form.
When nothing’s looking a one, it generally stops cooking.

In your case ‘Cook Every Frame’ allows the behavior you are looking for.
Is there a case you’re trying to solve by turning off that parameter?

For more information see:
docs.derivative.ca/Cook#Cooking_Details

Cheers,
Rob.

3

I got mixed up with « send events every cook » and « cook every frame » I guess. I thought turning off « cook every frame » would be better, optimization wise, in a case where the channel’s value changes occasionally. But it doesn’t seem to help even in that case.

Thanks for your reply!