thank you for the very clear and informative answer.
spat5 DSP objects (like spat5.spat~) always work with a “scheduler in audio interrupt” mechanism : the incoming messages are processed at the beginning of the next audio tick. So, using a smaller “signal vector size” offers a better temporal granularity (at the expense of a higher cpu load).
I see. So, unless we have signal vector size < 48 (at 48kHz), spat5.spat~ will always process messages after more than 1ms, even if Max messages are sent every 1ms. And, on the contrary, if lower it will potentially process the same value because of the last message received (for istance, with 16 samples signal vector size, last message will be processed 3 times). Am I correct?
What is your problem or what are you trying to achieve ?
No problems fortunately, just want to understand and use the tool in the best way for me. I was thinking about having smoother transitions, thus trying to overcome the Max scheduler.