In this tutorial we will show you how to create AAX plug-ins quickly, right from inside Pro Tools or Media Composer. Continue reading
With the release of Blue Cat’s Plug’n Script v3 and its ability to export VST, VST3 or Audio Unit plug-ins, the support for native (compiled) scripts, you might be wondering who this software has been built for. Is it now only targeted to software developers?
Today we are looking at who we had in mind when designing this very particular plug-in.
But first, as a preamble, let’s answer a key question many people have been asking over the years: Continue reading
Initially released in 2014 to add scripting capabilities to your favorite DAW, Plug’n Script has evolved into an integrated audio plug-ins development environment: native (compiled) scripts have been supported since 2015, and version 3.0 brings all the pieces together with a brand new workflow and VST plug-in export capabilities.
Let’s see in details what this new version brings to the table! Continue reading
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!
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.
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:
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:
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:
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).
- Blue Cat’s Plug’n Script, between version 2 and 3.0.
- Blue Cat’s Chorus, between version 4.2 and 4.3.
- Blue Cat’s Flanger, between version 3.2 and 3.3.
- Blue Cat’s Phaser, between version 4.2 and 3.3.
- Blue Cat’s FreqAnalyst, between version 2.2 and 2.3.
- Blue Cat’s Triple EQ, between version 4.2 and 4.3.
- Blue Cat’s Gain Suite, between version 3.2 and 3.3.
- Blue Cat’s Dynamics, between version 4.1 and 4.2.
- Blue Cat’s Protector, between version 2.1 and 2.2.
- Blue Cat’s DP Meter Pro, between version 4.1 and 4.2.
- Blue Cat’s FreqAnalyst Multi, between version 2.2 and 2.3.
- Blue Cat’s Oscilloscope Multi, between version 2.2 and 2.3.
- Blue Cat’s StereoScope Multi, between version 2.2 and 2.3.
Other VST3 plug-ins that are not listed above still have the Mac-Windows compatibility issue, except for Blue Cat’s Destructor, Late Replies, Axiom and Re-Guitar that were released with the fix from the very first version.
This bundle combines our most powerful tools to customize your virtual studio and build the ultimate audio toolbox: yours.
Let’s have a look at its content and what it can be used for! Continue reading
We are happy to announce the release of Blue Cat’s Plug’n Script 2.0.
This new version brings many improvements, such as an extra side chain input and multiple auxiliary outputs, native scripts support and enhanced user interface with the KUIML 2.0 programming language. It also includes several new scripts, presets and skins.
Let’s have a deeper look at this new release and what it can do for you! Continue reading
Did you know that you can use AAX plug-ins as MIDI Effects in Pro Tools? AAX plug-ins can receive MIDI events, modify them, and send them to another plug-in. Yes, it’s possible!
As an example, let’s see how to apply a simple MIDI effect on incoming MIDI events to control a virtual instrument. We are using here Blue Cat’s Plug’n Script, a plug-in that lets you write your own audio and MIDI scripts, for both the MIDI effects and the virtual instrument:
- Create an Instrument track with the virtual instrument that will receive MIDI events
- Add the MIDI effect on the same instrument track (in a slot before the virtual instrument)
- Create a MIDI track to route events from the MIDI input to the MIDI effect.
- Create a MIDI track to route events from the MIDI effect to the virtual instrument
- Arm both tracks for recording
Using the setup above, you can play “live” the instrument and record the performance on the MIDI track. Once this has all been recorded, an extra step is required before playback, because events will have been recorded twice (the original MIDI events on the first track, and the MIDI events after the MIDI FX on the other track):
- Remove MIDI events that have been recorded on the second MIDI track (events transformed by the MIDI effect).
- The first MIDI track does not need to be armed for recording (it will just play recorded MIDI events), but the second track that route events from the effect to the virtual synth has to, so that Pro Tools actually routes the events.
- Hit play: the MIDI effect is applied to recorded MIDI events and control the synth!
As you may have understood, if you want to use many MIDI effects at a time, making connections and enabling/disabling monitoring with all these additional MIDI tracks can become frustrating. So if you want to make things simpler, you may want to do all MIDI routing inside Blue Cat’s PatchWork. This does not limit you to VST or Audio Unit virtual instruments, since the PatchWork plug-in lets you route MIDI events to its own AAX MIDI output, but you should be able to use just a single MIDI track instead of many, if you want to chain MIDI effects.