Blue Cat Audio on FacebookFollow Blue Cat Audio on TwitterFollow Blue Cat Audio on InstagramBlue Cat Audio's Official Youtube ChannelThe Blue Cat Audio ForumThe Blue Cat Audio Blog - The Dark Side of the Cat
Blue Cat Audio - Software Made by Musicians for Musicians
Blue Cat's PatchWork User Manual
Blue Cat's PatchWork User Manual
Blue Cat's PatchWork - Fully Configurable Plug-Ins Chainer and Multi FX / Standalone Host or Plug-In
"The virtual patchbay for audio plug-ins"
MacOSUniversal BinaryWindows Vista or newerWindows x64 (64-bit)VSTVST3AAX64-bit AAXAudio Unit


Blue Cat's PatchWork is a universal plug-ins patchbay and multi FX that can host up to 64 VST, VST3, Audio Unit or built-in plug-ins into any Digital Audio Workstation (DAW) in a single instance, with both serial and parallel routing options.

It is possible to chain effects in series or create up to 8 parallel chains that can be activated independently. This lets you create your favorite effects or instruments configurations within the plug-in, without the need for multiple busses. These configurations can be saved as presets and recalled instantly, or shared with multiple DAWs, using any plug-in format (full list below). Use the built-in audio effects to add color to your own plug-in chains.

Despite the name, you can forget about wires or cables: configuring plug-ins routing is as simple as adding or removing a row or a column in the rack's matrix. All plug-ins can also communicate with each other or with the host application using the virtual MIDI ports offered by the plug-in.

For each plug-in slot, latency compensation, presets management, undo/redo integration, audio i/o selection and individual plug-in bypass are included for optimal operation. The plug-in also stores the position of the window for each plug-in so that the layout is restored with your session or saved with presets.

Also, sub plug-ins can be automated or controlled with external control surfaces using Blue Cat's PatchWork parameters mapping capabilities.

This product is available as an audio plug-in (effect or a virtual instrument) and standalone application, so that it can used alone or inserted on any type of track in your favorite DAW, with up to 16 audio channels.

Input and output level meters are also available to monitor the signal that is dispatched to inserted plug-ins, including side chain and aux channels.

If you are looking for a multiband plug-ins host for multiband processing, check out the Blue Cat's MB-7 Mixer plug-in. Also, any Blue Cat Audio plug-in is compatible and can be hosted by this software.

Looking for more advanced audio routing within PatchWork? Check out Blue Cat's Connector!

Copyright Note: VST is a trademark of Steinberg Media Technologies GmbH.

Blue Cat's PatchWork - Now available as a standalone application for Mac and PC, it lets you quickly load and use your favorite virtual instruments and audio/MIDI effect plug-ins. Blue Cat's PatchWork - Inludes 25 top notch built-in audio effects: EQ, compressor, gate, ducker, flanger, phaser, delays... Blue Cat's PatchWork - Create your own channel strips with macro controls

Typical applications: Plug-ins host, custom channel strip, parallel processing, effects chainer, virtual bussing, virtual instrument, share bus and plug-ins configurations between DAWs, VST or Audio Unit to AAX, Audio Unit, effect chains A/B comparison, standalone audio processing application, multi effects processor.

System Requirements


  • An Intel or Apple Silicon processor.
  • Mac OS 10.9 or newer.
  • For the plug-in, any VST / Audio Unit / AAX compatible application (64-bit) .
  • For the standalone application, a Core Audio compatible audio interface.


  • An SSE2-enabled processor (Pentium 4 or newer).
  • Microsoft Windows Vista, Windows 7, 8 or 10.
  • For the plug-in, any VST / AAX compatible host software (32 or 64 bit).
  • For the standalone application, an ASIO, MME or WASAPI compatible audio interface (ASIO recommended).

For more information about supported platforms, see our Knowledge Base.

Demo Limitations:

  • 5 instances of the plug-in allowed per session.
  • The effect is bypassed for half a second every minute.


The standalone version does not require any host application and can be run without requiring any third party application.

The plug-ins versions cannot be run standalone: they require a host application (see the System Requirements chapter for more information). Depending on which host application you use, you might need to install the plug-ins in different locations.

Before installing one of the plug-in versions, you should close all your host applications.



All versions of the plug-in provide an installation program. Follow the steps of the wizard to install the software on your machine. During the installation you will be asked where you want the software to be installed. For the VST version, you should install the plug-in inside the VST plug-ins folder used by your host application(s). The default path set in the installer should work for most applications, but you should check your host software documentation to know where it looks for VST plug-ins. For other plug-in types, you should just use the standard path.

Some applications will not automatically rescan the new plug-ins, so you might have to force a refresh of the plug-ins list.


When a new version of the software is released, just launch the new installer: it will update the current installation.


To uninstall the software, simply launch the "Uninstall" program that is available in the start menu or in the configuration panel. It will take care of removing all files from your computer.



On Mac the plug-ins are available as drive images with an installer. After download, double click on the dmg file to open it. You can then double click on the installer (.pkg file) to install the package.

Note for Mac OS 10.15 Catalina or newer: you may have to right click on the installer and select "Open" instead of double clicking on the file to launch the installation if your computer is not connected to the Internet.


When a new version of the software is released, just launch the new installer: it will update the current installation.


To uninstall the software, simply remove the component(s) from their install location (move them to the trash):

  • Standalone applications are installed in the /Applications folder
  • AAX plug-ins are installed in the /Library/Application Support/Avid/Audio/Plug-Ins/ folder
  • Audio Units (AU) are installed in the /Library/Audio/Plug-Ins/Components/ folder
  • RTAS Plug-ins are installed in the /Library/Application Support/Digidesign/Plug-Ins/ folder
  • VST plug-ins are installed in the /Library/Audio/Plug-Ins/VST folder
  • VST3 plug-ins are installed in the /Library/Audio/Plug-Ins/VST3 folder

If you want to completely remove all settings and configuration files, you can also remove these additional directories that may have been created on your computer:

  • ~/Library/Preferences/Blue Cat Audio/[Plug-in name and TYPE], where TYPE is VST, AU, RTAS or AAX: global preferences.
  • ~/Library/Preferences/Blue Cat Audio/[Plug-in name]: license information
  • ~/Documents/Blue Cat Audio/[Plug-in name]: user data, such as presets, additional skins and user-created plug-in data.

Please be aware that these directories may contain user data that you have created. Remove these directories only if you do not want to reuse this data later.

First Launch

Standalone Application

Once the application has been installed, simply double click on its icon to launch it. On Mac, the application will be located in the 'Applications' folder if using the default install location. On Windows, you will find it in the start menu.

The first time you launch the application, it will ask you if you want to configure the audio interface:

It is recommended to configure the audio interface before using the application, but you can still do it later by clicking on the "Edit/Audio Setup" menu. This opens the Audio/MIDI Preferences window reproduced below:

If the default setup displayed in the panel does not correspond to your needs, you can do the following:

  • Choose the appropriate I/O configuration, if available.
  • On Windows, choose the type of audio driver (ASIO is recommended. If you do not have an ASIO driver, we recommend using the ASIO4All driver).
  • Choose the driver to use for audio input and audio output, if available (with ASIO, you can only choose a single driver for both).
  • Select the sample rate and buffer size. Increasing the size of the buffer uses less CPU but adds latency.
  • Select the audio inputs and outputs to use with the software.
  • You can also set the tempo and time signature if relevant.
  • Click on "Tap Tempo Setup" if you want to tap tempo with a MIDI controller.

