We are glad to unleash the first episode of a video series about Blue Cat’s Destructor in the studio: Eli Krantzberg will show you how he uses Destructor to record and mix guitar parts for a TV underscore cue he is working on.

Guitar connected straight into the box, the chase for the perfect guitar tone can begin! As you will see, it is as simple as picking up a few presets and tweaking them to your taste.

In today’s episode, Eli is exploring a few clean guitar tones to record rhythm parts, check it out!

One Single Price for All

With the increase of individuals purchasing on our store and since the USD/EUR rate is now getting close to 1, we have decided to simplify the shopping experience on the bluecataudio store: all prices are now identical in USD and EUR, and wherever you live in the EU (VAT is included in the fixed public price).

Prices Remain Almost the Same

These modifications might induce very small price changes compared to the previous policy, depending on the products and your country of residence, but there is no major impact on pricing, don’t worry!

Of course, if you are a business within the EU (and outside of France), VAT can still be deduced upon purchase.

If you are using multiple machines or if you want to transfer your plug-ins quickly to a new PC without having to register your all your Blue Cat Audio plug-ins again and setup your preferences, here is the solution.

Note: this transfer step should be done BEFORE installing the plug-ins using the installers downloaded from your private download page.

On Windows, Blue Cat Audio plug-ins preferences and license files are stored in the Application Data roaming folder located in the user directory. This folder a hidden and usually cannot be opened from the Explorer directly. You can however access it by typing its path in the Explorer:

type your actual user name instead of [YOUR USERNAME]

You will find a Blue Cat Audio folder in this directory. It contains all preferences and license files for all Blue Cat Audio plug-ins:

To transfer all licenses and preferences to your new machine, simply copy and paste the Blue Cat Audio folder from the source machine to the destination one (in the user AppData/Roaming directory).

“Voilà”! Just install the plug-ins on the new machine and use them without having to register them individually!

Note: If you want to select just a few plug-ins, you can copy and paste each plug-in directory, one by one. In this case, you will notice that preferences are stored separately for each plug-in format (VST, AAX, RTAS or AU) in a directory named “BC [PLUGIN NAME] [PLUGIN FORMAT]”, while (for most plug-ins) a single license file (.lic) is shared by all formats in a directory named Blue Cat’s [PLUGIN NAME].

This tutorial also applies to multiple users on a single machine: you can transfer preferences and licenses to a different username on the same machine by moving the same files.

Map Plug-In Parameters

The first step is to select the parameters you want to control from the outside, using the Params Map function, as explained in details in the manual:

Mapping parameters of plug-in hosted in PatchWork

Mapped parameters will appear at the bottom of the PatchWork or MB-7 Mixer GUI, if “Show Assigned Controls” is enabled (icon with 3 knobs in the toolbar):

Mapped Parameters

PatchWork’s parameters called “Control 01” and “Controls 02” are now mapped to the “Drive” and “Mix” parameters of the hosted Destructor plug-in. It means that you can use the PatchWork parameters to change the corresponding plug-in’s parameters and vice versa.

Automate PatchWork Controls

You can now automate the PatchWork controls in Pro Tools (“Control 01” and “Control 02” in this example) – they will control the mapped parameters of the hosted plug-in(s):

Enable automation for the Mapped Parameters in Pro Tools

Record and Replay automation as if the sub-plugin was hosted in Pro Tools.

Despite all our efforts, sometimes bugs are not caught before the software is released, and this one has an impact on VST3 users on Mac, so we’d like to share more information about it with you, so that you can avoid major problems. If you are on Windows or do not use VST3, you don’t need to read this!

The Bug

We have noticed a bug on the first release of our VST3 plug-ins that affect the Mac versions: the identifier for the plug-ins (used by host to identify a particular plug-in) were not properly reported to the host on Mac.

The consequence was that the plug-ins inserted in sessions created on Mac would not be reloaded on Windows and vice-versa.

The Fix

We are now progressively releasing new versions of our plug-ins with a fix for the wrong ID on Mac (see impacted products list below). But this means that older sessions will not reload the new versions of the plug-ins, as they are seen by the host as a different plug-in.

How To Open Old Sessions

So here is a way to open older sessions without losing any plug-in data. You can then migrate these sessions quickly to use the new version of the plug-in so that they are future-proof.

The idea is just to install the old and new versions side by side, so that older sessions are reloaded with the older version of the plug-in (which would be missing otherwise). Renaming the old plug-in before installing the new version will do the trick:

Open the VST3 plug-ins directory

Rename old plug-ins (for example with “Legacy” at the end, but do not change the extension (vst3)

If the plug-in has multiple versions (Synth, Dual, Mono etc.), do not forget to rename them all. Once you are done, install the new version. Both should now be available, side by side:

Side by side installation

You can now open the existing sessions: the “legacy” version of the plug-in will be loaded, keeping the sessions unchanged.

How To Migrate to New Versions:

Since you probably do not want to keep both versions side by side forever, you can quickly migrate existing sessions so that they use the new plug-in in the future, instead of the old version:

Open the legacy plug-in in the session and copy its state

Replace the legacy plug-in with the new one and paste the state.

Voila! The old plug-in is replaced by the new one, with the exact same state.

Impacted Products

So far, the plug-ins impacted by this change are the Mac VST3 versions of the following plug-ins:

Blue Cat’s PachWork, between version 1.73 and 1.74 (also affects migration from 1.73 or earlier to version 2).

Blue Cat’s MB-7 Mixer, between version 2.53 and 2.54 (also affects migration from 2.53 or earlier to version 3).

Other VST3 plug-ins that are not listed above still have the Mac-Windows compatibility issue, except for Blue Cat’s Destructor that was released with the fix from the very first version.