Short Operating instructions

Switching on

• Once power is applied to the REGELWERK, the display will show the following message:-

REGELWERK V x.xx
DOEPFER (c) 210397

• V x.xx shows the current version's software release number, where x.xx stands for whatever version / release number has been reached.
• The actual date of the release will also be shown in the day / month / year format, so that, for instance, 210397 is March 23, 1997.

• at the same time, on power-up REGELWERK automatically loads Preset 1 and Pattern 1.

• Preset and Pattern 1 are the default data.

Menu structure

• The 16 buttons near the alpha-dial are the main tools to access the REGELWERK menu structure.
• TD shese buttons don't have indicator LEDs, but instead, generally, the relevant parameters are displayed in the second line of the LCcreen, in words.

• In most menus related parameters can be found one after the other, in so-called parameter groups. To access them, you simply keep pressing the menu button again until your chosen item is reached. Individual parameters are accessed one after the other, and keeping on pressing gets you back to the beginning again.

Menu overview

• Here's an overview of the various menus / parameter groups in the current version of REGELWERK.

• In later software versions the menus may be enlarged by the addition of further related parameters.

• For the purposes of this manual, the two rows of buttons near the alpha-dial are numbered from 1-8 (upper left to right) and 9-16 (lower left to right).

• The various parameter groups' menu headings are as follows:-

• ‘16 buttons dedicated to menu selection'.
• The top row of buttons (1-8) except for 1 & 2, (Dec. / Inc.), all relate to the specific track selected.

(1) Step Left / decrement Dec -1/<

• To move one place to the left, or reduce a value by 1, and also, in some menus, to specify something within a menu.

(2) Step Right / increment Inc +1/>

• As 1, except right instead of left, and increase instead of reduce.

(3) Fader Edit

MIDI channel:

• The MIDI channel of the particular event

MIDI event:

• The type of MIDI event
  

First MIDI data byte in words:

• The first MIDI data byte – i.e. whatever event has been programmed - translated into words

Second MIDI data byte in words:

• The second MIDI data byte – i.e. whatever event has been programmed – translated into words

String editor:|__,__,__,__>

• Template / editor for data strings (max. around 30 bytes in the current software version)

(4) Fader Param.

LowerVal.:

• The lower value programmed for the fader

UpperValue:

• The higher value programmed for the fader

ActMode:

• The response mode of the fader – Immediate, Relative or 'Catch'.

Threshold:

• The threshold specified for the 'Catch' response mode if chosen in ActMode menu

MIDI Input Mode:

• Configuring what is sent to MIDI outputs 1 and/or 2, and how this is affected by what comes in at MIDI inputs 1 and/or 2.

MasterSlave:

• Programming whether each fader acts as a master or slave.

LearnMode:

• 'Learning' from MIDI events at the MIDI Inputs, without having to go into the individual edit menu.

(5) Key On Edit

• The same menus and functions as in Fader Edit, but now concerning the operation of the 24 on/off buttons, and their relation to Key On function.

MidiChannel:

• The MIDI channel for these MIDI events

MidiEvent:

• The type of MIDI events programmed
  

First MIDI data byte in words:

• The first MIDI data byte – i.e. whatever event has been programmed - translated into words

Second MIDI data byte in words:

• The second MIDI data byte – i.e. whatever event has been programmed – translated into words

String editor:|__,__,__,__>

• Template / editor for data strings (max. around 30 bytes in the current software version)

6) Key Off Edit

• The same menus and functions as in Fader Edit, but now concerning the operation of the 24 on/off buttons, and their relation to Key Off function.

MidiChannel:

• The MIDI channel for these MIDI events

MidiEvent:

• The type of MIDI events programmed

First MIDI data byte in words:

• The first MIDI data byte – i.e. whatever event has been programmed - translated into words

Second MIDI data byte in words:

• The second MIDI data byte – i.e. whatever event or value has been programmed – translated into words

String editor:|__,__,__,__>

• Template / editor for data strings (max. around 30 bytes in the current software version)

(7) Key Param.

MuteValue:

• The data value which enables Mute

DemuteValue::

• The data value which enables Unmute

SwitchMode:

• Selecting which of the two modes (momentary or toggling) the switches are set for.

(8) Fader Mode

• To switch from sequencer or edit mode into fader mode, and switch the LCD readout to a sort of MIDI event monitor

(9) Special Function

