Document:Synergy MIDI Tracker - FaderPort 8/16
Author:bsp
Date:31-Dec-2021

1 Table of Contents

2 PreSonus FaderPort 8/16 support

2.1 Features

2.2 Setup

The FaderPort input and output devices must be enabled and their aliases (Devs page) must be set to FaderPort.
The Channel Profiles must be set to PreSonus FaderPort.
On the Prefs page Misc tab, select your FaderPort Model (8 or 16).
The Detail-Edit Precision setting determines the fader range in detail-edit mode. The highest precision has the lowest range.
Save the configuration, then restart the application.
tip_s
the auto-loaded default / example project in the Synergy release should work with a FaderPort 16 out-of-the-box

2.3 FaderPort controls

HW ButtonDescription
SelectSwitch to Bank 1..16 (A…P)
touch fader + SelectToggle label marker (invert last line)
Shift + SelectToggle fader lock
MHold for fader detail-edit mode (up to 14bit)
SReset fader to center, max, or min position (0x2000 / 8192, 0x3FFF / 16383, 0)
ARMSave temporary bank fader states
Shift + ARMSwap current / temporary bank fader states
Solo ClearUndo last fader change
Mute ClearQuery labels from Eureka ModMatrix (VST) parameter names, or MIDI synth profile
BypassUpdate current bank faders from output state (all scene groups)
MacroResend all current bank faders via MIDI Morph Scene
LinkToggle fader lock (all current bank faders)
ShiftTemporarily display bank names (A..P)
FaderPort HW buttons
The remaining (right-hand side) buttons and the two encoders can be mapped on the MIDIMap pages (global and context sensitive).
The following HW control mappings can be assigned on the MIDIMap(g) and MIDIMap(c) pages:
HW ButtonMap TargetDescription
EncPan ClickGLOBAL_YESClick focused UI button
EncNav ClickGLOBAL_YESClick focused UI button
PrevGLOBAL_PAGE_PREVGo to previous page
LatchGLOBAL_SCENE_F_1Select scene F1
OffGLOBAL_SCENE_F_2Select scene F2
Enc#2 NavGLOBAL_FOCUS_DELTACycle UI widget keyboard focus
Enc#1 PanGLOBAL_VALUE_DELTAEdit focused UI widget (inc/dec)
TouchNAV_NODE_PREVEdit previous node
ReadNAV_NODE_NEXTEdit next node
TrimNAV_PIPE_PREVEdit last-selected node of previous pipe
WriteNAV_PIPE_NEXTEdit last-selected node of next pipe
PlayTRANSPORT_PLAYStart / Stop replay
StopTRANSPORT_STOPStop replay
LoopTRANSPORT_CYCLEToggle song loop (cycle)
RewindTRANSPORT_MARKER_PREVGo to previous song marker
ForwardTRANSPORT_MARKER_NEXTGo to next song marker
ClickTOGGLE_METRONOMEToggle metronome click
FaderPort Global HW buttons MIDIMap
HW ButtonMap TargetDescription
Enc#2 NavCURSOR_TRACK_CTL_DELTACycle through track controller envelopes
FaderPort Tracker node HW buttons MIDIMap

2.4 FaderPort MIDI events

The faders send NRPN MIDI events #1..#256 (grouped in 16 banks).

2.5 FaderPort MIDI Morph Scene

When selecting a scene that references one or many fader NRPN events, the corresponding fader(s) will be restored to the last seen value(s).
Vice versa, moving a fader will transform the fader NRPN to the matching scene entry's target port and type.

2.5.1 Resending events

Pressing the Macro key resends the scene-transformed output events for the currently selected bank.
tip_s
this can be useful when switching between alternative FaderPort scenes or when recording multiple events to a sequencer step

2.5.2 Example scenes

Two example scene setups (.mms files) are included in the release:

2.5.2.1 faderport16

BankDescription
AControls currently selected Eureka track and currently edited sequencer node.
BControls vst_a channel 1 performance controllers and RPN 100..107 (Ctl1..Ctl8) (default Eureka ModMatrix source events)
CControls vst_a channel 2 performance controllers and RPN 100..107 (Ctl1..Ctl8) (default Eureka ModMatrix source events)
DControls vst_b channel 1 performance controllers and RPN 100..107 (Ctl1..Ctl8) (default Eureka ModMatrix source events)
EControls vst_b channel 2 performance controllers and RPN 100..107 (Ctl1..Ctl8) (default Eureka ModMatrix source events)
FControls vst_c channel 1 performance controllers and RPN 100..107 (Ctl1..Ctl8) (default Eureka ModMatrix source events)
GControls vst_c channel 2 performance controllers and RPN 100..107 (Ctl1..Ctl8) (default Eureka ModMatrix source events)
HControls vst_d channel 1..4 pitchbend+modwheel+ RPN 100+101 (Ctl1+Ctl2) (default Eureka ModMatrix source events)
IControls vst_d channel 5..8 pitchbend+modwheel+ RPN 100+101 (Ctl1+Ctl2) (default Eureka ModMatrix source events)
JControls vst_d channel 1..8 pitchbend+modwheel
KControls Analog Rytm performance controllers 1..12
L-
M-
N-
O-
PControls <autodev_a> RPN 100..107 (Ctl1..Ctl8) (context sensitive, redirected to current node automation port A)
faderport16 .mms preset scene banks (8 hi-res RPN controls)

2.5.2.2 faderport16_14c

