How To Make A VST, Audio Unit or AAX Plug-In, In 20 Minutes!

Have you ever wondered how you could create your own audio or MIDI plug-ins, without headaches, deep knowledge of C, C++, compilers and linker errors?

Ilya Orlov (also known as “Letimix”), developer and creator of fantastic tools for Plug’n Script, explains you everything you need to know to get started with Plug’n Script and create your own plug-in easily.

Within 20 minutes, with these two video tutorials, you should be able to write your first dsp scripts and export a plug-in of your own, check them out!

Looking for more more in-depth tutorials and tips and tricks to write your own plug-ins? Please visit the Letimix Plug’n Script page: it is great source of information for audio plug-ins development!

>discuss this topic in the forum

How To Create AAX Plug-Ins For Pro Tools And Media Composer

With Plug’n Script 3.2 you can now export your audio and MIDI plug-in creations as AAX plug-ins that can be loaded directly into AVID’s Pro Tools or Media Composer on both Mac OS and Windows.

In this tutorial we will show you how to create AAX plug-ins quickly, right from inside Pro Tools or Media Composer. Continue reading

Why Would You Need A Scripting Plug-In Inside your DAW?!?

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

Plug’n Script V3 – What’s New?

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

VST3 Plug-In ID Changes on Mac

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:

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

Blue Cat’s Crafters Pack: The New Bundle for Creative Minds

Blue Cat's Crafters PackThe release of Blue Cat’s Plug’n Script 2.0 is also the opportunity for us to unleash a new bundle: Blue Cat’s Crafters Pack.

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

Blue Cat’s Plug’n Script 2.0 Is Out!

mainWe 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