User manual

17
Active,
Mod enabled
= PURPLE
= PINK
Muted,
Mod disabled
Active,
Mod disabled
= RED
= BLUE
Muted
and
Mod enabled
Mute
To Mute a Channel output, press PGM_A to toggle access the Mute Page. In order to exit the Mute Page, press PGM_A again. The
associated PGM_A LED lights to indicate that the Mute page is active. While active, State changes are ignored. To Mute a Channel, now
press its associated Channel Button to toggle its Variable Clock Output on/o. When Muted, the associated Channel Button LED is red and
ashes with each Rising Edge of each Clock to indicate the currently Programmed Variable Clock.
When a Channel is Active, its associated Channel Button is blue. If a Channel is Mod enabled while Active, the associated Channel Button
is purple. Alternatively, if a Channel is both Mod enabled and Muted, its associated Channel Button is pink (see below).
The purpose of Mute is to stop the Clock activity at the Channel Outputs while still allowing the user to Program desired changes. In this
way, it is possible to Program a new Variable Clock into a Muted Channel. This is useful for cueing changes during live
performance by Machine or Human Programming. Exit the Mute page by pressing PGM_A.
It is possible to Mute several Channels at once. This makes it more intuitive to create interesting timing arrangements.
Please note: these changes ARE NOT SAVED until you Store the State. Without running the Store State operation, changes are not
held when the power is cycled. This is useful for improvising with alternate versions of a Stored theme.