Slows down throughput of messages. Limiting is based on a minimum amount of time between passed message.
The qlim object is similar to a combination of the speedlim and the Jitter jit.qball object. In Jitter, most execution take places in the low priority queue to prevent drawing to the screen at interrupt. The speedlim object unfortunately places messages back in the scheduler for execution, and thus may result in a crash when used to temporally downsample streams of Jitter matrices if Overdrive is turned on. The qlim object is an interrupt safe replacement for this and other tasks.
The minimum amount of time between successive outputs. Time can be specified in any of the time formats used in Max. If there is no argument, the minimum time is 0 milliseconds.
Turn this on to send output in the low-priority queue.
quantize [10 atoms]
Send output only on the specified time-boundary if appropriate. This is achieved by making internal adjustments to the times used for sending output. The quantization can be specified in the following time formats: bars.beats.units, ticks or note values.
threshold [10 atoms]
Sets the time threshold. The threshold can be specified in the following time formats: bars.beats.units, ticks or note values.
Common Box Attributes
In right inlet: The number is stored as the minimum amount of time, in milliseconds, between successive outputs.