Doepfer Regelwerk (device no longer available) - Manual (Page 17)

Doepfer Musikelektronik GmbH User manual V1.0 REGELWERK V1.2 ❅ ❆ ❇ ❈
and maximum values can be changed to
whatever you want within this scale, so that
the response of the fader will also be
changed to any range within the maximum 0-
127 scale.
•
A system also has to be evolved to decide
between the real and virtual position of the
fader, and determine which of them is sent
out with the MIDI event. This problem
obviously becomes crucial whenever the
actual position of the fader diverges from the
virtual position at all.
−
The ideal solution for this is to have
motorised faders, which automatically adjust
to the programmed value and so avoid the
problem, but for obvious cost reasons that's
out of the question for
REGELWERK .
−
Instead, the user him/herself needs to act as
the motor for any fader whose actual position
differs from its virtual position, and move it till
it's in the right place!
−
Naturally, it's nearly always best for the
events generated during this adjustment
process not to be sent out via MIDI.
•
Various strategies exist to deal with this, each
of which has its advantages and
disadvantages, but there should be one
effective way of achieving it for practically
every eventuality.
•
In addition each fader has the option of
processing any MIDI events which are sent to
the chosen MIDI IN socket, and which fit the
criteria in the relevant MIDI data sentence
(not string), and either re-transmit them, or
use them to control or transform fader
events.
-> see MIDI modes
8.2.2 Key / switch events
•
Each of the REGELWERK 's 24 buttons
underneath the faders can have a sentence
of 2 x 3 values associated with it – or in String
Mode a sentence of up to 2 x 30 values (with
even more in future software updates).
•
These packets of data are then sent out over
MIDI whenever the user performs the
associated action – like pressing the relevant
button. The values chosen to be affected by
a button-push can be inserted practically
anywhere in the MIDI data string, and will
produce an ON/OFF message.
8.2.2.1 Key status
•
The default function of these buttons is as
REGELWERK 's Mute / Demute function,
whose status is shown simply by the LED
above each of the buttons:
−
LED on = Demute: the fader is activated, and
can produce MIDI events,
−
LED off = Mute: the fader is muted, and
moving it doesn't transmit any MIDI events.
8.2.2.1.1 Demute function
•
When the switch is changed from Mute to
Demute status (LED lights up) it will depend
on its position whether a Demute value and
previously defined Key Off event / string is
sent with the Demute value and/or Key Off
event.
•
In muted mode (LED off) the relevant
fader's MIDI events are muted, and not
output via MIDI.
−
Internally, though, the fader movements are
still recognised and dealt with. These
messages aren't internally muted – they are
simply prevented from being transmitted via
MIDI OUT.
8.2.2.1.2 Mute function
•
When the switch is changed from Demute to
Mute status (LED first on, then off) it will
depend on its position whether a Mute value
and previously defined Key On event / string
is sent with the Mute value and/or Key On
event.
•
In Mute Mode (LED off) output of Fader
events from the relevant fader is enabled.
8.2.2.2 Key event input
•
In principle, the menus and functions are
similar to those for Fader events.
8.2.2.2.1 Key ON Event
•
This event refers to the process of switching
from Mute to Demute status (and the LED
thus coming on) -> ON event.
8.2.2.2.2 Key OFF event
•
This event refers to the process of switching
from Demute to Mute status (and the LED
thus turning off) -> OFF event.
8.2.2.2.3 Key ON / OFF parameters
•
These events have certain parameters
common to both, which determine their
behaviour and that of the relevant button.
•
So for instance with the button in Demute