BeatClockPlayer:
Filter:
crucial-library/Classes (extension) | Libraries > crucial > Players | Libraries > crucial > Scheduling

BeatClockPlayer
ExtensionExtension

'trig' rate player that plays steady impulse triggers locked to tempo

Description

A 'trig' rate player that plays steady impulse triggers locked to tempo

The cpu-cheapest ways to get a steady tempo locked trig. If it starts precisely on a downbeat, it can be trusted to keep on the beat for a very long time.

BeatClockPlayers will share Synths if one is already running on the server that has the same tempoFactor. Only one needs to be created on the server for every time division. After that, subsequent requests for a BeatClockPlayer to play will resuse the same Bus that the first one is playing on.

Class Methods

.new

Arguments:

tempoFactor

tempoFactor is in old-style music terms: 16 means a 16th note. 8 means an 8th note 1 is a whole note. etc.

mul
tempoBase

Instance Methods

.tempoFactor

.tempoBase

.mul

.storeArgs

.makeResourcesToBundle

Arguments:

bundle

.asSynthDef

.defName

.synthDefArgs

.spec

.guiClass

Examples

BeatClockPlayer is actually just an Impulse ugen with its frequency driven by the tempo setting. When used at the same time as a Stream2Trig, StreamKrDur or other client-side scheduling driven device, it is possible for inaccuracies in the accounting methods to build up to noticeable loss of sync.

Even clicking on different windows is leading to disturbances. This is TempoClock's inaccuracy, it is lagging. [note: not tested recently]

Change the tempo using the slider. At slower tempos its off.