BankDescription
AControls currently selected Eureka track and currently edited sequencer node.
BControls vst_a channel 1 pitchbend+modwheel and RPN 100..113 (Ctl1..Ctl14) (default Eureka ModMatrix source events)
CControls vst_a channel 2 pitchbend+modwheel and RPN 100..113 (Ctl1..Ctl14) (default Eureka ModMatrix source events)
DControls vst_b channel 1 pitchbend+modwheel and RPN 100..113 (Ctl1..Ctl14) (default Eureka ModMatrix source events)
EControls vst_b channel 2 pitchbend+modwheel and RPN 100..113 (Ctl1..Ctl14) (default Eureka ModMatrix source events)
FControls vst_c channel 1 pitchbend+modwheel and RPN 100..113 (Ctl1..Ctl14) (default Eureka ModMatrix source events)
GControls vst_c channel 2 pitchbend+modwheel and RPN 100..113 (Ctl1..Ctl14) (default Eureka ModMatrix source events)
HControls vst_d channel 1..4 pitchbend+modwheel+ RPN 100+101 (Ctl1+Ctl2) (default Eureka ModMatrix source events)
IControls vst_d channel 5..8 pitchbend+modwheel+ RPN 100+101 (Ctl1+Ctl2) (default Eureka ModMatrix source events)
JControls vst_d channel 1..8 pitchbend+modwheel
KControls Analog Rytm performance controllers 1..12
L-
M-
N-
O-
PControls <autodev_a> RPN 100..107 (Ctl1..Ctl8) (context sensitive, redirected to current node automation port A)
faderport16_14c .mms preset scene banks (14 hi-res RPN controls)
tip_l
press F12 to add a Eureka ModMatrix entry for the last touched VST editor widget (RPN 100..113).
tip_l
the <autodev_a> and <autodev_b> (virtual) MIDI devices will be translated to the actual automation port A / B device when a node editor is visible. The behaviour is node-type dependent: In the Tracker editor, RPNs 100..115 (Ctl1..Ctl16) will be mapped to the current instrument's usrctls 1..16. In the Modular editor, the RPNs will be mapped to "autorpnslider" modules. In the CtlMorph editor, they will be mapped to the first 16 entry center values of the current group. All remaining RPNs (as defined in midi_synth_profiles/internal.msp) will be used as-is (e.g. morph positions, step probabilities, ..).
The example scenes can be loaded via the Load Scene tools menu option on the Scene page (or by pressing lctrl-l).

2.6 Manual label editing

To change a fader label, edit the MIDI morph scene, select an entry and either press F2 or right-click on the Label column.
Labels that begin with * will automatically be marked (last line will be inverted).
Labels that end with the string _PB will cause the fader to be locked to the center position (pitchbend mode).
When a label contains the , character, it will be force-split into multiple lines.
tip_s
manually editing a label sets its base caption which the label will revert to if it is not currently assigned an automatic caption

2.7 Automatic label queries

2.7.1 Eureka ModMatrix (VST)

Labels can be auto-assigned the names of the (VST) parameters the corresponding fader currently controls.
note_s
This is done by querying the Eureka ModMatrix entries and finding those that correspond to the MIDI morph scene entry port and type (target event), and the fader (source event FaderPort device NRPNs 1..256).
Either go to the Scene page, (multi-)select the entries that shall be updated, then press lctrl-f (or choose Query Eureka ModMatrix Labels from the Tools menu), or simply press the Mute Clear button on the FaderPort to update the labels for all faders.

2.7.2 MIDI Synth Profile Import (HW)

This works similar to VST label queries with the difference that the labels are determined by MIDI Synth Profile controller aliases.
Go to the Scene page, move the cursor to an entry that matches the desired output device+channel (this is used to determine the MIDI synth profile), then press lshift-f (or choose Import From MIDI Synth Profile.. from the Tools menu).
note_s
the imported aliases / scene entries will be auto-adjusted (remapped) to their actual parameter ranges

2.7.2.1 Replace mode

When one or more scene entries are selected (not counting the table cursor row), the selected target event's device / channel / type will be replaced by the imported MIDI synth profile controller aliases.

2.7.2.2 Add mode (FaderPort)

When no scene entries are selected, and the table cursor row source event device is FaderPort, the imported MIDI synth profile controller aliases will be added to the scene.
When the table cursor row source event type is NRPN, it determines the fader bank and fader offset for the imported entries.
If the type is not NRPN, the imported entries start at the first fader of the first bank (A1).
Up to 16*16=256 MIDI Synth Profile aliases can be imported / auto-assigned to the faders (banks A..P).

2.8 Context-sensitive fader editing

Faders that have been assigned the (virtual) target device <editfocus> and target type RPN 100..131 (Ctl 1 .. Ctl 32) on the Scene page can be used as bidirectional, context-sensitive editing controls.
important_s
make sure that one of the internal, virtual MIDI devices is assigned the alias <editfocus> (see Devs page)
alt
FaderPort Scene configuration example

2.8.1 Modular Node

<editfocus> faders will be assigned the parameters of the currently selected (keyboard-focused) module.
This is especially useful with the CVSeq16, TrigSeq16, and Voltage Memory modules: The faders can be used for editing the sequence steps, similar to a hardware sequencer like the ARP 1601.
The (big) navigation encoder should be mapped to the GLOBAL_FOCUS_DELTA target in the global MIDIMap context (see above) so it can be used to cycle through the modules.
The fader labels will display the current module parameter names.

2.8.2 Tracker Node

<editfocus> faders will be assigned the step values of the first 16 events of the currently selected pattern column.
The (big) navigation encoder should be mapped to the CURSOR_TRACK_CTL_DELTA target in the Tracker node MIDIMap context (see above) so it can be used to cycle through the track envelopes.
The fader labels will display the current envelope (short) name, and event positions (sixteenth note offsets).
important_s
keep in mind that the first 16 events will be displayed, not the first 16 steps, i.e. the faders are used for editing existing events, regardless of the actual pattern length.

Valid HTML 4.01 Transitional

Document created on 24-Jun-2022 14:25:26