Professional Documents
Culture Documents
3):
mxmxmx edited this page on 29 Jan 2019 · 108 revisions
channel basics:
select the channel (#1 - #6) you want to edit by turning the left encoder.
mode parameters are selected and edited with the right encoder; click to edit. click again to exit
edit-mode.
the first parameter is the main clock mode. it defaults to the basic MULT, though
the mult/div, pulsewidth, and phase % parameters are available across modes. most other
parameters are mode-specific. channel #4 has an additional mode: DAC
pushing the left encoder once will re-sync the channels.
long-pressing the left encoder AND the up button simultaneously will reset all channels to MULT /
default settings, and clear all CV mappings. (NB: this won't permanently reset the module, you'd
also have to save the (cleared) settings to do so. see below)
save settings/state:
long-pressing the right encoder will take you to a menu page saying Load, Save, Apps, Conf.
o to save the channel parameters, navigate to Save using the left encoder and select one of
the four available 'preset' slots (the currently active slot, if any, is indicated by a little dot).
once you've selected a slot, long-press the right encoder again to save the current state; the
cursor should flash a couple of times, then return you to the clock app.
o to load a previously saved preset, do much the same: navigate to Load, select the preset
(#1-#4) and long-press the right encoder. the cursor will flash while the preset is being
loaded, then return you to the clock app.
o if you just want to leave the save/load menu, either navigate to Apps and click the right
encoder or, alternatively, load the currently active setting.
o to reset the module/EEPROM (settings sans calibration data), hold down both the up and
down buttons during start-up.
1
global settings:
CV mapping:
push the down button, that'll take you to the CV page; assign CV channel # by selecting the
destination (right encoder), then click to edit / select the source (CV1-CV4)
basically any parameter can be assigned to a CV input, except reset/mute and a very few others.
values with just 0/1 states (notably clock source) are toggled, if the CV input goes above ~ 1.2V
assignments are cleared either by specifically selecting destination - (ie none), or by long-pressing
the down button (when on the CV page) -> that'll clear all CV mappings in that particular channel)
clock sources:
push the up button, that'll take you to the screensaver preview; now long-press the up button to
slave all channels to the internal clock. a BPM setting will appear, which allows you to adjust the
tempo of the internal timer. the default tempo (= -) is quarter notes, which can then be further
divided down or multiplied via the individual channel settings.
alternatively, you can assign individual channels to either TR1, TR2, or INT (the internal timer) by
adjusting the channel parameter clock source.
long pressing the down button while the BPM page is active will reset all channels to TR1.
reset/mute: when applicable, this assigns a reset source (basically: MULT, EUCLID, SEQ); it
typically doesn't make sense, of course, to choose RST1 when the clock source is TR1, and v.v.
Alternatively, choose =LO2 or =HI2 to mute a/the channel whenever TR2 goes low, respectively
high.
the latency setting (at the bottom of the CV menu), allows to increase the trigger-to-processing
latency by a few microseconds up to 4 milliseconds. this can be useful for timing gate/CV
manipulations, ie if/when control voltages lag behind the main trigger.
echo: pulse-width =
pulse-width of
echo, 1ms, 2ms,
pulse-width external
..., 254ms, 50%
clock, 50% = 50%
duty cycle
phase offset (in % of
phase % 0 - 99
period)
select channel
/64, /48, /32, /24, /16, /12,
mult/div division/multiplication
.... x48, x64
factor
2
available
range/values note
parameters
NB: these basic settings are available across all modes (when applicable).
NB: when multiplying (x2, x3, ...), the pulse-width gets halved, too; in those cases, the displayed
number is no longer reflecting the actual pulse-width, but will be a fraction of that value. rather, say,
60ms is 30ms when multiplying 2x, 20ms when x3, etc.
3
available
range/values note
parameters
NB: the burst frequency or 'speed' is determined, in the first instance, by either the internal BPM
clock (when choosing clock src = INT) or by a/the external clock (when choosing clock src =
TR1 or clock src = TR2) plus whatever multiplier/divisor settings are applied. f (initial) is a
percentage of this frequency.
you can use either TR1 or TR2 to actually trigger a burst: when clock src = TR1, TR1 determines
the frequency and TR2 triggers the burst, and vice versa. when clock src = INT, you can choose
which trigger input to use (ie burst src = TR1 or burst src = TR2).
note that an incoming trigger will choke an ongoing burst, even if phase-delayed. (that's not, exactly,
a bug, more like an artefact of the implementation as is).
logic
operation
logic type AND, OR, XOR, NAND, XNOR, NOR
to
perform
channel
used as
op1 ch#1 - ch#6
operand
#1
channel
used as
op2 ch#1 - ch#6
operand
#2
what to
operate
on:
track --> P_W, state pulse-
width, or
on/off
states
NB: since the channels are processed sequentially, rather than in some quantum-entangled
fashion, the result of the logic operation may not reflect the current output-state of the operand
channels; it may lag behind by one clock or be lost in time in some way or another (notably, when
logic operations are performed on channels performing logic operations).
'tracking' P_W differs from tracking on/off state (beats) in the way the operands enter the equation,
which tends to result in different output patterns. Thus, a pulse with, say, 10% duty cycle will be
treated (as far as the logic operation is concerned) as "true" only 10% of the duty cycle, and as
4
"false" 90% of the duty cycle (in terms of P_W); in terms of state, it'll count as "true" for the entire
duty-cycle. A skipped beat will simply be "false", either way, of course.
select trigger
sequence # USER1 - USER4
pattern #1-4
edit trigger
--> edit length: 2 - 16, on/off
pattern
concatenate
- patterns, up
playmode , SEQ+1, SEQ+2, SEQ+3, TR2+1, TR2+2, TR2+3, SH- to 64 steps;
1, SH-2, SH-3, SH-4 or CV-
address (SH)
editor UI note
go to previous sequence
down button
('edit offline')
details:
binary,
random,
'turing
DAC: mode BIN, RAND, T_M, LGTC, SEQ
machine',
logistic map,
sequencer
DAC output
range
DAC: range 1 - 255
(centred at
0V)
DAC
voltage
DAC: offset -3 - +3 offset (~ 1
volt/octave
(ish))
primitive sequencer, where the channel on/off states determine the output value:
o clock channel #1 = MSB, clock channel #6 = LSB (channel #4, being the DAC, isn't counted,
hence 5-bit)
o the sequencer can either track P_W (pulsewidth) or on/off state. (for details
see LOGIC above)
random values, with weighted history (basically, this averages over the last 1-8 output states
(= depth) according to some weight factor (= weight))
6
emulation, sort of, of the popular 'turing machine'; ie some kind of shift register based output. the
parameters (LFSR length, LFSR p(x)) work as above (see LFSRmode).
provides chaotic rather than random output, with one parameter: LGST(R), the r coefficient of the
equation.
editing works much like the trigger sequencer (see above), except there's only one 16 step track
and you cannot mute steps (because there's no corresponding trigger output).
use the right encoder adjust the pitch value (coarse); to fine-tune, hold down the left encoder while
turning the right encoder.
playmode: choose from the typical set of directions
(fwd, rev, pendulum, random resp. up, down, up/down and random).
when playmode = ARP, steps can be muted: muting a note removes it from the arpeggiation
pattern. the ARP mask can also be rotated (-> mask CV).