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

Doepfer Musikelektronik GmbH User manual V1.0 REGELWERK V1.2 ❉ ❊ ❋ ●
status, a Fader event for a particular fader
can be sent with your choice of any number
from 0 to 127 as the Demute value.?? With
the Demute value set to 'NO', on the other
hand, no Fader event is transmitted.
•
Thre are two clearly-defined ways in which
the REGELWERK responds to a button-
press:
−
With Momentary Switch mode selected, a
button-press changes from Demute to Mute,
and releasing it again changes back from
Mute to Demute.
−
With Toggle Switch mode selected, the fader
switches ('toggles') between Mute and
Demute status and remains the same until
another button-press.
8.2.3 MIDI modes
•
Each fader is fundamentally a MIDI data
source.
−
First of all, it's important to specify which MIDI
OUT socket it will transmit MIDI events to.
•
A fader can also receive MIDI data, though.
−
i.e., incoming MIDI data can interact with the
fader and change or modify the fader's
properties (by changing the programmed
values, switching off an element of fader
control, etc.)
•
For this function to work, the respective
incoming MIDI event must match the settings
of the particular fader event, and /or must be
input via the correct MIDI IN socket. ??
−
For any chosen incoming MIDI event, first of
all a check is made to see if any fader is set
to receive its MIDI mode.
−
For each input message, all 24 faders have
to be systematically checked for MIDI events.
−
In Momentary mode, only Note On / Off, and
Controller Events are taken note of.
−
The search starts at fader 1 and goes
through to fader 24. As soon as a match is
found, the search is called off, and the
programmed function adjusted accordingly.
Events which match in all respects except
MIDI mode aren't recognised (v1.0).
−
Thus the intended events should be
positioned as early as possible in the fader
sequence, for quicker search results, and
other events kept as far away as possible (to
avoid the worst case scenario of 24 faders
having to be searched before the correct one
is found).
8.2.3.1 Normal
•
Normal fader mode, with the data ouput on
the chosen MIDI OUT/s.
8.2.3.2 Velocity Overdub One/All
•
The incoming MIDI event received at the
chosen MIDI input has a new velocity (MIDI
data byte 2) imposed ('overdubbed') on it.
•
The new event that is created is then output
on the chosen MIDI output/s.
•
In All mode, the event's MIDI data byte 1 is
ignored, and the overdubbed value is
imposed on all 128 events of this data type
on this MIDI channel.
−
In One mode, one chosen MIDI event has, for
instance, a new velocity imposed on it. This is
mainly for the first group of controllers, sent
from an external sequencer or master
keyboard, etc..
−
All mode is more suited to the second group,
Note Events, so that, for instance, velocity
can be imparted to all the notes on a certain
channel - if, e.g., the originating keyboard
doesn't transmit velocity messages.
8.2.3.3 Velocity Multiplication One / All
•
This is like velocity overdub, except that
instead of replacing the old velocity value, it
multiplies it by the fader velocity value.
−
This comes into its own when the velocity of
the incoming MIDI data is generally
satisfactory, but just too loud.
-> Useful when layering sounds.
−
In software version 1.xx this only works to
decrease velocity (a fader set at half-way
halves it).
8.2.3.4 Update
•
The actual fader values can be changed from
an external MIDI source.
−
For total recall, or for simultaneous control
over another computer / controller or
REGELWERK with a fader page or the like,
so that the data changed in the external
controller is also changed in the receiving
REGELWERK . -> Update
8.2.3.5 Hook On
•
Faders set to 'hook on' in the Special
Functions menu send no data at all until they
are told to.
•
They remain in this state until a MIDI IN
message with right MIDI event is sensed and
'caught'. See Catch mode.
−
The threshold for this is adjustable in the
Special Function menu.
•
As soon as the relevant criteria are met, the
particular fader is released, and can send
events again. This is indicated by a rapid
flashing of the relevant LED.