this is a 'double edged sword' ... interpolation/smoothing is not free, it costs cpu, which is a scarce resource on the STM32F4, so I prefer to put it in explicitly when required. (of course the exception is where its essential to the function e.g. a vca ), e.g from a cc input, to a particular parameter on an object, sometimes that smoothed outlet can then also go to multiple inlets/objects.
I guess the 'ideal' option, would be an attribute which would enable/disable interp/smoothing code at compile time but this would have to be per parameter/inlet , which would clutter the object interface quite quickly.
its these kind of thing, where perhaps in some places, the factory looks 'low level' rather than end-user friendly, but the advantage is that you can spend your cpu cycles where you need them.
( you can of course create your own subpatches to create smooth/interp versions which you find yourself using repeatedly)