Muse Research Receptor manual v1.2 - Manual (Page 27)

2: Receptor Architecture 27 Receptor Manual
Master Channel
Receptor’s Master Bus channel has its own trio of 3 dedicated insert FX, which are perfect for applying
compression or limiting to an entire mix. As with the insert FX on the Instrument and Bus channels, these can
be arranged in any series/parallel combination and the output of the master bus can be routed to any hardware
output.
Patch Hierarchy
Receptor has an intelligent patch hierarchy that uses the following patch types:
•
VST (.fxp) Patches - each type of VST instrument or effect can store and recall patches in standard .fxp
format.
• Single Patches - Receptor allows you to store an entire Instrument channel (one Source and three FX
assignments plus their patches) as a “Single patch.” This is a quick way to recall commonly used “super
patches”, such as guitar processing patches that process the signal through all three insert effects, or
synthesizer patches that rely on VST FX processing (such as flangers or delays) to achieve a particular
sound.
• Multi Patches - Receptor can store an entire configuration (all 19 channels, their plugin assignments, and
their mix parameters) as a Multi patch. This is particularly useful for creating big “stacked” sounds that
combine multiple synthesizers, or for MIDI sequencing, where each instrument channel is controlled by a
different MIDI channel.
The following sections contain more information about each patch format and what, specifically, it stores.
VST (.fxp) Patches
Although many plugins have their own internal patch management interfaces, they also are designed to save and
load patches stored as VST standard .fxp patches.
Any time you instantiate a plugin, you will be able to select which .fxp patch you want to load into that plugin.
Unlike a computer-based plugin player, Receptor organizes these .fxp patches into MIDI-compatible banks and
patches.
IMPORTANT: To insure consistent operation of Receptor, always use Receptor’s patch management menus
and not any patch management facilities built into a specific plugin. The reason for this is that .fxp patches
are controlled from a host application level. Receptor manages your .fxp files in such a way that you may have
MIDI selectable banks and patches (just like a hardware synth). Receptor automatically extracts any patches
that are built in to a plugin and creates a factory bank for that plugin, so you never have to worry that you’re
“missing” some patches by using Receptor’s patch management tools.
Single Patches
Single patches store the configuration of a single Instrument Channel (as defined previously). This means that a
Single patch stores an instrument channel’s:
•
Source assignment
• Patch (.fxp) data loaded into that Source plugin
• All three Insert FX assignments
• Patch (.fxp) data loaded into each Insert FX plugin
• FX routing
Mix parameters such as Mute, Solo, Volume, and Send Level are not stored within a Single, since these
parameters are all dependent on the context in which you use the Single patch.
For this same reason, Single patches do not store the “Listen To MIDI Ch” setting (as discussed in “SOURCE:
Listen to MIDI Ch” on page 49). All these parameters are, however, saved as part of a Multi patch, which is
discussed in the next section.