HookMode: Off / On

• Enable / disable 'hook mode'

Threshold

• Set the threshold for 'hook mode'.

Overdup: Off / On

• Enable / disable 'overdub' mode

MIDILock: Off / In1 / 2 / 1 and 2

• Enable / disable either or both MIDI inputs

Sample / Sek.:

• Global 'refresh' rate for all faders (from 8 to 24 samples per second).

10) String Edit

faderXXX Edit Name

NoName! Make? > OK

• Editing page for giving faders names (eg VCF1 cutoff).

EditString: Pres

EditString: Start

EditString: Stop

EditString: Cont

EditString: Rew.

EditString: Forw.

• Editing page for data strings for a given function or button.

(11) Edit Tools

COPY Event type / value between two locations

• Copying function, for duplicating the most important data and pasting wherever required.

(12) Snap Tools

Get SnapShot

Store Snap:

Delete Snap:

• Snapshot function management page

(13)Preset / Pattern Tools

Get Preset / Pattern

Store Preset / Pattern

SysEx Preset / Pattern

Init Preset <OK>

Init Pattern <OK>

• Preset / pattern management page

(14) Sequencer Sync

SYNC – INTERN / EXT.

MIDI / Sync synchronisation

(15) Sequencer Parameters

Midi Channel

Note Number

Step Time

Gate Time

End Step

• Track parameters, global for each of the eight tracks.

(16) Sequencer Mode

NoteNr (StepNr)

Veloc. (StepNr)

• Note number / velocity for each of the 16 steps in a track, which can be programmed with the alpha-dial (with selection via Gate On / Off buttons) and / or directly via the sequence faders 9-24 (16 steps in total).

The eight buttons with LEDs, for global real-time control (from left to right):

(17) START button (no LCD readout):

• for starting REGELWERK from zero on the chosen track, and simultaneously sending a MIDI START realtime message – and, if programmed, a START string (StringEdit: Start).

(18) STOP button (no LCD readout):

• For stopping REGELWERK, and simultaneously sending a MIDI STOP realtime message – and, if programmed, a STOP string (StringEdit Stop).

• On the first button-push, the STOP button LED blinks. This shows a sort of 'pause' mode, which can then be turned into STOP or CONTINUE by pushing the relevant button.
• On the second push, the STOP button LED stops flashing, and stays on. Simultaneously, the REGELWERK's internal buffer is cleared, and an All Notes Off message is sent on all 16 channels to MIDI OUT.

(19) Cont. (continue) button (no LCD readout):

• for starting REGELWERK from the current position in a sequence, simultaneously sending out a MIDI realtime CONTINUE message, and, if programmed, sending out a CONT string (StringEdit: Cont).

(20) Tempo button (with LCD readout):

• for setting the internal tempo of the REGELWERK in bpm (50 - 255 bpm). (The tempo value is stored with the pattern).

(21) REWIND (no LCD readout):

• for sending, if programmed, a REW string. (StringEdit: Rew.)

(22) FORWARD (no LCD readout):

• for sending, if programmed, a Forw. string (StringEdit: Forw.)

(23)Snapshot function:

• for taking a 'snapshot' of current settings:
• Sending out a full MIDI dump with all current settings. When the button is pressed, the LED blinks, to indicate that the snapshot is ready to be saved to your chosen location (using StoreSnap from the Snap Tools menu).
• A saved Snapshot can be re-loaded by going to ‘GET SNAPSHOT: (in the Snap Tools menu) and entering the correct location.
• n.b.: This is NOT the way to save a Snapshot: if the LED isn't flashing, the Snapshot won't be saved.

(24) ENTER/OK button:

• for functions which require confirmation. To show that confirmation is necessary, the OK button's LED flashes.

• Buttons (17)-(24) and their relative functions can be enabled from anywhere in the REGELWERK's editing pages. Displaying and editing Tempo simply overwrites the current LCD message.

(25) Alpha dial.

• To increase a value, turn clockwise. To decrease a value, turn anti-clockwise.

Menus in detail

Step Left / decrement

• Moves one place to the left; also used in some menus; and/or decreases a value by one.

Step Right / increment

• Moves one place to the right; also used in some menus; and/or increases a value by one.

Fader Edit

• For editing the MIDI events associated with each fader. The fader is selected by pressing the relevant Fader Select button (above the faders) .

• Sub-menus: (selected by repeatedly pressing the Fader Edit button)

