How much added computation results from a non-zero value in the feedback parameter window of a filter?

Question

Kyma issues the warning "You may have exceeded the limits of realtimecomputation..."  for a timeline I've use with some regularity ... but it always plays back fine. (I've even used it repeatedly in concerts!) Today, while tweaking it for an upcoming performance, I decided to added a very low value in the feedback parameter window for two LowPassFilters. That change seems to have been enough to cause the TimeLine to fall out of realtime. Return that value to zero and it runs again. Huh?

Have I proved once again the old proverb about the straw that broke the camel's back?  ;-)

Answer 1

Kyma is always trying to optimize behind the scenes so there are situations where entering a zero into a parameter field is detected and allows us to do less computation.  So yes, it is possible that changing a parameter from a constant 0 to a non-zero value could generate a slightly different program that takes slightly longer to compute or that it requires allocating memory on a processor that was not required when the parameter was zero.