CLKD - TheTechnobear/SSP GitHub Wiki
clkd - clock module
a dedicated clock module with clock division and multiplication
Documentation
Note: This is the primary page for documentation on this modules
- Wiki - https://github.com/TheTechnobear/SSP/wiki/CLKD
- Forum - https://forum.percussa.com/t/clkd-by-thetechnobear
Developer: TheTechnobear
I develop these plugins for free, please consider supporting my efforts with a donation. https://ko-fi.com/thetechnobear
Parameters
| Name | Desc |
|---|---|
| Clock | Clock source: Internal, Clk In, Midi |
| Clk Div | Clock input division |
| Int BPM | BPM for internal clock only |
| Midi PPQN | PPQN for midi clock only |
| Div A-H | clock division / multiplication for Clock X |
| Run/Stop | Run or stop clock |
| Reset | Reset clock |
| TrigSync | syncronise trigs with clock |
Inputs
| Name | Desc |
|---|---|
| Clk In | signal input for cv clock |
| Reset | signal input to reset/sync clock |
| Run | signal input to run the clock |
| Midi Clk | midi clock input, usually from MIDI module |
Outputs
| Name | Desc |
|---|---|
| Clk A-H | Clock outputs |
| Reset | high when clock is reset |
| Run | high when clock is running |
General Usage
CLKD can be used either as a master clock by using the internal clock, or it be slaved to midi or cv using appropriate inputs.
the input or interal clock, generate the modules clock, which then can be multiplied or divided into up to 8 outputs.
when we use clock multplication, then the output clocks are faster than the input clock, so we have to use tempo estimation. i.e. the input clock signal allows use to determine a bpm, and from there we can create faster clocks. if the clock input is stable this is 100% accurate and will stay in time without drift. however, if your input clock flucutates (or you change division), then there will be drift. you can use reset to re-sync (occasionally)
clock division by default works also with tempo estimation. however, trig sync changes this so that we count clock pulses instead e.g. 1/4 rather than estimating the tempo from previous pulses, will instead count 4 pulses and then trigger , regardless of of frequency of these pulses. therefore trigsync is useful as a conventional division module, or unstable clocks. whereas no trigsync is useful as a traditional clock, where you compensate for slight variations in clock pulses. (really this should only be the case with midi, but is possible in other scenarios)
Tips
every clock output is run independently, so if you want to syncronised them all, you should use reset to sync them. similarly you will want to sync external clocks using the reset output.
Change Log
- 1.0.1 early access release