MidiChannel:

• Select the MIDI channel for the fader event.

Select the type of event:

• MidiEvent: shown in abbreviations
• NoteOf Note off
• NoteEv Note event
• PolAft Polyphonic aftertouch
• Contrl Controller
• PrgChn Program change
• MonAft Monophonic aftertouch
• PitBen Pitch bend
• String String

• String is a special case, in which a user-programmed string instead of a simple fader event is dealt with and output via MIDI.
• In the String menu, the editing values for MIDI data bytes 1 and 2 have a special function, for String control parameters.

• Besides this, there are also special ('meta') events.

• These aren't necessarily related to the MIDI function of the faders, but can be used, for instance, to program the REGELWERK for real-time control.
• For instance, various sequencer parameters can be controlled directly without having to go through a series of menus or use the alpha-dial.

MidiEvent: special (meta) events

• Extens Extensions
  'Place holders' for expansions

• TrkPat Track patterns
  Pattern selection for sequencer by using faders.

• TrkEnd Track end
  Selects the last ('reset') step of a sequence track using the faders (in the range from 1-16)

• TrkVel Track velocity
  Selects the global Track Velocity for a sequence by using the faders.

• TrkNot Track note
  Selects the global base note for a sequence by using the faders.

• StpVel Step velocity
  Selects individual step velocity by using the faders (changing the MIDI channel changes the instrument playing this step).

