Installing “unsupported” plugins – Muse Research Receptor manual v1.2 User Manual

Page 172

Advertising
background image

13: Receptor File Management

172

Receptor Manual

Installing “Unsupported” Plugins

1

Locate the desired .dll plugin file on your Windows PC.
If this is a plugin that you’ve already installed on your Windows PC, you can usually find the .dll file (which is the
actual plugin) in your Vstplugins folder on that machine.
IMPORTANT: Receptor does not run Windows installers. If you want to try running a Windows plugin on Receptor and
that plugin comes as part of an installer, then you must first install the plugin on a Windows machine, then navigate to
its Vstplugins directory to find the .dll file for the desired plugin.

2

Mount Receptor on your computer.
See “Mounting Receptor on your Computer’s Desktop” on page 149 for more information.

3 Drag the desired .dll file from your PC into Receptor’s hard drive.

Specifically, you must drag the .dll file into this exact location on your Receptor:
Program Files / VST Plugins / Unsupported Plugins
You can set up your own hierarchical file structure within this directory.
IMPORTANT: Muse Research strongly recommends that you never try to install more than one plugin at a time using
this method.

4 Click the SETUP tab in Receptor’s graphical user interface,

5 In the INSTALL section of the SETUP tab, check the option called

Include Unsupported Plugins folder.

This tells the Install button to look inside the Unsupported Plugins directory and try to install those .dll’s into Receptor,
as well as any official Receptor plugins that may be in the Drop Installers Here directory.

6 Click the

Install <n> files button.

Where “<n>” is the number of new files Receptor finds and will attempt to install.
Receptor will install the files and attempt to instantiate any plugins in the background.

The following are the possible outcomes:

Receptor indicates that all the files installed and no dialog boxes appear on screen. This means your plugin
installed and instantiated. You should now test the plugin by switching to the MIX view and instantiating
it. If it’s a VSTi, you do this from the Channel Source Selector. If it’s an effect, you do this from a Channel
FX Selector (after assigning a Source to a channel). If everything works, congratulations! If the plugin
doesn’t work properly or fails to instantiate, you should uninstall the .dll as discussed in “Uninstalling
“Unsupported” Plugins” on page 173.

A dialog box appears on screen. Some commercial plugins may produce a dialog box requesting a serial
number. If this is the case, you may be able to type in your serial number and the plugin will then work
correctly. Other commercial plugins may use a more complicated challenge/response form of copy
protection. It may be possible to use another computer (one that’s connected to the internet) to transfer the
challenge code to the developer’s web site and, upon receiving a response code, type that into the dialog
box that appears on Receptor. After entering the requested information, you should then test the plugin by
switching to MIX view and instantiating it. If everything works, congratulations! If the plugin doesn’t work
properly or fails to instantiate, you should uninstall the .dll as discussed in “Uninstalling “Unsupported”
Plugins” on page 173.

Receptor indicates that the file failed to install. Plugins may fail to instantiate for any number of reasons,
such as missing support files or CD-based copy protection schemes. In this case you should uninstall the
.dll as discussed in “Uninstalling “Unsupported” Plugins” on page 173.

IMPORTANT: If Receptor crashes or fails to restart properly after you install an unsupported plugin, please
follow the instructions in the following section to uninstall the problem plugin.

Advertising