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

2: Receptor Architecture 28 Receptor Manual
IMPORTANT: Notice that Single patches store the patch data used for each plugin. This way, if you ever
delete, rename, modify, or move a .fxp that was used to create the Single patch, you have no need to worry
-- your Single patches will always sound exactly as they did when saved, regardless of what you do to the .fxp
patches that were used to create the Single patch originally. So, even though Single patches always attempt to
display the name of the .fxp files used to create them, keep in mind that the patch data saved with the Single
may not be the same as the data saved in the named .fxp file -- again, this is to protect your Single patches from
inadvertently changing if you change a .fxp that was used in its creation.
You can think of a Single patch as a sort of “super-instrument,’ since it contains not only an audio source,
but also its insert effects. One of the wonderful things about Single patches is that, by recalling one, you
automatically instantiate every plugin required by that patch.
Multi Patches
Multi patches store an entire Mixer setup, including all Source and FX assignments, patch data, mix parameters,
output routings, and the following Setup parameters:
•
Master Transpose
• Tempo Source
• Tempo BPM
• Time Signature
NOTE: Setup mode parameters are discussed fully in “SETUP Button” on page 59.
You can think of Multi patches as “snapshots” of your entire Receptor mixer, which makes them quite 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.
IMPORTANT: Notice that Multi patches store the patch data used for each plugin. This way, if you ever delete,
rename, modify, or move a .fxp that was used to create the Multi patch, you have no need to worry -- your Multi
patches will always sound exactly as they did when saved, regardless of what you do to the .fxp patches that
were used to create the Multi patch originally. So, even though Multi patches attempt to display the name of the
.fxp files used to create them, keep in mind that the patch data saved with the Multi may not be the same as the
data saved in the named .fxp file -- again, this is to protect your Multi patches from inadvertently changing if
you change a .fxp that was used in its creation.