Changes are applied to the application in real time and saved when closing the preferences window. You can see the status of the audio engine at the bottom of the window, as well as the estimated i/o latency (it depends on the sample rate, buffer settings and selected audio interface(s).

If the status of the engine is 'NOT Running', you may need to change the settings: try to increase the buffer size, change the sample rate (it might not be supported by the interface) or select another audio interface.

The MIDI In and MIDI Out panes let you select the MIDI devices to be used as input and ouput. You can either use them all, none, or select from a list:

Once the this has been setup, you can close the window and start using the application.

Standalone Application: Network Server

It is also possible to use the applications as a "slave" of another application that sends audio and MIDI with the Connector plug-in locally or over the network. To do this you should select the "Network Audio" driver type and "Connector Slave" driver.

Click on the button with 3 dots at the right of the driver name to access the connection settings (see the Connector Manual for more details):

Note: in this mode, the application will not process audio unless some data is sent to it by an instance of the connector plug-in loaded into an active audio application.

Audio Plug-Ins

Blue Cat Audio plug-ins cannot be run standalone, they require a host application (see the System Requirements chapter for more information). Some host applications will require you to scan the plug-ins before they are available in the application.

If the plug-in is not available in the application, please check that it has been installed in the appropriate directory (with no host application running), and that the host application has scanned it.

Using Blue Cat's PatchWork


Blue Cat's PatchWork is a simple yet powerful plug-ins rack: the main purpose of the plug-in is to host VST or Audio Unit (AU) plug-ins, with a fixed but flexible routing scheme.

Effect or Instrument

Two versions of the plug-in are included: audio effect or virtual instrument. They both offer similar capabilities (you can host instruments in the effect version for example), but they will be considered differently by your host application.

Also, the effect version includes an external side chain input, and the synth version offers multiple output busses (up to 16 audio channels).

Simply use the synth version if your main purpose is to host virtual instruments (or MIDI effects), and the effect version if you want to process the signal as an effect.

Note: the Audio Unit plug-in also includes a MIDI Effect (MFX) version, to be used for MIDI processing in Logic Pro X.

Signal Flow

The signal flow is the following:

  • At the input of the plug-in, the signal is split so that the original input signal can be mixed back with the processed signal, using the mix control.
  • It is then processed by the input gain stage and the active "PRE" plug-ins, in series.
  • It is then dispatched to the active parallel chains (each chain offers its own pre and post gain knobs).
  • After the parallel chains, the signals are summed (and compensated if "average" summing mode is selected) before going into the "POST" chain that processes the plug-ins in series.
  • The output gain is then applied before going into the mix stage that mixes the original input with the processed signal.

Note about the included level meters: the input levels are measured right after the "PRE" gain control, and the output levels right after the mix control.

Summing Mode

Starting with version 1.4, you can select the summing mode for parallel chains. With "average", the parallel chains are averaged, which compensates for potential gain increases. This is particluaraly useful when using the plug-in as an audio effect, to avoid gain increases when adding new parallel chains. However, when using the plug-in to mix multiple synths, you may want to choose "sum" instead, so that muting one of the chains does not impact the volume of other chains.

Multiple Channels Support

The plug-in supports audio streams in mono, stereo or multichannel (surround) formats (up to 8 channels). If you insert a plug-in that can process less channels, only the first channels will be processed, and others will be forwarded to the next plug-in, until it reaches the output of the PatchWork plug-in.

Exception for mono plug-ins: by default, mono plug-ins will process only the first audio channel, and the wet mono output will be copied to all other channels of the main bus (aux and side chain unaffected). If you want to only apply the plug-in to one of the incoming audio channels without modifying others instead, you can use manual audio I/O configuration as explained later in this manual.

External Side Chain and Aux Outputs

With the effect version, the plug-in also has additional side chain audio channels, and the synth version uses multiple aux audio outputs for additional external routing in the host application.

The meters for these extra channels are separated from "main bus" channels by a small dark area to make it easier to visualize the main and aux levels:

Stereo main output with 14 aux channels

All these extra channels follow the same signal flow as main audio channels, but are by default unaffected by both the plug-ins and level or phase reversal controls. As a result, by default:

  • External side chain input is distributed dry to all plug-ins with a side chain input.
  • Aux outputs from virtual instruments are routed the the PatchWork plug-in's aux outputs without being modified.

It is however possible to process or re-route the side chain or aux channels, using custom audio I/O routing for individual plug-ins, as explained later in the manual.

Multicore Processing

PatchWork includes a multicore processing engine that can spread parallel chains processing on separate processor cores. It lets you use all your processor cores at the same time and load more effects or instruments at the same time.

Note: effects that are processed in series (one after the other) cannot be parallelized and do not benefit from multicore processing. Only parallel chains can be processed independently.

The multicore engine can be activated or deactivated for each preset independently. When using very few plug-ins with low CPU usage in parallel, the cost of multicore processing can be higher than the benefits (you can check the CPU usage with the built-in CPU meter at the bottom right of the user interface).

Performance also depends on the host application and its own multicore processing strategy, so you may want to try and compare with or without multicore enabled.

Latency Compensation

If a plug-in inserted in a parallel chain reports latency (signal delay), the PatchWork plug-in will compensate the delay so that other parallel chains are in sync. Latency is also reported to the host application so that it can be compensated. However, some hosts may require that the plug-in is deactivated and re-activated before the new latency is taken into account (Cubase, Sonar and Studio One for example). Restarting transport may also be required (Pro Tools 10 and earlier for example).

When using plug-ins on a subset of available channels (when using side chain, aux outputs or individual plug-in i/o mapping), the latency is also compensated on unprocessed channels. This however happens only at the end of each processing chain (pre, parallel chains or post), so be careful if using audio i/o remapping intensively with plug-ins introducing latency.

Parameters Mapping & Macros

With Blue Cat's PatchWork, it is possible to map sub plug-ins parameters in order to control them with host automation, an external control surface, or simply within Blue Cat's PatchWork's user interface. Thanks to the included "learn mode", simply touching the knobs of your favorite plug-ins will let you assign parameters for external control (up to 40 controls are available).

Starting with version 2.6, it is possible to map several parameters to a single control and adjust the range of each parameter, to create macro controls that can adjust multiple parameters at once.

MIDI Preset Loading

Starting with v1.63, it is possible to load effects chains as presets using MIDI (with Bank Select and Program Change messages). More details about MIDI and presets loading is available in the presets section.

Phase Flip?

The plug-in includes a phase flip (also called phase reversal) button for each parallel processing chain. This lets you change the polarity of the signal if some plug-ins are causing phase reversal problems, or to simply compute the difference with other parallel signals.

Audio I/O Routing For Plug-Ins

For each audio plug-in, it is possible to choose the audio channels to use for both inputs and outputs. It is thus possible to apply effects to only a subset of audio channels (for multi-mono processing for example, or to apply effect to only an auxiliary channel). It is also possible to achieve complex routing within the effect chain (such as sending specific channels to the side chain input of a plug-in) and yet keep it simple.

Note: when using audio I/O routing intensively, it is recommended to change the names of the plug-ins according to the channels being processed:

Built-In Effects

Blue Cat's PatchWork includes 30 top quality built-in effects that can be used in plug-in slots, next to third party VST, VST3 or AU plug-ins:

Bit Crusher, Chorus, Comb Filters, Compressor, Ducker, Echo, Multitap Delay, EQ, Multimode Filter, Flanger, Frequency Shifter, Gain, Gate, Stereo Pan, Phase Shifter, Phaser, Pitch Shifter, Stereo Strip, Sweep Filter, Tremolo and Waveshaper and more.

PatchWork is also available as a built-in plug-in (in the Utility category), so that you can load it into itself and share the presets.

Built-in plug-ins offer the same preset management and control features as the main plug-in (MIDI learn, undo/redo, parameters range...). For more details about each effect and its controls, please refer to the included documentation ("?" icon in the toolbar of each plug-in).

The User Interface

Note: The main toolbar, menus and basic features available with all our plug-ins are detailed in the Blue Cat Audio Plug-ins Basics section.


The generic controls that can be found in all our plug-ins are not described in this chapter. More details for these are available in the next section.

The main components of the user Interface are listed below:

  1. Main toolbar.
  2. Input gain knob and (peak) level meter. When the lock next to the knob is active, the input gain is not modified when loading presets.
  3. PRE plug-ins slots: processed in series.
  4. PARALLEL plug-ins slots: parallel processing chains.
  5. POST plug-ins slots: processed in series.
  6. Output gain knob and (peak) level meter. When the lock next to the knob is active, the output gain is not modified when loading presets.
  7. Knobs for assigned parameters are displayed here (when mapping sub plug-ins parameters for automation).
  8. Enable/disable multicore processing for parallel chains.
  9. Real time workload meter that measures CPU load.

The Main Toolbar (1)

  1. Main bypass (to enable/disable the plug-in).
  2. Mix knob: select the amount of wet vs dry signal (mix the original input signal with the processed signal).
  3. Generic menu, controls settings, undo redo, help and plug-in info buttons. More details are available in the next section.
  4. Lock the user interface settings so that they are not affected when loading presets.
  5. Select the appropriate size for the plug-ins slots (small, medium, large).
  6. Display the preferences pane.
  7. Select the number of columns for the plug-ins matrix. With 2 columns or less, parallel processing slots are disabled.
  8. Select the number of rows for the plug-ins matrix. With a single row, no parallel processing is available.
  9. Show/hide the level meters.
  10. Assignable controls menu: show/hide assignable controls (macro params), open the params map editor, or select the style of assigned controls.
  11. Show/hide the plug-ins slots.
  12. Open all plug-ins editors.
  13. Close all plug-ins editors.
  14. Link pre and post gains (global and for each chain), so that pre-gain changes are compensated by the post gain (to drive level-dependent plug-ins without increasing the volume).

Parallel Processing Chains (4)

  1. activate the effects chain.
  2. pre-gain for the effects chain.
  3. plug-ins slots for the chain (processed in series).
  4. post-gain for the effects chain.
  5. phase flip for the chain (reverse the phase of the signal - 90 degrees phase shift).
  6. solo the chain: deactivates all other non-soloed parallel chains.
  7. exclusive solo mode: when active, solo buttons are mutually exclusive: only one chain can be soloed at a time.
  8. summing mode for parallel chains chain: "average" splits the signal and compensates the gain based on the number of active chains. "Sum" simply sums all active parrallel chains like busses on a console, with no gain compensation.

Workload Meter (9)

The workload meter on the bottom right of the user interface gives an idea of the amount of cpu used by the plug-in to process audio frames:

It measures the realtime workload, which corresponds to the time spent processing an audio buffer compared to its duration. This value may be impacted by other tasks running on the system.

In general the average value gives a good idea of the cpu usage of the plug-in, while the peak value is an indication of potential audio dropouts (if larger than 100% for too long), that may be caused by overall system load (not just the plug-in's audio processing).

The workload meter becomes orange then red when the peak load grows. Hover the mouse on the meter to see numerical values in a tooltip.

Browsing Presets

In order to browse both factory and user presets, you can either use the simple presets menu or open the full featured presets browser from the toolbar that remains visible until you close it:

Click on preset files and folders to open them, or use the arrows to navigate between displayed presets. You can navigate upward in the folders tree by clicking on the current folder at the top. Type in the search box to find presets by name (it also searches in folder names). The search is performed recursively in the currently selected folder (displayed at the top).

Search Tips: you can search for multiple terms by separating them with commas. Wildcards are also supported (with * and ? characters), but they are applied to the full path of the preset. For example, to search for all presets containing the word "phase", type *phase* in the search box. To look for these presets only in the factory presets, you can type Factory Presets/*phase*.

Using VST, VST3 or Audio Unit Plug-Ins

Note: before inserting VST plug-ins, it is strongly recommended that you setup your main VST plug-ins directory in the preferences pane, as detailed later in this manual (this setting does not affect VST3 plug-ins).

Warning: in a 64-bit application you can only load 64-bit plug-ins, and in a 32-bit application you can only load 32-bit plug-ins, unless your are using a third party bridging application.

Each plug-in slot lets you insert a plug-in. When clicking on an empty slot, the following menu appears:

The "Select" item is enabled if you have previously saved plug-ins as favorites using the "save as" command described below. It lets you choose a favorite plug-in directly from the menu, instead of having to load it from the file system.

Selecting "Load VST" will open a standard system window where you can select the VST plug-in you want to load. If the preferences have been properly set, the window should open the appropriate location where you can find the VST plug-ins.

Selecting "Load VST3" will open a standard system window where you can select the VST3 plug-in to be loaded.

On Mac, an additional "Load AU" menu item is available to load Audio Units. It opens a file open dialog in the standard location for Audio Units on your system. Note: if you want to load the system Audio Units provided by Apple, you will need to open the CoreAudio component located in the /System/Library directory (/System/Library/Components/CoreAudio.Component).

You can also choose to paste an existing VST, VST3 or AU plug-in if previously copied into the system clipboard from another slot. When using the "Paste with Map" command, if the plug-in in the source slot had mapped parameters, these parameters will be added to the map until no more assignable parameters are available.

Once a plug-in has been loaded into a slot, a mouse click will display the following plug-in menu that offers various controls over the plug-in:

  • Show (Hide) Editor: display or hide the plug-in's user interface.
  • Bypass: toggle bypass for the plug-in.
  • Presets: access the plug-in's factory presets if any, and load/save presets files in the plug-in's native format (fxb/fxp, vstpreset or aupreset).
  • Cut: copy the plug-in and its settings into the system clipboard and remove it from the slot.
  • Copy: copy the plug-in and its settings into the system clipboard. Onced copied, it can be pasted to any other slot, in any instance of the PatchWork plug-in (even in a different application).
  • Save As: save the plug-in in the slot and its settings as a favorite. Favorites are saved in the plug-in documents folder and can be organized using folders to appear later in sub menus.
  • Center Editor: bring back the editor of the plug-in to the center of the screen, in case you cannot find it.
  • Select: select a plug-in and its settings from the favorites list.
  • Load VST: load another VST plug-in in the slot (will replace the existing plug-in if any).
  • Load VST3: load another VST3 plug-in in the slot (will replace the existing plug-in if any).
  • Load AU (Mac only): load another Audio Unit plug-in in the slot (will replace the existing plug-in if any).
  • Paste: paste a plug-in and its settings from the system clipboard into the slot.
  • Paste with Map: paste a plug-in, its settings and mapped parameters from the system clipboard into the slot. Parameters are re-mapped in order, until no more assignable parameter is available.
  • Remove Plug-in: remove the plug-in from the slot.
  • Params Map: lists the plug-in's parameters that can be mapped for automation, and lets you assign them to external controls (see the next paragraph).
  • MIDI In: select the MIDI port(s) this plug-in is receiving data from (see below).
  • MIDI Out: select the MIDI port(s) this plug-in is sending MIDI data to (see below).
  • Audio I/O: opens the audio i/o routing window for this plug-in (see below).
  • Oversampling: select oversampling ratio and quality for the plug-in (see below).
  • Rename: rename the instance of the plug-in. Setting an empty name reverts back to the plug-in's default name.
  • Set Color: open the system color dialog to select the color for the plug-in slot.
  • Track Undo: toggle undo tracking for the slot. If enabled, inserted plug-ins changes will be inspected and added to the PatchWork plug-in undo history when possible. Please note that some plug-ins may not work properly when this feature is enabled. It is also recommended to disable this feature when controlling a plug-in with MIDI events generators such as Blue Cat's DP Meter Pro or Remote Control.

Once a plug-in has been loaded into a slot, the following buttons are available:

Clicking on the power button on the left will bypass/unbypass the plug-in in the slot. The button on the right can be used to show/hide the plug-in's editor.

Missing Plug-Ins

In some cases, it may happen that you are working on a workstation that does not have all plug-ins that were previously loaded into your PatchWork session. In this case, the PatchWork plug-in will display a "Missing Plug-in" message on corresponding slots. You can still continue working on your session: the PatchWork plug-in will retain the state of the missing plug-ins as if they were here. The session can be saved later: the data for missing plug-ins will be saved as well, and the session can be restored later without losing data.

For VST and VST3 plug-ins, if the plug-in is missing because of a path issue (the plug-in is located in another directory, or the 64-bit version has a different name from the 32-bit version...), you can choose to relocate the plug-in:

This lets you find the plug-in on your workstation and re-link to it. The state of the plug-in that was previously saved in the preset or the session will be restored, making sure all data is kept.

Note: the plug-in chosen with the relocate function has to be compatible with the plug-in that was originally loaded in this slot. Relocation will fail otherwise.

Mapping Parameters (One To One Quick Mapping)

The "Params Map" item in the plug-in menu lets you map sub plug-in parameters so that they can be automated or controlled with an external control surface. It also lets you view existing mapping for this plug-in if any:

  • Map All Params: assign all parameters of this plug-in to remaining controls (in the same order as exposed by the plug-in). The maximum number of parameters that can be mapped is 40.
  • Learn Mode (on/off): when learn mode is on, touching a control in your plug-in's user interface will automatically add it to the parameters map (if the plug-in supports it). Once you are done with parameters assignment, you may want to disable learn mode to avoid mapping unwanted parameters.
  • Reset All Assignments: removes all assigned parameters from the params map, for this plug-in. This frees all controls used by previously assigned parameters (for this plug-in only).
  • All parameters available for assignment are then displayed in the menu. Clicking on a parameter toggles mapping on or off. When a parameter is mapped, the name of the external control (as displayed in the host application) appears next to it, inside parentheses.

Parameters Mapping works the following way: 40 parameters are available for mapping in Blue Cat's PatchWork. They are named "Control 01" to "Control 40". When a sub plug-in parameter is selected for mapping, the first control available within Blue Cat's PatchWork is used. Once mapped, the sub plug-in parameter and this control are linked together, so that any change to either of them is reported to the other.

This enables the sub-plug-in to expose its parameters to the outside of the PatchWork plug-in. You can for example use these external controls for automation, MIDI control , control surface assignment etc.

If assigned controls are shown in Blue Cat's PatchWork ("Show Assigned Controls" button), new knobs will appear when new parameters are mapped, until the maximum number of 40 controls is reached.

It is possible to choose the style of the knobs using the menu, and set the name of each control by clicking on it:

These custom names should be displayed in the host application in place of "Control 01, Control 02..." if it supports it.

Macro Controls: The Parameters Map Editor

It is possible to access more advanced options for parameters mapping and create macro controls assigned to multiple parameters from multiple plug-ins by launching the Params Map Editor:

The Map Editor is displayed in a separate window that you can re-size at your convenience:

Available controls are displayed on the left (you can add or remove them with the icons on at the top), and when a control is selected you can see the parameters that have been assigned in the pane on the right.

Assignments can either be created manually (using the "Add" icon and then selecting the plug-in and parameter in the menus), or automatically with the learn button at the top right of the pane. When this assignment learn function is engaged, clicking or moving a knob of a plug-in should add the corresponding parameter to the list. Do not forget to disengage it when you are done or unwanted parameters might be added when touching the plug-ins later!

It is also possible to learn parameters individually using the learn button on the left of each line.

Once parameters have been added, their range can be adjusted using the knobs on the right (or by double clicking on the value). To reverse the range, simply invert the min and max values (using a min value that is larger than the max value).

You can also change the name of the controls by double clicking on them in the list displayed in the left pane.

It is also possible to change the order / add parameters by dragging and dropping items in the left column (it works between different instances too).

Internal MIDI Routing

Blue Cat's PatchWork lets you build your own MIDI connections between inserted plug-ins and the host application. Each slot can be connected to multiple ports to receive and send MIDI events:

  • Host: this port connects to the host application to send (MIDI Out) and receive (MIDI In) events. By default, all slots have their MIDI input connected to the Host.
  • Port A to Port P: these are virtual ports that can be used to connect sub plug-ins together.

For the MIDI input of a plug-in you can additionnaly choose to filter events by channel so that it receives all events for one or several selected channels only. If you just want the plug-in to receive all events without any filter, choose "All Channels" for the selected port.

Using virtual internal ports is simple: connect the output of a plug-in to a port, and the input of another plug-in to the same port. The two plug-ins will then be able to exchange MIDI data (from sender to receiver). Multiple plug-ins can be connected to the same port (as input or output). MIDI events will be gathered from MIDI Outs and redistributed to to all connected MIDI Ins.

However, there is a limitation in which plug-ins can be connected together:

  • it is not possible to create feedback loops.
  • only a plug-in that processes audio data before another can send MIDI data to this plug-in. It means that a plug-in can receive MIDI data from plug-ins that are located earlier in the audio processing chain only (see the signal flow above). If the plug-in is located in a parallel chain, it can also receive MIDI data from plug-ins that are located in parallel chains above it.

These limitations ensure causality and perfect synchronization of MIDI data exchanged between plug-ins, without latency.

Note: when connecting a plug-in to control its parameters via MIDI, you may want to disable undo tracking on this plug-in, to avoid that to many undo steps are recorded by Blue Cat's PatchWork and reduce CPU usage.

Audio I/O Routing

Using the "Audio I/O" command in the plug-in menu, it is possible to manually change which audio channels are processed by each plug-in.

Automatic Selection

By default, Blue Cat's Patchwork will automatically detect the number of channels to use for each plug-in depending on its own configuration: effect plug-ins will process only the main audio channels and leave aux and side chain channels unaffected. Plug-ins which appear to have a side chain input will receive the side chain channels. Plug-ins with aux outputs will be connected to aux channels if Blue Cat's patchWork is configured with aux outputs too.

About mono plug-ins: in automatic mode, mono plug-ins will process only the first audio channel, and the wet mono output will be copied to all channels of the main bus (aux and side chain unaffected). If you want to only apply the plug-in to one of the incoming audio channels instead, you can use the manual configuration.

Manual Selection

Automatic detection may however not work properly for some plug-ins, and you may want to change which channels the effect applies to (for multi-mono effects, or to process aux channels for example). That's what the audio I/O window is for:

By default, audio i/o selection is automatic

When selecting a specific number of inputs and/or outputs instead of using "automatic", you can choose which channels are connected to each i/o for this particular plug-in:

manual audio i/o configuration


  • if the same channel is selected for multiple outputs, only the last selected plug-in output will be audible (plug-in outputs are not summed).
  • By default, all channels that are not used as outputs by the plug-in remain unchanged (copied from the same channels before the plug-in). For example, on a stereo configuration, if a mono plug-in is set to process only channel 1 and use channel 1 as output, channel 2 will remain unaffected. Select "mute unused audio channels" to mute these unprocessed channels instead.

Auto vs Manual

In automatic mode, Blue Cat's PatchWork will automatically choose the best configuration according to its own audio layout. This is very useful if you are saving your plug-in chains to reuse them with different audio i/o configurations.

In manual mode, the number of inputs and outputs of the selected plug-in is selected and will not change. It means that you may not be able to use this particular configuration later with another number of audio channels.


Starting with PatchWork 2.65, it is possible to have a plug-in process audio (and MIDI) at higher samplerates. You can select the oversampling ratio and resampling quality with the oversampling menu:

Oversampling can be useful for plug-ins doing non-linear processing (distortion, compression...) which do not have built-in oversampling capabilities and cause artefacts (aliasing). It may also benefit EQs (you can get smoother curves in the upper frequencies).

Oversampling may however result in other types of artefacts and will require more CPU to process the same amount of data. With high quality resampling, additional latency may also apply.

Warning: please note that some third party plug-ins may not support higher sample rates. Save your work before trying this feature on new plug-ins!

Tip: If you want to oversample an entire chain of plug-ins, you can load the built-in version of PatchWork in a slot, load your plug-ins inside, and choose to oversample the Patchwork plug-in containing the entire chain.

Note: The oversampling settings are saved when using the "Save As..." command to save the plug-in as a favorite.

The Preferences Pane

In the preferences pane, you can set the default VST plug-ins path by clicking on it or on the button labelled "...". This VST plug-ins directory is used for several purposes:

  • It is the default directory that is opened when you want to load a VST plug-in.
  • It is used as the root path when saving/loading presets that include VST effects: the path of VST plug-ins is saved relatively to this root path, so that you can reopen your sessions on different machines that may have different VST paths (typically on a Mac and a PC).

If you happen to have your VST plug-ins installed in several paths, we advise you to choose the VST path that contains most of your plug-ins. You can then use the "User VST plug-ins directory" to define an extra location for plug-ins. This extra path will be used by the PatchWork plug-in as an alternative root path to load and save the plug-ins.

Please note that these paths are used for VST2 plug-ins only - they do not affect the location of VST3 plug-ins.

If the "Restore plug-ins editors on open" option is checked (default), when the PatchWork plug-in is opened, inserted plug-ins user interfaces will be restored at the same position as when the PatchWork plug-in was last closed. If the option is unchecked, all plug-ins user interfaces will be kept closed when re-opening the PatchWork plug-in, and their position on screen will not be saved.

When the "plug-ins editors always on top" option is checked, the windows of the hosted plug-ins will be kept on top of all other windows. It can be useful when you want to make sure the hosted plug-ins remain visible all the time. Also, if you are using Cubase on Windows, you may want to check this option to fix the erratic behavior of Cubase's own "always on top" option.

Drag and drop support

The user interface supports drag and drop to manipulate plug-ins easily:

  • drag and drop plug-ins between slots (copy or move).
  • hold the alt key on Mac and Ctrl key on windows to copy (duplicate) a plug-in instead of moving it.
  • drop the plug-in before another to insert it in the chain
  • drag and drop plug-ins between several instances of the plug-in/app or accross plug-ins (compatible with the latest versions of Late Replies, MB-7 Mixer, Axiom and Fader Hub).
  • drag and drop .dll, .vst, .vst3, or .component files directly from the Finder or Explorer onto plug-in slots.
  • drag and drop .plgnfo files (previously saved from the software) directly from the Finder or Explorer onto plug-in slots.

The various elements of the user interface (knobs, sliders, buttons...) are simple and intuitive to operate, but more information about how to interact with them is available in the "Plug-ins Basics" chapter of this manual.


This section decribes several common use cases for the plug-in. A complete list of the parameters exposed by the plug-in is available in the next section.

Custom Channel Strip

When configured with a single column, the plug-in can be used as a simple custom channel strip, chaining plug-ins together:

That's the preferred configuration to use the plug-in as a simple chainer.

Mixing Multiple Synths

If you want to mix the sounds of multiple synths and control them as if it were a single synthesizer, you can use several parallel chains and insert a synth on the first slot of each chain. No need for multiple tracks: all synths can be stacked together on a single track and controlled with a single keyboard with no additional MIDI routing required.

For this scenario you probably want to use the "sum" parallel chain mode so that the volume of each synth is not altered when soloing or muting one of the chains.

You can also improve your multi-synth presets using MIDI effects (arpeggiator, MIDI delay...) and connecting the MIDI input of some of the synths to the MIDI output of these MIDI effects. This lets you create a single preset with multiple synths playing different arpeggios, all triggered by a single keyboard (See "MIDI Routing" below).

Comparing Effects Chains

It is often useful to try several effects chains before choosing the one that fits best on a track. Blue Cat's PatchWork makes it very easy to do A/B comparisons: it is possible to use two or more parallel chains and activate one after another to compare them. They can include different plug-ins or the same plug-ins with different settings.

Instant Configuration Recall

You can save your favorite effect chains and settings as presets, including full windows layouts. They can be recalled later with a single click in the presets menu.

This is of course applicable to audio effects, but it can also be useful to store complete synthesizer plus additional effects configurations as presets, so that the complete chain can be restored easily (instead of having separate presets for synths and post effects).

Custom Parameters Mapping

It can be interesting to combine Blue Cat's PatchWork's parameters mapping feature with its advanced automation and MIDI control capabilities in order to wrap an existing plug-in that does not provide the same flexibility. For example, if you have a plug-in that does not support MIDI control, you can just map its parameters within the PatchWork plug-in and then use the mapped parameters for MIDI control.

All mapped parameters have the same control options as all Blue Cat Audio plug-ins parameters: you can choose the response curve, modify the range or choose MIDI control messages. MIDI learn is also available. And it is now possible to apply these capabilities to all other existing plug-ins!

Macro Controls And Custom Plug-In

With macro controls (controls assigned to multiple plug-ins parameters), it is possible to create your own custom plug-in with a reduced set of parameters, out of a complex chain of existing plug-ins:

It can be saved as a preset and used as a custom effect in the future, without having to open each plug-in's individual editor to perform adjustments.

MIDI Routing

You can easily create your own synth using multiple plug-ins connected via internal MIDI ports: for example, why wouldn't you trigger several MIDI arpegiators with a single keyboard, each one controlling different synths? And all within a single plug-in: Blue Cat's PatchWork!

It is also possible to use these MIDI routing capabilities together with our plug-ins that can generate MIDI CC in order to create side chain effects quickly, all within Blue Cat's Patchwork: for example, detect the envelope of the incoming sound in a parallel chain and control the cutoff of a filter on a synth from another chain!

What may be tricky in your DAW and require multiple MIDI tracks to create MIDI connections is much simpler using Blue Cat's PatchWork instead.

Computing Differences Using Phase Flip

Flipping phase on a parallel chain is the same as multiplying the sound by -1. So it is possible to compute the difference between two effect chains easily. A typical application is to use an empty effect chain with flipped phase in parallel with an effect chain you are tweaking:

The above setup performs A minus B. And since the B chain carries the dry signal, as a result you can hear what the A chain actually adds to the original signal. This is particularly useful for dynamics processing or distortion: you can hear what the effect adds to the original sound (and you can easily switch to the full processed signal by disabling chain B).

Note: you may have to adjust the gain of the B chain, if the A chain does not preserve the average volume.

Creating a Virtual Send to Aux Channels

With a simple plug-in such as Blue Cat's Gain Suite and changing its outputs to another set of audio channels, you can create a "send" to aux outputs and control its volume:

sending channels 1/2 to channel 3/4

With the above setup, channel 1 and 2 will remain unaffected after the plug-in, whereas channels 3/4 will contain the original 1/2 channels, modified by the gain plug-in.

This can be useful if you want to route audio channels to the auxiliary outputs of the PatchWork plug-in for additional processing in your host application, or send particular channels to the side chain input of a plug-in down in the processing chain.

Auxiliary Outputs Routing for Instruments

Some virtual instrument plug-ins offer many auxiliary outputs, but there is sometimes no way to select a specific output for each sound. This can be solved easily by using Blue Cat's PatchWork and selecting your own routing:

selecting synth output channels

Each aux output can also be processed by different plug-ins, so you can easily swap between sounds and effects aven after the effect chains have been setup!

Multi Mono Effects

Using the Audio I/O panel, you can quickly apply different mono effects to the various audio channels, as shown below:

Patchwork of Patchworks

When using complex routings and many plug-ins, you may want to reuse parts of your effects configurations as modules. In this case, using several instances of the Patchwork plug-in into another one and using presets for predefined configurations will do the trick!

Standalone Application Basics

Main Features

The standalone application will let you process audio data coming from the inputs of the audio interface and stream it to its output, in real time, without the need for a third party host application. The application also receives MIDI events from all MIDI input interfaces available on the machine, without any particular configuration required.

The core features of the application are the same as the plug-ins versions, except that the application can run on its own.

It is worth noting that user presets are shared between the standalone application and the plug-ins versions, so that presets can be reused between standlone and plug-in sessions.

Application Preferences

The audio/MIDI setup for the application is decribed in details in the first launch chapter.

The configuration window above can be displayed using the Edit/Audio Setup menu item. More information about the various fields can be found in the first launch chapter.

Application Menu

The application menu gives you access to the following commands:

  • Edit/Undo: undo last change.
  • Edit/Redo: redo last undone change.
  • Edit/Audio Setup: open the preferences window.

Keyboard Shortcuts

To speed up operation, several keyboard shortcuts are available in the standalone application:

On Windows

  • CTRL+Z: undo.
  • Shift CTRL+Z: redo.
  • CTRL+P: open the preferences window.
  • ALT+F4: quit the application.

On Mac

  • CMD+Z: undo.
  • Shift CMD+Z: redo.
  • CMD+, or CMD+P: open the preferences window.
  • CMD+Q: quit the application.


No Sound

if you cannot hear anything coming out of the software, you need to check the audio configuration: open the preferences window (Edit Menu / Audio Setup command), and check that the audio engine is running. If it is not running, you may need to select another audio interface or change the buffer and sample rate settings. If it is running, you may want to select another audio interface or differnt audio inputs and outputs.

Cracks and Pops

If you can hear unwanted "cracks" and "pops" during the performance, you may be experiencing audio dropouts, because the application is using too much CPU. You can try to increase the buffer size in the preferences window to reduce CPU usage, and close other applications that are currently running.

Blue Cat Audio Plug-Ins Basics

This chapter describes the basic features that are common to all our plug-ins. If you are already familiar with our products, you can skip this part.

User Interface Basics

About Skins

Like all Blue Cat Audio plug-ins, Blue Cat's PatchWork uses a skinnable user interface. It means that the appearance and behavior of the user interface can be entirely customized.

Especially with third party skins, the experience may be quite different from the one offered by the default skins that we provide. However, our plug-ins and our skinning engine have several standard features that will be available whatever your favorite skin.

More information about custom skins can be found in the skins section.

The Main Toolbar

In most skins, an optional toolbar at the top of the user interface gives you access to the main options and settings of the plug-in:

Smooth Bypass

On the left, the power button can be used to smoothly bypass the plug-in.

Presets Area

At the center of the toolbar, you can see the current preset area (the "Default Settings" box). It displays the name of the current preset, with a "*" at the end if it has been modified since loaded.

The arrows on the left and right let you navigate thru the (factory and user) presets available for the plug-in.

Clicking on the preset name opens the presets menu which lets you manage the presets of the plug-in.

Using the knob on the bottom right of this area, you can reduce the opacity of the window, and make it transparent (the actual result may depend on the host application). Additional messages may appear in the area next to this knob, depending on the plug-in.

Some plug-ins may also propose you to manually select the audio I/O inside the plug-in (bottom left of the presets area), regardless of the host configuration. It can be useful for example to save CPU by selecting mono to stereo configurations (instead of full stereo sometimes chosen by default by the host), or add extra channels to manage side chain internally, when the host does not provides any side chain input. Please note that this does not change the number of I/O seen by the host application.


The icons in the toolbar give you access the to the following commands that are detailed in the next paragraph:

Icon Name Function
Menu Open the main menu
Control Settings Display the controls settings menu (to manage automation and MIDI control, as described here).
Undo Undo
Redo Redo
Manual User Manual
About About
Zoom Scale the user interface (from 70% to 200%).

The Main Menu

The main menu is available from the main toolbar, or if you right click anywhere on the background of the plug-in:

  • Presets: opens the presets menu to manage presets.
  • Preset Skin: opens the skins menu to choose the skin for the current preset and manage alternative skins for the software.
  • Undo/Redo: undo or redo the latest modifications. This includes all changes made to the current preset settings such as MIDI or automation preferences.
  • Presets Settings: open the presets settings window. It lets you change the skin, MIDI and automation settings for the current preset.
  • Global Settings: open the global settings window. It lets you change the skin, MIDI and automation settings that are used by default in all instances of the plug-in (if not overridden by the current preset).
  • User Manual: open this user manual.
  • Check for Updates: opens up our website to let you check if any update for this software is available.
  • Get More Skins: get more skins for this software.
  • Legal Information: browse licensing and misc legal documents.
  • About: displays the “about” dialog box.



Here are a few examples of typical controls you will encounter in the user interface of our plug-ins:

slider slider knob button Text control

Interacting with Controls

You can interact with the controls of the plug-in interface either with the mouse or the keyboard.

Setting the keyboard focus on a control (so that it responds to key strokes) may be automatic (when you pass the mouse over it it gets focus) or manual (you have to click on the control to set the focus on it). Note that all host applications behave differently regarding keyboard handling. In some applications you may not be able to use all keys described later in this manual to interact with our plug-ins. It is usually made obvious to you to know the active surfaces of the skin (the places where you can click with the mouse): the mouse cursor usually changes when you can do something on a control. In the default skins delivered with the plug-in, the cursor changes to a small hand or an arrow to tell you when your mouse is over an active control.


Various mouse movements will let you interact with the controls:

Mouse Interaction Action
Left Click Acquire focus and start dragging or push (button)
Left Click + Alt Key Set the value to default
Left Double Click Acquire focus and launch the “fine tuning” edit box (except button):
Right Click Set the value to default
Mouse Wheel Increment or decrement the position (focus required)
Mouse Drag Change the control position depending on mouse movement (except button)


All control widgets support the following keys (note that some of them are caught by the host and thus never forwarded to the control. For example in Steinberg Cubase SX you cannot use the arrow keys to control the plug-in):

Keys Common to All Controls

Key Action
Up Arrow Small increment of the position (up or right)
Down Arrow Small increment of the position (down or left)
Left Arrow Same as Down Arrow
Right Arrow Same as Up Arrow
Page Up Large increment of the position (up or right)
Page Down Large decrement of the position (down or left)
+ Small increment of the value of the control
- Small decrement of the value of the control
d Set to default value (same as mouse right click)
e Opens the 'fine tuning' window to precisely set the parameter:
SHIFT When the key is down, the fine tuning mode is on, and you can modify the value with better precision when moving the mouse, the mouse wheel or using the keyboard. Just release the key to get back to the normal mode.

Keys Specific to Buttons

Key Action
Enter Pushes the button


To get started with the plug-in and discover its capabilities, a couple of factory presets are provided. You can also save your own presets and recall them later for other projects. Our plug-ins propose a full-featured preset manager to let you save, browse, organize and recall its presets.

The Presets Menu

The presets menu can be opened from the main menu or the main toolbar. It displays the list of presets available for the plug-in as well as commands to load, save or organize presets:

  • Factory Presets: shows the list of factory presets delivered with the plug-in.
  • "Folder A" to "User Preset Z": user presets and categories.
  • MIDI Program Change: activate MIDI Program Change support (see below).
  • Load: load preset from file.
  • Save: save current state to last loaded user preset.
  • Save As: save current preset to a file.
  • Copy copy preset to the system clipboard.
  • Paste paste preset from the system clipboard, if available.
  • Save As User Default: save the current state as the default preset. This preset is used every time a new instance of the plug-in is created.
  • Clear User Default: reset the default preset to its factory state: this makes the plug-in forgets the custom settings you might have saved as a default preset.

More about Presets

There are two types of presets: factory presets (read only) that are provided with the plug-in, and user presets that can be created and stored by the user.

The user presets are stored in a subdirectory of the documents folders of your profile ("Documents" on Mac, and "My Documents" on Windows): Blue Cat Audio/[Plug-in Name]/Presets. Each preset is stored as an individual file. You can create folders and subfolders in the Presets directory to classify your presets, as shown in the example below:

If you save a preset named "Default" in the root Presets directory, it will override the factory default preset (that's what "Save As Default" does). To restore the factory default preset, you can just remove this file or use the "Reset Default" command.

MIDI Program Change

It is possible to load presets remotely using MIDI "Bank Select" and "Program Change" messages. To enable this feature, select a MIDI channel to receive the events from in the MIDI Program Change menu item from the presets menu:

This setting is saved for each plug-in istance with your session but not in presets (except for the default preset, using the "Save as User Default command"). Once activated, the plug-in menu will display the bank number followed by the preset number for each preset:

Every root folder is considered as a new bank, starting with the factory presets (bank 0). Program and bank numbers may change while you add folders and presets, so you should be careful when naming them if bank and program numbers matter to you. It is recommended to use folders to make this task simpler. As a side note, sub folders do not define additional banks (all presets contained in sub folders are associated with the current bank.

As specified by MIDI, bank select messages are not used until a program is actually selected.

MIDI Implementation note: the software supports all types of Bank Select methods. You can use either MIDI CC 0 or MIDI CC 32 to select banks. If both are used simultaneously, they are combined together so that you can use more banks (in this case CC0 is LSB and CC32 is MSB, and actual bank number is 128*CC0+CC32).

MIDI and Automation Control

Blue Cat's PatchWork can also be remotely controlled via MIDI using MIDI CC ("Control Change") messages or automation curves, if your host application supports it. It is possible to customize the channel, control numbers, range and response curve used for each parameter in the settings panel available from the main menu (see the Plug-in Settings chapter for more details).

MIDI and Automation Settings Menu

The main menu

Most skins also provide the ability to change MIDI and automation settings directly in the main user interface. Clicking on the control settings icon in the main toolbar opens the following menu:

  • Show Control Settings: show direct access to individual control settings for each parameter in the user interface (see next paragraph).
  • Lock Control Settings: lock the current controls settings for MIDI and automation so that they remain unchanged when loading presets.
  • Use Global Control Settings: ignore the current MIDI/automation settings and use the global settings instead.
  • Control Settings Window: display the control settings window, to change control settings for all parameters.
  • Save As Global Control Settings: save the current settings as global settings (used by default, when no specific MIDI/Automation setting has been set for the cuirrent preset).

Individual Control Settings

When this feature is activated using the "Show Control Settings" item in the MIDI and Automation Settings menu, dropdown menu buttons appears next to the main controls displayed by the plug-in:

Clicking on this button shows the MIDI/Automation settings menu:

  • MIDI Learn: launches MIDI learn mode for the control: touch your MIDI controller and the control will learn from it the MIDI channel and CC number. To end the learn mode, reopen this menu and deselect the option.
  • MIDI Unlearn: deactivates MIDI control for this parameter.
  • Control Settings: launches the advanced settings panel described below. This controls the settings for the current preset.
  • All Control Settings: display the control settings window, with access to all parameters.

Advanced MIDI and Automation Settings

You can completely customize the way the plug-in is controlled by automation and MIDI. For a global view of all parameters at a time, you can use the Plug-in Settings window for the current preset which is available from the main menu.

MIDI Settings:

  • Enable MIDI: enable/disable the MIDI control of the parameter.
  • Channel: MIDI Channel for the parameter control. If set to 0, the plug-ins will accept Control Change Messages from all MIDI Channels (MIDI Omni mode).
  • CC: Control Change Number.
  • Learn: click on this button to activate the MIDI learn functionality. When it is activated, you can move your MIDI controller, and the plug-in will automatically set the MIDI Channel and CC Number.

MIDI and automation settings:

  • Response: response curve of the MIDI or automation control: from very fast to slow control.
  • Min: minimal value of the parameter when MIDI controlled or automated.
  • Max: Maximum value of the parameter when MIDI controlled or automated.

Note: if the Min value is higher than the Max value, the response curve will be reversed: increasing the control value will decrease the parameter value.

Note: if you double click on the parameter text control boxes for the max and min values, a “fine tuning” edit box will appear and let you change the min and max values with more precision:


Check our online tutorial for more screenshots and more examples of our plug-ins user interfaces.

Blue Cat's PatchWork Parameters

All parameters described below can be automated and controlled via MIDI if your host application supports it. You can precisely define this behavior in the settings panels described later in this manual.


The input parameters of this plug-in are the following:

Name Unit Description Comment
Bypass the effect.
Number of columns for the rack.
Number of rows for the rack.
Amount of wet signal compared to dry input signal (0% is fully dry or unprocessed, 100% is processed signal only).
In Gain dB Input Gain.
Out Gain dB Output Gain.
Level Meters
Enable or disable level meters.
Summing mode for parallel chains.
For each parallel effect chain (index: i)
Power i
Activate parallel chain number i.
Pre Gain i dB Pre gain for parallel chain i
Post Gain i dB Post gain for parallel chain i
Phase Flip i dB Invert phase for parallel chain i
Solo i
Solo parallel chain number i. Solo will deactivate all other non-soloed parallel chains.
Assignable Controls
Control 01 to Control 40 dB Assignable parameters for sub plug-ins automation.

Plug-in Settings

In addition to the controls offered in the main user interface, Blue Cat's PatchWork has various settings that let you fine tune the behavior of the plug-in. You can choose to change these settings either for the current preset or globally for all instances of the plug-in.

The Global Settings Window

The settings available in this window apply to all instances of the plug-in, for all presets, if not overridden in the presets settings. Consider these settings as “default” settings.


You can change the default skin for all instances of the plug-in: write the skin file path in the text edit box or click on the button to open a file chooser dialog. If you have several instances of the plug-in opened in your session, you will have to re-open the user interfaces of these plug-ins to see the skin change.

The output data refresh rate can also be customized for all instances of the plug-in. It controls the refresh rate of non-audio data produced by the plug-in (parameters, curves...). It also controls the refresh rate of output MIDI CC messages or output automation data. The higher the refresh rate, the better precision, but also the higher cpu usage (some host applications may also have trouble recording MIDI data at high refresh rates). The default value is 50 Hz.

Global Control Input Settings (MIDI and Automation)

The plug-in offers a couple of settings that affect the way it is controlled by MIDI messages or automation. While the first settings only apply to MIDI control, the "Control Response", "Min" and "Max" settings apply to both automation and MIDI control.

For each parameter you can define a default MIDI channel and CC number. You can then control the plug-in with an external MIDI controller or one of our plug-ins that generate MIDI messages.

The settings below are available for each plug-in parameter.

MIDI Settings:

  • Enable MIDI: enable/disable the MIDI control of the parameter.
  • Channel: MIDI Channel for the parameter control. If set to 0, the plug-ins will accept Control Change Messages from all MIDI Channels (MIDI Omni mode).
  • CC: Control Change Number.
  • Learn: click on this button to activate the MIDI learn functionality. When it is activated, you can move your MIDI controller, and the plug-in will automatically set the MIDI Channel and CC Number.

MIDI and automation settings:

  • Response: response curve of the MIDI or automation control: from very fast to slow control.
  • Min: minimal value of the parameter when MIDI controlled or automated.
  • Max: Maximum value of the parameter when MIDI controlled or automated.

(generic screen shot, does not correspond to the actual plug-in parameters)

Note: if the Min value is higher than the Max value, the response curve will be reversed: increasing the control value will decrease the parameter value.

Note: if you double click on the parameter text control boxes for the max and min values, a “fine tuning” edit box will appear and let you change the min and max values with more precision:

"Send MIDI events when parameters values change": activate this option when using a control surface that accepts MIDI events as input. MIDI messages will be sent to the output of the plug-in when the user change the parameters values in the user interface, to keep the software and the controller in sync. MIDI is only sent for parameters that are activated for MIDI control.

The Current Preset Settings Window

In this window you can change the settings for the current preset of the current instance of the plug-in only.

Preset Skin

You can choose to use the global skin setting or to change the skin for the current preset. This way you can have different skins for different instances of the plug-in in the same session in order to differentiate them.

Preset Control Input Settings (MIDI and Automation)

Use the global settings or override them for the current preset. The parameters are the same as for the global input settings.

(generic screen shot, does not correspond to the actual plug-in parameters)

About Skins

Blue Cat's PatchWork integrates Blue Cat's skinning engine that allows you to customize the user interface. You can download alternate skins for your plug-in at the following address:

If you don't find a skin that fits your need or if you want a custom one, you can choose to create your own skin.

Choosing the Skin

There are two ways to select the skin of your plug-in: you can change the default (or 'global') skin, or change the skin for the current preset only (either in the preset settings page or from the main menu). The global skin applies to all plug-in instances (choose this one if you want to use the skin used by default, regardless of the session or preset), whereas the current preset skin only applies to the current preset of the current plug-in instance (use this one if you want to change only the skin for the current session/preset).

Note: in some host applications, the plug-in window won't resize automatically when you choose a skin with a different size. In this case, just close the window and re-open it: it will be displayed with the right size.

The Skins Menu

The skins menu can be opened from the main menu. It displays the list of skins available for the plug-in as well as commands to manage the skin used by default when no preset skin has been selected:

  • First Section - Factory Skins: shows the list of factory skins delivered with the plug-in ("Default" and "Light" in this example).
  • Second Section - User Skins: shows the list of user skins that have been installed in the Documents Skins folder for the plug-in (see below).
  • Use Global Skin: use the global skin for the current preset/session (unloads any custom skin previously selected for the current preset).
  • Load: opens a file browser dialog to manually select the skin from the file system.
  • Save As Global Skin: use the current preset skin as the global skin (loaded by default if no preset skin has been defined).

Installing User Skins

To select user skins directly from the skins menu, install them in the "Skins" directory available in the plug-in's documents folder:

[Your Documents Folder]/Blue Cat Audio/[Plugin Name]/Skins/

The skin engine will scan this folder for new skins (xml files) and display them in the menu. The skin files should be in the root skins folder or in a subdirectory inside this folder: subdirectories are not scanned recursively.

Other Methods to Select Skins

You can also select the skins in the settings panels available from the main menu:

The global skin (used by default if no preset skin has been selected) can be changed in the global settings pane. The current preset skin can be changed in the preset settings page .

Create a Custom Skin

You can create custom skins for your plug-in in order to adapt it to your exact needs. You can change its look and feel and make it completely integrated in your virtual studio!

Just read the Blue Cat's Skinning Language manual and download the samples for the tutorial on You can get ready to create your own skins in a few minutes. You can then share your skins on our website.


This manual only covers the main aspects of Blue Cat's PatchWork. Our website offers many additional resources for your Blue Cat's PatchWork plug-in. It is constantly updated, so keep an eye on it!


As you can see in the history log below, we care about constantly updating our products in order to give you the latest technology available. Please visit our website often to check if Blue Cat's PatchWork has been updated, or subscribe to our Newsletter to be informed of the latest news about our products.

Note: minor version updates are available from the same location as the original full version download (link received by email upon purchase). The demo version publicly available on our website will not let you register.

You can also follow us on twitter, facebook and instagram for almost real time updates notification, and subscribe to our YouTube channel to watch the latest videos about our software.

Versions History

V2.68 (2024/07/03)

  • New option to disable "suspend processing on silence" for plug-ins that do not report tail size properly (such as Valhalla plug-ins).
  • Added .aif files support in built-in audio player.
  • Reduced GPU usage under MacOS Sonoma, now that Apple has fixed the performance issue (Sonoma 14.3 and newer required).
  • Fixed Mix parameter not always properly recalled when loading a preset.
  • Fixed an issue with stuck MIDI notes with some VST3 plug-ins.
  • Fixed a potential issue with VST3 plug-ins using unicode characters in parameter names and values.
  • Fixed a crash with some VST3 plug-ins requiring inputParameterChanges (such as Martinic plug-ins).
  • Fixed crash on Apple Silicon and wrong preset names on other platforms when loading VST3 plug-ins that define presets without names (such as FabFilter plug-ins).

V2.67 (2024/02/28)

  • Seamlessly play over backing tracks with the new built-in audio player, supporting wav, mp3, and flac formats.
  • Drag and drop audio files directly into plug-in slots to open the audio player.
  • Choose from additional 15 styles to customize macro knobs.
  • Playback and rewind in the application can now be triggered by MIDI (allowing easy synchronization of plug-ins playback).
  • Offline rendering support: hosted plug-ins are now notified when the host application is rendering offline (non-realtime).
  • Improved audio performance when the application is used as a network server for Connector or Fader Hub.
  • Fixed audio recording issues under very low latencies and high CPU usage.
  • Fixed multicore performance issues for Apple Silicon systems (random audio dropouts).
  • Improved multicore performance on Intel Macs and Windows PCs.
  • Fixed Graphical User Interface performance issues on Mac OS Sonoma (caused by an Apple bug).
  • Fixed a crash with Audio Units reporting corrupted latency (invalid value) upon load.

V2.66 (2023/07/06)

  • Drag and drop macro parameters to change order / insert / copy.
  • Macro Parameters & params assignments can now be saved and copied/pasted.
  • The "Remove" macro command now removes the currently selected macro parameter instead of the last one.
  • Macro LEARN mode is now disabled automatically when the Params Map Editor is closed.
  • AAX plug-in now reports the recording status to hosted plug-ins (in recent versions of Pro Tools that support it).
  • Synchronize multiple MIDI controllers: when "all channels" (0) is used for MIDI input control and "send MIDI events when parameters values change" is active, the plug-in now sends MIDI events to all other channels.
  • Updated parameters layout for GUI-less plug-ins to accomodate plug-ins with multiple parameters.
  • GUI-less plug-ins generic editor now follows PatchWork's zoom level.
  • Improved plug-in loading time.
  • Fixed a crash when opening the editor of a VST2 GUI-less plug-in that uses non-unicode encoding in its parameters (piz-midi plug-ins).
  • Fixed plug-in slots display issue on Mac OS 10.9.
  • Fixed plug-in slot menu issues when loading plug-ins with more than 22380 parameters on Windows.

V2.65 (2023/03/14)

  • Plug-ins oversampling: it is now possible to oversample processing for every plug-in (up to 16x).
  • Custom Colors: Each individual plug-in instance can now be assigned a custom color.
  • Updated 120 factory presets and all built-in plug-ins with custom colors.
  • PatchWork can now use its own parameters in macros, mixed together with loaded plug-ins parameters.
  • Graphical user interface refresh performance improvements, especially on Mac.
  • Improved resampling when the application starts streaming audio as a network server with Blue Cat's Connector.
  • Fixed custom tone maps presets not properly saved for some built-in plug-ins (Reverb, Chorus, Flanger, Phaser, Sweep Filter, Wave Shaper, Freq Shifter, Wah, EQ).
  • Fixed stuck notes with some VST3 instruments.
  • Fixed some VST3 instruments not producing any sound (like Toontrack instruments).
  • Ableton Live 11: Fixed PatchWork VST3 MIDI input not detected and PatchWork Synth VST3 not loading.

V2.61 (2022/12/12)

  • New transport toolbar in PatchWork app, including pause, rewind and tempo selection (with tap tempo).
  • Added Apple Silicon support for AAX plug-in format.
  • Added Ambisonic (1st order) and alternate surround formats (up to 8ch) support for Pro Tools.
  • Fixed an issue with some VST3 plug-ins requiring to click twice on the bypass button to get bypassed.

V2.6 (2022/09/26)

  • New macro controls editor to edit plug-in parameters mapping.
  • Assign multiple parameters from multiple plug-ins to a single macro control, and adjust the range for each parameter.
  • Assign a name to each macro control, that is now displayed in automation lanes in most host applications (may require a session reload in some cases).
  • Parameters names for existing sessions will be automatically updated upon load.
  • Select macro knobs appearance among 19 predefined styles.
  • New learn modes to quickly assign plug-in parameters.
  • MIDI output is now enabled in standalone application.
  • Select individual MIDI I/O in standalone application.
  • Added an option in global & preset input settings to send MIDI events when MIDI-enabled parameters are modified in the plug-in (to update control surfaces accordingly).
  • In most plug-in formats, internal audio I/O configuration can now be selected regardless of the configuration defined by the host (you can for example reduce the number of channels to save CPU and process only selected channels).
  • PatchWork App now uses Apple's Hardened Runtime and the installer has been notarized to avoid security warnings on Mac.
  • Improved performance to load the user interface.
  • Improved VST parameter value display in some host applications.
  • Fixed bypass that did not let MIDI messages go thru for some MIDI plug-ins.
  • Fixed some GUI resizing issues with some VST3 plug-ins.
  • Fixed signal overflow issues with the Reverb built-in plug-in for some surround configurations.
Warning: presets and sessions saved with this new version will not reload properly with older versions of PatchWork (params maps will be lost).

V2.52 (2022/03/28)

  • Native Apple Silicon (M1) version can now load 64-bit Audio Units that are not compatible with Apple Silicon (via the MacOS bridge).
  • New "network slave" mode to run as an audio/MIDI processing server for the Connector plug-in.
  • Presets can now be loaded via MIDI even when the user interface is closed.
  • Improved MIDI events timing precision in the application.
  • Windows: ASIO Control panel can now be launched from the audio settings window in the application.
  • Audio engine can now be restarted from the audio settings window in the application.
  • Fixed MPC Beat plug-in not loading.
  • Fixed VST3 version not always loading properly in Ableton Live 11.
  • Fixed latency compensation changes not always picked up by host applications.
  • VST3: Fixed parameters update issues in Studio One when bouncing tracks.

V2.51 (2021/11/18)

  • Single Installer on Mac (all plug-ins formats).
  • Apple Silicon (M1 processor) support.
  • Dropped 32-bit support on Mac.
  • Dropped legacy RTAS format support.
  • Now requires MacOS 10.9 and newer.
  • Added MIDI tap tempo support for standalone application
  • Improved MIDI & automation control settings with lock, reset and "save as global setting" capabilities.
  • Fixed issues with Wah and Pitch Bender effects when using cheap MIDI controllers not updating values fast enough.
  • VST3: fixed random crash in Ableton Live 11 upon load.
  • VST3: fixed parameters update issues in Studio One when bouncing tracks.
  • Fixed a crash when loading some VST3 plug-ins that define a bypass parameter beyond the last automatable parameter.
  • Fixed skin loading issue when loading the built-in PatchWork plug-in in the PatchWork Synth version.
  • AAX: Fixed erratic mouse behavior in Pro Tools on Mac.

V2.5 (2021/04/06)

New Features & Improvements:
  • Up to 8 times more processing power with the new multicore engine that processes each parallel chain on a separate core.
  • New DSP workload meter that displays the DSP activity and CPU load.
  • Added MIDI control support (MIDI CC messages) for Next and Previous Preset commands, with MIDI learn.
  • Reduced time to load PatchWork or any built-in plug-in.
  • Multiple DSP performance improvements.
  • Improved buffer management in standalone application on Mac, reducing both latency and CPU usage.
  • Level meters are not updated anymore when the user interface is closed, reducing CPU usage.
  • Reduced the number of threads used by the plug-in.
  • Improved global and preset settings window loading time on Windows.
  • Added ability to select the plug-in to load when a shell plug-in file is dragged and dropped onto a slot.
  • Full unicode support.
  • Preset files can now be dropped onto the preset LCD area to be loaded.
  • Improved "Tone Maps" user interface (available for 9 built-in effects).
  • Fixed standalone app not always asking for Microphone access on most recent MacOS systems.
  • Fixed host loop end value not properly passed to hosted plug-ins, for the VST2 version.
  • Fixed several crashes upon load for multiple third party plug-ins (mostly VST3).
  • Fixed display issues with Waves plug-ins V12 in Mac standalone application.
  • Fixed MIDI control for hosted plug-ins not always working when fed with silence.
  • Fixed VST3 (and sometimes VST) version freezing Ableton Live upon save on Windows.
  • Fixed harmonizer and Pitch Shifter built-in plug-ins that did not always flush their buffer upon bypass (short sounds could be heard when getting out of bypass)

V2.43 (2020/10/05)

New Features & Improvements:
  • Tail spillover: activate tail spillover from the toolbar to play effects tail when bypassed (available for PatchWork itself or built-in delays and reverbs).
  • Arrow keys can now be used to navigate presets, in the main view or in the presets browser.
  • The opacity of the tone map window can now be adjusted for built-in effects.
  • Smoother presets switching.
  • Improved smooth plug-in bypass (faster and smoother transition).
  • New high resolution graphics for knobs and sliders.
  • Reduced disk footprint.
  • Fixed: the state of some VST2 plug-ins (which do not save their state as chunks) were not be restored properly if their number of parameters had been changed (e.g. FabFilter Pro-Q's latest update).
  • Fixed: several issues with hosted plug-ins bypass (graphical glitches, untriggered bypass...).
  • Mac: fixed GUI performance issues on native P3 displays and improved performance on other displays.
  • Mac: fixed mouse wheel that required large movements to change parameter values.
  • Mac: fixed mouse cursor flickering issues.
  • Mac: fixed Esc key not closing fine edit parameter dialog.
  • Mac: fixed keyboard not responding in registration panel in some host applications (LUNA, Garage Band...).
  • Mac: fixed demo version that could hang Logic when reloading projects using the plug-in.
  • Mac Audio Unit: fixed plug-in listing in some host applications (Plogue Bidule...).

V2.42 (2020/01/06)

New Features & Improvements:
  • Navigate presets and create new tones easily with "Tone Maps" for 9 built-in effects: Chorus, Flanger, Phaser, Wah, Sweep Filter, EQ, Freq Shifter, Reverb and Waveshaper.
  • Mac application now fully supports dark mode on Mac OS Mojave and newer.
  • New presets for the built-in wah plug-in.
  • Built-in EQ: improved impulse response convolution performance (long reverb tails are now supported, with low CPU usage).
  • Mac: faster GUI rendering on recent Mac OS systems (up to 5x faster for level meters).
  • Mac: fixed user interface not properly shown on retina displays in some applications built with the 10.14 Mac OS SDK (Cubase 10.5 for example).
  • Mac: fixed settings panel rendering issues in dark mode on Mac OS Mojave and newer.
  • Fixed issue with some VST3 plug-ins that failed to initialize when loaded (Roland Cloud VST3)
  • Fixed built-in Wah plug-in that could exceed selected range in reverse mode.

V2.41 (2019/07/23)

  • Fixed an issue with hosted plug-ins editors not always restored in the right position in Cubase on Windows.
  • Changing the slope of lowpass and highpass filters in the built-in EQ is now smoother.

V2.4 (2019/06/20)

New features:
  • New presets browser with built-in search.
  • Plug-in bypass and editor buttons can now be clicked on the entire button area (not just the icon).
  • MIDI Program Change preference is now saved into session instead of global preferences, so each instance can now use different MIDI channels. It is also saved in the user default preset.
  • VST3: added program change support for VST3 plug-in format.
  • VST3: added MIDI output support for VST3 plug-in format.
Built-in plug-ins:
  • New Level (volume control) and Micro EQ built-in plug-ins.
  • Added a gain parameter to several built-in plug-ins to avoid volume changes when switched on/off (pitch and frequency shifters, modulation effects, delays).
  • Increased knobs precision for pitch shifter and waveshaper built-in plug-ins for smoother control.
Third party plug-ins host:
  • VST and VST3 plug-ins previously displayed as missing because of name changes are now relocated automatically (Waves major updates, 32 and 64-bit plug-ins with different names etc.)
  • Improved auto-relocation performance when a large number of plug-ins have moved.
  • VST3 Host: added MIDI output and program change support for recenlty updated VST3 plug-ins.
Other fixes and improvements:
  • VST: the user interface is now properly resized in Cubase on Windows.
  • Fixed dry/wet mix knob only mixing left channel in mono to stereo configurations.
  • Mac: fixed issue with Magic Mouse that could trigger drag and drop instead of mouse click.
  • Built-in EQ plug-in spectrum analyzer display will not take priority over DAW or other plug-ins user interfaces.
  • Miscellaneous user interface performance improvements.

V2.31 (2018/12/06)

  • Spectrum analysis is now performed in the background and does not affect audio performance (built-in EQ).
  • Improved convolution performance for the impulse response loader on multicore processors (built-in EQ).
  • Fixed modulation plug-ins that did not always properly set rate when used in host sync mode (sweep filter, flanger, tremolo).

V2.3 (2018/10/22)

  • Drag and drop support (see our video):
    • drag and drop plug-ins between slots.
    • hold the alt key on Mac and Ctrl key on windows to copy (duplicate) a plug-in instead of moving it.
    • drop the plug-in before another to insert it in the chain.
    • drag and drop plug-ins between several instances of PatchWork or accross plug-ins (compatible with the latest preview of Late Replies, MB-7 Mixer and Axiom).
    • drag and drop .dll, .vst, .vst3, or .component files directly from the Finder or Explorer onto plug-in slots.
    • drag and drop .plgnfo files (previously saved from the software) directly from the Finder or Explorer onto plug-in slots.
  • Built-in EQ plug-in can now load and manipulate impulse responses (IR).
  • Fixed: effect tail not processed anymore when just inserted on a track (avoids using CPU when not necessary).
  • Fixed: built-in multitap delay plug-in could get out of sync in some host applications.
  • Improved performance of the built-in EQ plug-in.
  • Improved performance when saving preset/session with many built-in plug-ins.

V2.2 (2018/09/07)

  • Added 4 new built-in plug-ins (reverb, harmonizer, wah, mute).
  • New factory presets.
  • Major presets loading improvements: hosted plug-ins are now reloaded only when changed, and updated otherwise. Improves performance and audio rendering when loading presets using the same plug-ins.
  • Faster GUI loading / instantaneous GUI display after it has been opened once.
  • Performance and memory usage improvements.
  • Fixed: changing bypass in the Audio Unit version did not update host application's bypass state.
  • Fixed: bypass buttons are now in sync with the hosted plug-ins' state.
  • Win: fixed copy/paste that sometimes stopped working until next app restart.
  • Mac: fixed crash in Ableton Live when hitting space bar while a sub plug-in window is opened

V2.11 (2017/11/27)

  • Last loaded preset is now remembered in session and displayed in the presets menu.
  • Plug-in state can now be reverted to the last loaded preset.
  • VST3: factory presets are not exposed to the host application anymore - this fixes the problem of Cubase resetting the state of the instrument version upon session reload.

V2.1 (2017/11/09)

  • Added 25 new built-in effects borrowed from from Blue Cat's Late Replies: EQ, filters, pitch & frequency shifter, delays, modulation effects, compressor, gate, bit crusher, wave shaper and more.
  • 75 New presets using built-in effects.
  • The GUI can now be zoomed from 70% to 200%.
  • New option to keep plug-ins windows always on top.
  • Default preset now also saves the state of locks (when using "save as user default").
  • Load PatchWork into itself as a built-in effect.
  • Fixed host keyboard shortcuts lost when a sub plug-in is opened (in several host applications).
  • Fixed wrong number of channels used when hosted plug-in input set to manual and output to auto.
  • Fixed sub-plug-ins automation overwritten when using touch mode in some hosts.
  • VST2: fixed a crash in Wavelab.
  • Mac: new installer.
  • Mac: fixed minor compatibility issues with Mac OS High Sierra.
  • Windows: fixed plug-in windows not showing on displays on the left or above the main display.

V2.0 (2017/02/23)

  • Brand new GUI design, with improved usability and touchscreen support.
  • Now supports retina displays on Mac (text using high resolution).
  • Favorite plug-ins and their settings can be saved to be quickly reloaded later from a menu.
  • Unused channels for each hosted plug-in can now be muted (instead of default pass-thru).
  • Load/save native VST, VST3 or AU preset files.
  • Presets and parameters menus are now split in sub menus instead of a single list.
  • Additional user VST path to locate VST plug-ins is now available.
  • Missing VST & VST3 plug-ins are now automatically relocated.
  • Lock GUI state and in/out gains to prevent changes when loading presets.
  • Output gain is now always active, even when using a single PRE column.
  • Exclusive solo mode for parallel chains.
  • Show or hide all plug-ins editors with single click.
  • Hide plug-ins slots to minimize the plug-in.
  • Standalone application: drag and drop preset files on the application to load preset instantly on startup (and create shortcuts to launch app with a specific preset).
  • Now compatible with most recent Audio Units (Waves for example).
  • Changed demo limitations: up to 5 instances allowed, bypass time changed to half a second, and bypass parameter is not affected anymore.
  • Fully compatible with previous versions of the plug-in.
  • Dropped support for Windows XP and Mac OS X 10.6 and earlier.

V1.74 (2016/12/29)

  • Fixed MIDI channel issue with VST3: MIDI channel for note events was offset by one in the VST3 plug-in version and when hosting VST3 plug-ins.
  • Improved perfomance when loading presets.
  • Increased fine edit window width (opens when double clicking on a control).
  • VST: fixed random latency compensation issues upon project load or when loading plug-ins while not playing.
  • VST: fixed bypass issue when using reverse range in MIDI/automation settings.
  • (Mac AU) Fixed latency compensation issues in Logic, on project load, or when loading plug-ins while not playing.
  • (Mac AU) Fixed GUI display issues when changing size in Ableton Live.
  • (Windows) new graphics for Windows installer.

Warning: because of a bug of the initial VST3 release, this new version may not work with existing sessions that used the VST3 format. See this blog post for more details and how to fix it.

V1.73 (2016/05/10)

  • VST3 plug-ins hosting.
  • Fixed VST3 version crash in Wavelab 9.
  • Fixed issue with parameters precison in VST3 version.
  • Improved automatic I/O configuration for VST and VST3 versions.

V1.72a (2016/03/04)

  • (VST only) Fixed a crash when loading the VST version in Ableton Live.

V1.72 (2016/03/03)

  • VST3 plug-in format support, with improved external sidechain compatibility for Cubase and Nuendo.
  • Fixed a crash with some VST plug-ins using long preset names (SonicCharge Microtonic).
  • Windows: fixed a crash with some plug-ins that display a modal dialog when opened (Valhalla plug-ins).

V1.71 (2015/07/16)

  • Last loaded preset can now be saved directly from the presets menu without having to select the file.
  • VST: fixed latency compensation reporting in Cubase (no need to re-enable the plug-in to update the latency anymore).
  • AAX & RTAS: fixed feedback loop that could occur in bypass mode when the plug-in was inserted before another one.

V1.7 (2015/03/26)

New features:
  • The effect version now supports external side chain input.
  • The synth version now includes multiple output busses (up to 16 output channels).
  • The standalone application now offers up to 16 audio I/O.
  • Sub plug-ins audio i/o routing: connect the inputs and outputs of each plug-in to any channel.
  • Latency is now compensated for individual channels when a plug-in is processing only a subset of all available channels.
  • Fixed side chain input always fed with silence for some Audio Unit plug-ins.
  • Fixed issue with standalone application: displayed i/o were not reset properly when changing i/o configuration.
  • Fixed a crash with some VST plug-ins that use long preset names.
  • Fixed demo version popup window freezing Pro Tools in some situations.

V1.63 (2015/02/04)

  • GUI-less plug-ins support: a generic user interface is now provided for VST or AU plug-ins that do not include a graphical editor.
  • Presets can now be selected using MIDI Program change and bank select messages (can be activated with the presets menu/MIDI Program Change item).
  • Fixed issue with some Audio Unit instruments that did not produce any sound (IK Multimedia, Kontakt...)
  • Added log scale support for Audio Unit parameters.

V1.62 (2015/01/08)

  • New alternative light theme skin (light color scheme and lower contrast).
  • Factory and user skins can now be selected directly from the plug-in menu.
  • Added 192 kHz samplerate support to the standalone application.
  • Mac: fixed MFX Audio Unit that was not processing MIDI events properly.

V1.61 (2014/11/27)

Bug Fixes (Standalone application only - plug-ins unchanged):
  • Mac: fixed a crash when hitting the return key while changing the buffer, tempo or time signature.
  • Windows: improved audio drivers compatibility.
  • Windows: fixed a crash with some audio drivers on Windows 8, for the 64-bit application.

V1.6 (2014/11/25)

New Features:
  • Now available as a standalone application.
Fixes and compatibility improvements:
  • Improved presets and session load/save performance (up to 4 times faster in some situations).
  • Fixed issue with Izotope Audio Units that were configured as mono effects on stereo tracks.
  • Fixed crashes during auto save with Kontakt 5 in Pro Tools 11.

V1.5 (2014/10/20)

New Features:
  • The Audio Unit can now be loaded as a MIDI FX in Logic Pro X.
  • MIDI FX Audio Units can now be loaded into the plug-in.
  • Missing VST plug-ins can now be relocated if not found.
  • The plug-in now saves missing plug-ins' state so that they can be restored later.
Fixes and compatibility improvements:
  • Fixed issue on Mac when loading sessions created on Windows using VST plug-ins in sub-directories.
  • Fixing compatibility issues with several plug-ins that used to crash when unloaded (Image Line, MeldaProduction, Catanya...).
  • VST Plug-in name is now displayed when loaded from a missing VST shell bundle (instead of just the name of the bundle).
  • (Mac) Fixed randrom crashes when using keyboard shortcuts in the host application to switch between plug-ins or tracks.
  • (Mac) Fixed parameters not available for mapping when Audio Unit bridged with SoundRadix's 32Lives.
  • (Mac) Fixed parameters mapped with wrong range for some Audio Units (u-he, AAS...).
  • (Mac) Fixed parameter changes sent from host not visible in the user interface for some Audio Units (u-he...).

V1.4 (2014/07/24)

New Features:
  • Selectable parallel processing chains summing mode: sum or average.
  • Solo button for parallel chains.
  • MIDI Channel filtering for each plug-in input.
Fixes and compatibility improvements:
  • Fixed undo/redo incompatibilities with some plug-ins.
  • (Mac) Fixed crash introduced in 1.3 when trying to load missing VST plug-ins.
  • (Mac) Fixed wrong plug-in instantiated in some cases when selected from a VST shell package.
  • (Mac) Fixed crash after closing the editor of an Audio Unit plug-in loaded with SoundRadix's 32Lives.

V1.3 (2014/06/17)

New Features:
  • Audio Unit hosting support: Audio Units can now be loaded into the plug-in on Mac.
  • Plug-ins can now be cut from a slot for cut/paste operations.
  • Plug-ins can now be pasted into a slot with their params map.
  • User interface loading or resizing is now up to 50% faster.
  • Reduced the size of windows installers.
  • Minor layout changes.
Fixes and compatibility improvements:
  • Fixed undo/redo incompatibilities with some plug-ins.
  • (Mac) Fixed random crashes when unloading some plug-ins on Mac (Waves plug-ins for example).
  • (Win/AAX) Fixed shortcut to user manual in start menu.
  • (AAX) Fixed inaccurate transport information reported to sub plug-ins when stopping playback in Pro Tools.

V1.2 (2014/04/23)

New Features:
  • MIDI Routing: custom MIDI routes can be created to connect plug-ins together and with the host application to send and receive MIDI.
  • Plug-in instance Renaming: it is now possible to give a name to each instance of a plug-in.
  • Mono to stereo processing: the plug-in can now be used as a mono to stereo plug-in and process mono tracks with stereo effects in hosts that support it.
  • Improved performance of undo tracking when loading presets for plug-ins with many parameters.
  • The "Parameters Map" menu item is now checked when a parameter is mapped.
  • Improved performance when changing the size of the plug-in user interface.
Fixes and compatibility improvements:
  • Fixed keyboard stealing issue in many host applications when sub plug-ins editors are opened (except 32-bit applications on Mac).
  • Fixed compatibility issue with Pro Tools 9 on Mac (random crashes).
  • Fixing crashes with some plug-ins requesting information while being opened.

V1.1 (2013/12/18)

New Features:
  • New parameters mapping feature for sub plug-ins automation (includes a "learn" mode for easy mapping): Up to 40 parameters can be mapped to external controls. Our plug-in's advanced automation and MIDI control features can also be used to map controllers to sub-plug-ins parameters.
  • New layout to display mapped automation controls in the main user interface.
  • Added phase flip buttons for each parallel chain, so that you can easily compute differences between signals or correct phase problems introduced by some plug-ins.
  • Link all pre and post gain knobs so that pre gain changes are automatically compensated by the post gain knobs. This can be used to easily push dynamics or distortion plug-ins without increasing the volume.
Fixes and compatibility improvements:
  • when no plug-in is inserted, level meters remained frozen when stopping transport.
  • fixing crashes with GRM Tools plug-ins that changed their audio I/O count dynamically ("Reson" for example).
  • fixing sample rate initialization issue with Nebula when using copy/paste.
  • The plug-in can now be used as a virtual instrument in Cubase and Studio One (it used to be silent).
  • Some plug-ins that required the deprecated "effIdle" VST message should now work properly (Steinberg's Virtual Guitarist for example).

V1.01 (2013/11/22)

Fixes and compatibility improvements:
  • Improved compatibility with plug-ins that do not support sample rate changes (Nebula).
  • Improved compatibility with synths that internally use VST presets banks: the entire state was not properly restored with the session (Nexus or Korg Legacy series).
  • Fixed output gain compensation issue: when using parallel chains, the global output gain stage was skipped.

V1.0 (2013/11/12)

First release.

Thanks again for choosing our software!

See you soon on!