• StpNot Step note
  Selects individual step note number by using the faders (changing the MIDI channel changes the instrument playing this step

• NoStat No status
  Selects no event to be sent – if for instance the fader is being used just as a master controller.

• To some extent, the parameters which are controllable by meta-events can also be controlled by other means (in the sequencer menus).
  Using meta-events for control has the main advantage that almost all fader control features and functions can also be controlled by meta-events.
  The disadvantage is that if meta-events are being used, the faders can only be used for sequencer, not Fader events.

For

• MidiEvent: StpVel, StpNot
  there's also a display for
• StepNumber
  since it's essential, when dealing with a fader as controller, to know which step number is being programmed.

For

• MidiEvent: Extens, TrkPat, TrkRun, TrkVel, TrkNot
  there's also a display for

• ‘Not used Par.:’
  since for sequencer fader events the MIDI channel is selected in the Sequencer Parameter menu.

First MIDI data byte in words, plus Note Off note:

• Note Number: ,
• Pol Aft Number: ,
• Contrl Number: ,
• Prg Chn Number: ,
• Mon Aft Number: ,
• Pitch Be Val.1: ,
• String-Xpos: .

Range 0..127.

..............:Sld

• This is the location where the fader's actual value is entered. 'Sld' is short for 'slider'.

• If the ‘String’ event type shows this display:

String-Xpos:

• then the desired variable value for the fader should be input. This can go from 0-127.

For

MidiEvent:

• Extens,
• TrkPat,
• TrkRun,
• TrkVel,
• TrkNot,
• StpVel,
• StpNot

there's also a display

• TrackNumber:
  since for sequencer fader events it's necessary to specify which track is being referred to.

Second MIDI data byte in words:

• NoteOfVeloci: ,
• NotenVelocit: ,
• PolAftVeloci: ,
• ContrlValue: ,
• No sec. Byte:.
  
  With regard to the adjustment range as above, normally the Sld (slider) value will be set here.

When this value is irrelevant or invalid for a particular type of event, the following message appears:

• No sec.Byte ,
• PitchBeVal.2: ,
• String......: .

In the String- Editor window, a template appears, which starts off looking like this:-

• 000|__,__,__,__>
  
  XXX<,aa,bb,cc,dd>
  
• At any one time you can see the hex-strings for four bytes, in hexadecimal notation.
• Position XXX = aa, XXX+1 = bb, XXX+2 = cc, XXX+3 = dd.
• Use the </> (Inc/Dec.) buttons to scroll backwards and forwards within the template. The symbols </> appear, to show if there are further positions available to the left or right. When the end is reached, the symbol ‘|’ replaces < or >.
• The byte in position 'aa' is always the one which can be edited.

• At present the maximum length is 30 bytes. (In future software versions it could be higher)

• In all cases, to enter a string, the length must first be defined.

• Any positions which lie outside this defined length are shown as either _ or 00.

1. For example:
   If the string is going to be three bytes long :
   
2. Scroll to position 3
3. Turn the alpha dial until
4. ‘ ..; ’ appears.
5. The OK LED should blink.
6. Press OK.

• This causes you to leave the fader edit menu, and you need to re-enter to produce the correct string!

• The value that has been chosen for editing can now be scrolled to, using the </> buttons, and when it is in the 'aa' position, it can be edited using the alpha dial.
  
• Some bytes which aren't part of standard MIDI are reserved for internal REGELWERK functions, and are shown by the symbols ‘..;’ or ‘>>‘.
• The first MIDI data byte 'XX' is entered into the incomplete string, to set the fader value.
• To enter strings in the editor, it is advisable first of all to write the string out on paper, and then to enter it carefully, with reference to your notes. Otherwise it's very easy to lose one's place. The current software version doesn't have any insert or delete function, so it can be extremely time-consuming to correct a mistake in a string.

Fader Parameters

• As well as the basic fader event information, some further parameters often need to be set.

LowerVal: 0-127

UpperVal: 0-127

• The standard fader response goes from a minimum value of 0 (with the fader right down) to a maximum value of 127 (with the fader right up).
• These values can be changed if required, to produce any other fader response characteristic you might want – reversed, if you feel like it.

• These related values 0,127 are accessed separately, so that no conversion is needed, and the proces is actually faster. There's no need to change the default value of either, unless you have a specific need to.

Actmode:Immediate/Relative/Catch

• This determines the way the actual fader position relates to the value output by it....
• ... and / or the difference between the fader position and the actual value.

• Immediate: -> The fader position = value.

• Relative: -> The fader position is added to the existing value to create the output value.

• Catch: -> A new value is only output once the fader has been moved so that it goes through ('catches') the existing value.

Threshold:

• Window / capture area for Catch mode.

MIDI Input-Mode: (n.b.: not directly visible in the display)

• Each fader can be programmed to send MIDI data to different combinations of MIDI Out -> O12 = Output 1 & 2,
• O1 = Output 1,
• O2 = Output 2,
• XXX = no value output.

• A fader can also act as a MIDI data receiver - incoming MIDI data are altered or 'worked on' by the fader, and/or themselves change the fader response – altering the output value, switching the fader on, etc..

• For these functions to work, the incoming MIDI event must match the event the fader is programmed for, and must be input at the specified MIDI input - I1 (Input 1) or I2 (Input 2) - both inputs can't work simultaneously in this mode.

• When a MIDI event arrives at one of the inputs, REGELWERK scans to see if any of the faders is programmed to the MIDI mode.
• Even with just one MIDI event input, all 24 faders are scanned (momentarily for Note- On /Off, and Controller Events).
• Scanning begins at fader 1 and proceeds towards fader 24. If a match is found, the relevant MIDI message is sent to that fader, and the scan stops. In the current version of software, therefore, you can't send the one message to several different faders at once.

• Bearing the scanning system in mind, it's best (fastest) to use the faders as close as possible to the left-hand side (low numbers) for receiving data – and definitely worth avoiding sending irrelevant data which doesn't match any of the faders' settings. In this worst case scenario, all 24 faders will be abortively scanned – a serious and un-necessary drain on processing ability.

• Generally, the following algorithm shows the logical path from left to right:

• from input I (1/2) (from MIDI In1 or 2)
• via data processing
• to destination O(1)(2) (to MIDI Out 1 and/or 2).

FaderEvent>O(1)(2)

• Normal fader mode, with data output on MIDI Out 1, 2 or both.

n.b. The following modes' status can be accessed by moving the alpha dial clockwise from Fader Event mode, not by pressing the Fader Parameter button again.

I1/2> VelOvpOne> O(1)(2)

• Velocity Overdub (one fader)
  A MIDI Event input at a MIDI overwrites its velocity (MIDI data byte 2) on the first fader event which matches it.
  This new value is output instead of the original (fader) value from the selected MIDI Out socket/s.

I1/2> VelOvpAll> O(1)(2)

• Velocity Overdub All
  the same as ‘one’ (see above) except that MIDI data byte 1 is ignored, so that the velocity message affects all 128 possible events of this type on this MIDI channel.

I1/2>VelMulOne>O(1)(2)

I1/2>VelMulAll>O(1)(2)

• Velocity Multiply One/All
  Like Overdub (see above), except that the old velocity value isn't overwritten Instead the fader velocity value and new MIDI value are 'multiplied' together – they interact.

I1/2> UpdateFad> O(1)(2)

• The actual fader value can be changed by remote control – used for the Regelwerk's version of Total Recall, etc.

I1/2> HookOnFad> O(1)(2)

• Hook Mode: If this mode is activated (as shown in the Special Funct. menu) any fader set to it doesn't send any data out at all, until a matching MIDI event present at a MIDI In hits its actual value.
  
• (The threshold for this 'hook' can be set in Special Funct.) As soon as these criteria are met, the fader is released, and can send data. This is shown by fast blinking on the relevant LED.

I1/2> Ovdup/Fad> O(1)(2)

• Overdub Mode: This mode also needs to be set in the Special Funct. menu.

• Until this mode is cancelled, the output on this fader is taken over by the MIDI input assigned to it.
• As soon as the relevant fader is used to generate an event, it takes back control of what is sent to the MIDI output, and MIDI In data is ignored until this mode is reset.

The following modes are accessed by pressing the Fader Parameter button.

Master/Slave- Mode:

• Slider = Master: self-explanatory: this fader is working as a master fader.

• Slave/Master: fader no. X works as a slave to master fader no. X.

• The Master/Slave system works by multiplication. If the master value is 100%, the slave value is as it stands. If the master value is less than 100%, the value of the slave reduces proportionally.

Learn - Mode:

• The process of fader editing for each fader can be undertaken not just by hand, but also by MIDI events, chains or strings input at the relevant MIDI in socket. This is called Learn Mode.

• What happens is that MIDI data (events or strings) are simply stored in the relevant memory.

• Learn Mode has to be explicitly switched on and off.

• Event:
  Only the first MIDI event received is stored in the relevant memory location.

• Ev>Str:
  A succession of MIDI events is stored in the relevant memory location, until it's full (currently a maximum of about 30 bytes).

• Sx>Str:
  The same as Ev>Str, except that it will only recognise and store SysEx strings.

• For all three of the above sections in this menu, the OK LED blinks.
• By pressing OK, the cursor is able to be reset to the beginning of the string, so that in Learn mode only the required data is recorded – and it's not, e.g., added to the end of another string.

Key On Edit

• This is a sub-set of functions virtually identical to the ‘Fader Edit’ menu, except that these are related solely to Key On events.

MIDI channel:

MIDI Event: (n.b. not Meta Events)

First MIDI data byte

Second MIDI date byte

String:'
When a Key On event occurs, a switch signal is sent, which, depending on the setting in the Key Parameter menu, can either be momentary, or toggled (i.e. it stays in that state until the next switch).

• The condition of the LED for each button will act as a reliable indicator of the status of the button in all modes when there is a...
• Key On- Event: Before the button-press the LED is on, and after the button-press it's off, showing that the control is now in mute mode – that is, not sending any fader events at all.

Key Off Edit

• In principal identical to the Key On functions, except that the momentary switching produces a 'release' function, and the function of the toggle switching is reversed.

MIDI channel:

MIDI Event: (n.b. not Meta Events)

First MIDI data byte

Second MIDI data byte

String:
When a Key Off (i.e. Note Off) event occurs, a switch signal is sent, which, depending on the setting in the Key Parameter menu, can be either momentary, or toggled (i.e. it stays in that state until the next switch).

• The condition of the LED for each button willact as a reliable indicator of the status of the button in all modes when there is a...
• Key Off Event: Before the button-press the LED is off, and after the button-press it's on, showing that the control is now in un-mute mode – that is, sending fader events as normal.

Key Param.

MuteValue: (0..127 / Send NO Muteval)

DemuteValue: (0..127 / Send NO Demuteval)

SwitchM: Tog&Mute/Mom&Mute/Toggle / Momentary

• These three parameters control the behaviour of the relevant button and any functions triggered by it, in relation to programmed MIDI events (controlled via the Key On/Off Edit page).

• The main distinction is between Toggle (held till next button-press) and Momentary (on/off, like a keyboard key).
  
  Toggle = Each button-press alternately triggers Key On and/or Key Off functions. Releasing the button has no effect.
  Momentary = Pressing the button triggers Key On, and releasing it triggers Key Off.
  
• The Key On function is only closely linked to the switching on of Mute status in the Modes '&Mute'.
  
  Then, if the associated LED goes out, and the relevant fader automatically sends a final Fader Event, not with the fader position, but with the Mute value (or with nothing at all if No Mute Value has been programmed).
  From that moment, the fader is muted, and won't transmit any more fader events until the mute status is changed.

• The Key Off function is only closely linked to the switching off of Mute status in the Modes '&Mute'.
  
  Then the associated LED comes on, and the relevant fader automatically sends a fader event, not with the fader position, but with the Demute value (or with nothing at all if No Demute Value has been programmed).
  From that moment, the fader is un-muted, and will transmit fader events as normal until the mute status is changed.

• Through the Key On and Key Off functions, the MIDI events programmed in Key On Edit and Key Off Edit modes are also transmitted.
• By pressing and/or releasing a button, it's possible, if you've configured it like this, to send a maximum of two complete MIDI events.
• One is transmitted by the relevant fader with a pre-programmed (De-)Mute value.
• The other Event is directly associated with the Key On / Off function.

FaderMode

• In fader mode the display turns into a sort of mini-MIDI monitor, indicating in words or abbreviations the MIDI events associated with the relvant fader, or transmitted by it.

• Data is shown as follows. On the top line of the display: fader name, then the actual fader position in brackets, then the variable value:-

faderXXX[Pos]Val
Contrl , 1 ,Val

• And on the bottom line (see above):-
• programmed MIDI Event, then the first MIDI data byte, then the second MIDI data byte.
• Pressing a fader select button causes the current reading/s of the fader to be called up in the LCD, and the actual value to be transmitted.

• Faders can also be selected by using the alpha-dial.

Special Functions

HookMode:Off/On

• All faders which are programmed in hook mode are indicated by the 'fader select' LEDs – the top row of LEDs.

• The OK LED blinks when hook mode is entered.

• Pressing the OK button confirms hook mode. When it is no longer required, it has to be turned off with the HookMode:Off function.

Threshold:

• Threshold value for hook mode.

Overdup: Off/On

• Same system as for hook mode, but this time for overdub mode.

MIDILock: Off / In1 / In2 / In12

• To relieve the REGELWERK of unnecessary processing of MIDI information that isn't relevant to it, it's possible to switch the MIDI inputs on and off independently.

• MIDI real-time data will be received and processed. All other MIDI events present at the inputs will be ignored.

• That means, for instance, that it's possible to synchronise the REGELWERK sequencer to an external MIDI clock, without burdening the REGELWERK's processor with all the other MIDI data on this channel.

Sample/Sek.: 24 - 8

• This is where the scanning / sample-per-second rate for the faders can be altered.

• The rate applies globally, to all faders.

• There could theoretically be a maximum of 24 x 24 fader events per second -> 576 fader events (and if each had three bytes, that would approach 50% of the maximum possible MIDI data flow rate).

• Because of frequent difficulties in the past with MIDI instruments which couldn't cope with the highest theoretically possible speeds of MIDI data transmission, it was decided to limit the maximum resolution to these amounts, and to allow a lower sample rate to be chosen if necessary.

String Edit

• If a fader hasn't been specifically labelled by the user, the software automatically calls it FADERXXX (where XXX stands for the number of the fader).

• The advantage of this: no hassle having to label a fader, and no need to use up memory for a name when saving the preset.

• The disadvantage: just by looking, it's impossible to tell what the fader is programmed to do.

• So it's also possible to enter a user-chosen label for each fader (in current software, up to eight letters long).

When no name has been given to a fader, this default message comes up in the LCD:

faderXXXEditName
NoName! Make?> OK

• Now to label a fader, the default mode must be switched off by responding to the question

NoName Make?> OK ,

• and giving the anonymous fader a label.

• Once you press OK to confirm this question, you automatically leave the page, and have to re-enter it.

Then the LCD shows:

ABCDEFG EditName
ABCDEFG Delete?

• ABCDEFG is the default name, which can now be edited with the aid of the cursor keys and alpha dial.

• Should you ever want to return to the default name (for instance to save memory), you need to confirm

‘Delete?’

• by pressing OK, and thus deleting the user name once more.

Also in this menu, it's possible to enter a string which is transmitted if any of the following events occur:-

EditString:Pres

EditString:Start

EditString:Stop

EditString:Cont

EditString:Rew.

EditString:Forw.

• a preset is called up
• the Start button is pressed (or a real-time start message is received)
• the Stop button is pressed (or a real-time stop message is received)
• the Cont button is pressed (or a real-time continue message is received)
• the <<- rewind button is pressed
• the ->> fast forward button is pressed

• These settings are available for each of the presets, and are ideal for, e.g., MMC (MIDI machine control).

Edit Tools

• For the time being, a fairly limited 'copy and paste' type of editing is all that's available .

Copy: Event type x from source fader a
to Event type x at destination fader b

Types of event can be:

• FaderEvt, - Fader Event
• KeyOnEvt, - Key On Event
• KeyOffEvt, - Key Off Event
• FaderStr, - Fader String
• KeyOnStr, - Key On String
• KeyOffstr - Key Off String
  
  
• Using the alpha dial you can scroll through all the possible combinations of compatible source and destination event types.

• Using the fader select buttons 1-24, choose the respective source and destination faders.

• The data entry point always swaps between source and destination faders.

SnapTools

GetSnapShot:

StoreSnap:

DeleteSnap:

• Select the preset number by using either the alpha-dial or a combination of the eight top left hand buttons (labelled Preset/Snap Bank / Pattern Bank) and the 16 right-hand top buttons. To select, e.g., snapshot 17, press Bank 2,
  number 1.
  
• A maximum of 128 snapshots are available.

• Snapshots, like Event Strings, are stored in a dynamically managed memory location.
• That means that the maximum number of snapshots available does depend on how much space is left in this location.
• The amount of memory used up is shown by a percentage readout.

PresSnapMem: XXX%

• If there's not enough space left, memory can be re-used by using the individual delete function.

Preset / Pattern Tools

• To select the 64 Presets & 64 Patterns you use the same 8 bank buttons as for the snapshots, again in combination with the 16 Preset/ Pattern buttons. The first four bank buttons are for presets, and the second four for patterns.
  
• All the functions work in an identical way to the snapshot functions.
  
• 64 Presets / 64 Patterns (all fully compatible with the Doepfer Schaltwerk).
  
• Select as with snapshots (Preset/Pattern Bank), using the GetPreset page

GetPreset / Pattern:

StorePreset / Pattern:

• Presets / Patterns accessed by the GetPreset function are (unlike in the SCHALTWERK) not automatically sync-ed to a master track.

• The time it takes to access a preset from memory depends, among other things, on how full the dynamic memory is.

• It's normally better to stop any ongoing sequence to load a new preset. It's quicker, and because of the lack of synchronisation, there's no advantage in having the sequence running. Stopping it avoids any chance of problems with notes hanging, etc.

SysEx Preset / Pattern:

• Transmit a preset / pattern via SysEx.
• The SysEx format of REGELWERK patterns is compatible with the Doepfer SCHALTWERK.
• A SCHALTWERK connected via MIDI could therefore read REGELWERK patterns, and store them in its memory locations and re-transmit them to the REGELWERK.

• REGELWERK SysEx strings are in two sections.

• The first block contains all the static parameters – the fader events and parameters for all the 24 faders and buttons. (This block is the same size as a pattern memory.)
• The second block, which is of variable length, contains all the dynamicly variable data in a preset – the faders themselves, key strings, and user-defined fader names / labels.

• REGELWERK reacts automatically to any SysEx string received.

• When receiving the dynamically variable part of the SysEx string, it is possible that an error message will be generated, if the available storage space in the dynamic memory location isn't sufficient for the amount of data being transmitted.

• In this case, enough memory must be freed up in this section (by deleting old and unwanted strings and snapshots) and the SysEx transmission then repeated.

• In the ‘Delete Preset’ function, the actual preset itself isn't deleted first time round: just the dynamic memory containing the string, name, etc.. If there's still not enough space, then the rest of the memory for this preset can be cleared.

• The Preset itself remains intact.

InitPreset?<OK>

InitPattern?<OK>

• Use this function to set the preset or pattern in the edit buffer to its default values.

• The individual presets / patterns remain intact.

Sync Menu

• In general, REGELWERK's tempo is controlled by its own internal clock:-

SYNC- INTERN / EXT.
Mode: Intern

• REGELWERK can also be controlled by an external MIDI Clock at MIDI input socket 1

Mode: Ext. MCL1

• or at MIDI input socket 2:

Mode: Ext. MCL2

• or by an external DIN sync signal:-

Mode: Din Sync

• received at the DIN sync socket.

In internal sync mode, the REGELWERK sends Realtime MIDI Messages:

• Start ($FA),
• Continue ($FB) ,
• Stop ($FC) , and also
• MIDIClock ($F8)

from both MIDI output sockets.

• At the DIN sync socket, a synchronised square-wave signal is transmitted.

• In external MIDI sync modes, the REGELWERK tempo is controlled by MIDI Realtime Messages at MIDI In 1 and / or MIDI In 2.
• At the DIN sync socket, a synchronised square-wave signal is again transmitted.

• In external DIN Sync Mode the DIN sync socket turns into an input, and the REGELWERK is controlled by any square-wave signal or start / stop messages received at the socket.

• Further sync parameters can be altered when using MIDI clock sync, to change the response of the REGELWERK to Continue commands.

• Setting the mode to the following:-

Mode: Start; Cont

• makes REGELWERK tracks reset to the first step after a Start message (or in normal cycling mode)
• A Continue message starts the sequence from the last step reached.

• Setting the mode to the following:-

Mode: Start = Cont

• means that all tracks will start afresh from step one, whether a Start or a Continue message is received.
  
• As standard, MIDI Realtime messages are transmitted from both MIDI Out 1 and MIDI Out 2. There may be some MIDI configurations, though, where this could be undesirable, or cause problems.

• 
  Accordingly, REGELWERK gives you the option of sending Realtime Messages just from one or other of the MIDI Outs, or from neither.

Mode: Mcl1

• sends Realtime Messages out only from MIDI Out 1;

Mode: Mcl2

• sends only from MIDI Out 2;

Mcl1 & Mcl2

• sends from both MIDI Outs (the default setting at power-up);

No Mcl-Out

• sends no Realtime Messages from either of the two MIDI Outs.

• All Sync Menu settings are only stored in volatile memory, so will be lost when power is switched off, and will need to be re-entered if required on power-up.

Sequencer Parameters

• Editing Track Parameters :

MIDI Channel,

Note Number,

Step Time

Gate Time

End Step.

• A Track is chosen for editing by pressing one of the Track Select buttons.
• Tracks are turned on and off with the Track On buttons.
• Gate On / Off is controlled by the Sequencer Step buttons.

• The MIDI Channel page is used to select the MIDI channel for each track.
• The Note Number page defines a note offset for the track as a whole, adding the programmed number of semi-tones to all the notes of a track. This is always a positive offest – negative offsets aren't possible.

• The Step Time page sets the number of MIDI clocks or DIN sync pulses between each event in the track. The result is whole-number division of MIDI clock and / or the internal tempo.
• The Gate Time page enables you to adjust the relative length of the notes (and spaces, of course).

• Gate Time is the time between identical repeated events – like two Note Ons.

• Step Time is shown in the display like this:-:

Step Time:006 = 1/16

• The '006' means that 6 MIDI Clock pulses must elapse before the next event is produced, and / or a track moves to the next step.
• The reference to the musical terminology '1/16' stems from the fact that, as there are 96 MIDI clocks in a beat, each clock is 1/96. Six clocks are therefore 1/16 (6/96).
• The End Step page is used to select the last step in a track. After reaching this step, the track jumps back ('resets') to the first step in the track and continues playing from there.

Sequencer Mode

• A Track is chosen for editing by pressing one of the Track Select buttons.
• Tracks are turned on and off with the Track On buttons.
• Gate On / Off is controlled by the Sequencer Step buttons.

• In addition faders 9 - 24 are dedicated to steps 1 - 16, and are used to set note number and note velocity.
• In Sequencer Mode, the normal Fader Mode output from faders 9-24 is switched off, and only faders 1-8 retain their usual fader mode function.

• Which function is being dealt with can be seen from the LCD, and is switchable from one function to the other by the menu buttons.

• In Sequencer Mode, the sixteen dedicated faders (9-24) behave like the sliders or knobs on a quantised analogue sequencer.

• That is, once the fader is moved, the respective parameter will immediately jump to the value (note number or velocity) the fader is outputting .

• That means that editing with a fader is 'destructive': the old value can no longer be recalled once a fader has been moved. As soon as a new fader position registers, the old value is over-written.
• The old value remains intact, so long as it is not deliberately over-written, and if you want to make a small adjustment to it, relative to its current position, select it with its respective gate button and adjust it using the alpha dial.
• Which of the eight Tracks' data is being adjusted is controlled by the Track Select buttons.

back to overview

FAQ's