The qmetro object is similar to a combination of the metro object 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. Most objects also support automatic "dropframing" in order to keep up with realtime if the requested operation cannot be calculated in realtime. Certain things like OpenGL drawing commands are not suitable for this kind of "dropframing" and instead, the metronome driving such events must be "dropframed" using the jit.qball object in order to ensure that they will not backlog the queue. The qmetro object is a single object replacement for this functionality.
This object uses the Max time format syntax, so the interval that the qmetro object uses can be either fixed or tempo-relative. Its output can be quantized using tempo-relative syntax, and if the autostarttime attribute is set, the object can start at a tempo-relative point.
The optional first argument sets an initial value for the time interval at which metro sends its output. This time interval can be either a number which specifies time in milliseconds (e.g. metro 100) or notevalue (e.g. metro 4n).
Note: While the metro object lets you specify time in any of Max's standard time formats, the attribute argument should be used when specifying time in any other time unit besides milliseconds or notevalues (e.g. ).
If there is no argument, the initial time interval is 5 milliseconds.
Turns the qmetro object on and off.
If turned on (non-zero) the qmetro object will begin running automatically at the time specified with the autostarttime attribute.
autostarttime [10 atoms]
If the autostart attribute is enabled (non-zero) the qmetro object will begin running automatically at the time specified with the this attribute. The autostart operates as a timepoint object that is internal to the qmetro object.
Turn this on to send output in the low-priority queue.
interval [10 atoms]
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.
This attribute names a master time transport. If the time is specified using a 'relative' unit (for example: ticks, bars.beats.units, or notevalues), then the named transport is used to determine delay times based on tempo, time-signature, and other related information.
Common Box Attributes
In right inlet: The number is the time interval, in milliseconds, at which qmetro sends out a . A new number in the right inlet does not take effect until the next output is sent.
|Timing and Sequencing Events||Timing and Sequencing Events|
|Max Basic Tutorial 4: Metro and Toggle||Max Basic Tutorial 4: Metro and Toggle|