Muse Research Receptor v1.7 Release Notes - Manual (Page 21)

Receptor v1.5 Release Notes 21 Muse Research, Inc.
Receptor v1.5 Release Notes
This section discusses the most significant of Receptor’s v1.5 improvements, new features, and bug fixes.
Features described in this section supersede any descriptions in your Receptor v1.2 owner’s manual or in
previous Release Notes.
New Feature: UniWire™
UniWire™ is a new way to connect one or more Receptors to a computer-based digital audio workstation using
only Ethernet cables—no audio or midi cables are needed. In addition, UniWire instrument and effects plugins
are installed on your host computer, which allow your digital audio workstation to communicate with Receptor
as if it were both a virtual instrument and a virtual effect plugins. This means that, unlike “old school” external
sound and effects modules, Receptor integrates with your digital audio workstation exactly like a locally hosted
plugin — but without using any of your host computer’s precious CPU cycles.
In addition, UniWire lets you use Receptor’s built-in MIDI and superb audio I/O circuitry as another ‘audio and
midi interface’ for your computer-based DAW.
UniWire is an extremely feature-rich and powerful new way to integrate Receptor into a digital audio
workstation and, as such, there are a number of new settings and new options sprinkled throughout Receptor’s
interface. These, and everything else about UniWire, are discussed fully in the stand-alone UniWire Manual
Supplement. All Receptor customers are encouraged to read that document and explore the power of UniWire in
their own recording, production, or performance environments.
New Feature: Snapshot Banks and Patches
Receptor has a new type of Multi Patch, called a Snapshot Patch. All related snapshot patches are saved
together in (you guessed it) a Snapshot Bank. Specifically, all Snapshot Patches within a Snapshot Bank share
the same plugin assignments and patch data, which are stored in a hidden ‘parent’ file. The only differences
between the snapshots in a Snapshot Bank are their mixer settings (volume, pan, mute, bypass, etc.).
Introduction
All Snapshot Patches within a Snapshot Bank use the plugin assignments and plugin parameters that are
stored in a common parent file. This is illustrated graphically on the next page, where plugin assignments and
parameter settings are indicated by the white blocks in the Parent file. The Mix parameters contained within
the Parent file are shown in gray because these parameters are actually provided by the Snapshot Patches. Each
Snapshot patch, as you can see, has gray plugin/patch assignments since these are provided by the Parent file
and not the snapshot.
There are several advantages to using snapshots rather than traditional Multi patches. The biggest is that you
can switch between snapshots very quickly without any interruption in the sound. Unlike a Multi patch, which
must instantiate every plugin (not previously Z-loaded), plus all the parameter data for each plugin, this data
is only loaded once and is re-used by all snapshots in the Snapshot Bank. This can be particularly useful when
you’re switching between patches that use different samples, since sample data can take a substantial amount of
time to load into RAM.