Legacy RackAFX6 & 1st Edition Book Projects

Although I no longer support RackAFX Classic (aka RackAFX6), I am still making it available for download for people with the original FX book or the 1st edition synth book.

RackAFX7 is the next evolution of the product, which massively cleans stuff up and brings the software into the C++11 and beyond extensions. It is super simple to use and exports projects in the new ASPiK format.

Get the latest version of RackAFX7 here: RackAFX7 Installer

Download 1st Edition FX Book Projects

You can download the old 1st edition FX book projects here: 1st Ed FX Projects

Download RackAFX

RackAFX runs on Win7, Win8, and Win10. It has been tested with Parallels, Virtual Box and Boot Camp on MacOS with no issues or problems. In addition to RackAFX, you will also need:
– Visual Studio 2015 or 2017
– a Windows compliant sound adapter; native ASIO drivers are preferred
– VS2015 Redistributables Installed on your computer (see below)
– CMake installed for exporting projects a AAX, AU and VST
– MacOS 10.12 or higher and XCode 8.x or higher (for MacOS exported projects)

Last Supported Release: v6.9.3.0

RackAFX Installer: RAFX v6.9.3.0 Installer

  • VST SDK: 3.6.10
  • AAX SDK: 2p3p0
  • AU SDK: Version 2.0, 2016-02-19


You will need to install CMake on your Windows and MacOS partitions to export your plugin projects as AAX, AU and VST. You can get CMake here: https://cmake.org/

You can read about why I’ve adopted CMake as well as the instruction for using it in the technical notes here:
Technical Note 8A: Introduction to CMake

Technical Note 8B: Exporting Projects

Technical Note 8C: Using CMake

Preparing Visual Studio:

The v6.8+ releases of RackAFX fixes an issue that came up when Microsoft changed some shortcuts in Visual Studio 2013. To setup your version of Visual Studio to receive the remote Rebuild command from RackAFX follow the easy instructions here:
Setting up Visual Studio for Remote Rebuilding
This is the simplest way to use RackAFX + Visual Studio as the Rebuild command will also automatically unload your DLL, preventing compiler errors that the DLL can’t be written.

Release Notes v6.9.3.0:

– fixed AU export problem with additional User Meters
– fixed VST export issue with MIDI events
– reopen your project and let it do the “6.9.3.x AU update” then you can re-export your projects to get the AU and VST fixes.

Release Notes v6.9.2.0:

– fixed issue with AU exporting for synth plugins
– updated to VST3 SDK 3.6.10 (current version)
– fixed issue with using Windows mapped drives
NOTE: this version requires that you update the VST3 3.6.10 SDK if you want to export VST2/3 plugins
The VST3 SDK includes the latest version of VSTGUI4 however, all ported projects will work
with either the older VSTGUI 4.5 or the new VSTGUI 4.6 folder inside the “myprojects” directory
where you store your exported projects.

Release Notes v6.9.1.0:

– fixed issue with AU automation when recording directly from GUI controls
– updated to VST3 SDK 3.6.9 (current version)
– updated to VSTGUI 4.6 (current version)
NOTE: this version requires that you update the VST3 SDK if you want to export VST2/3 plugins
The VST3 SDK includes the latest version of VSTGUI4 however, all ported projects will work
with either the older VSTGUI 4.5 or the new VSTGUI 4.6 folder inside the “myprojects” directory
where you store your exported projects.

Release Notes v6.9.0.9:

– fixed lockup issue when using the “Classic” GUI front end
– fixed issues with presets and Copy UI Controls From (other) Project
– fixed duplicated meters when copying UI controls repeatedly
– fixed issue with meter preset when value is NaN (from incorrect meter calculation in plugin)
– fixed duplicated “#include ” statements

Release Notes v6.9.0.8:

– fixed issue with .RC files when exporting projects with custom graphics files (thanks Ted!). Note this is for Visual Studio projects only (MacOS/Xcode exports are not changed and are already properly exporting the PNG files)

Release Notes v6.9.0.7:

– fixed issue with new project/GUI control

Release Notes v6.9.0.6:

– discontinued support for Visual Studio 2013
– updated to VST3 SDK 3.6.8 (current version)
– updated to VSTGUI4.5 (current version)
– changed project export paradigm to use CMake for VS and XCode project generation
– removed Make AAX, Make VST and Make AU functions; consolidated into one Export Project function
– NOTE: see the tutorial videos and the readme.txt file within your exported projects for help
– AAX: added latency support for older versions of Pro Tools
– AAX: added native PT downward gain meter support (you must connect the meter yourself)
– VST3: updated SDK and shrunk files
– AAX/AU/VST: project folder locations have been moved to the SDK root folder and may easily be customized by editing the top level CMakeLists.txt file
– VSTGUI4: you will need to install the vstgui4 subfolder into your exported project outer folder (named “myprojects” in the demo videos) – you can now install the latest version (4.5) from the RackAFX Utilities menu to any location you choose.


v6.9.0.6 uses the latest AAX SDK 2p3p0 and VSTGUI 4.5 (you can install the VSTGUI 4.5 folder with Utilities -> Install VSTGUI 4.5) into your “myprojects” folder in the AAX SDK.


Microsoft have confirmed a bug in Visual Studio 2017 that I reported which involves using VS2017 on a computer that does not have VS2015 installed on it (or had VS2015 installed and then removed). When opening an older VS project, you get a message that states that the Target OS and ToolSet will be upgraded; after the upgrade, the Target OS will still be incorrectly set to Win8.1 – without the VS1015 installation files, this project will not compile. The same is true of book projects and new RackAFX projects which have no Target OS setting; instead of setting the new Target OS to Win10.0, it defaults back to Win8.1 and creates the same problem. Microsoft asks that we remain patient while they fix this… but in the meantime, you can work around the bug by manually retargeting old and new projects alike; in the Solution Explorer, right-click on the Solution and choose Retarget SDK Version, then choose 10.0.xxxx.y (there may be multiple versions – if so, choose the latest version).


RackAFX v6.9.0.6 requires the latest VST3 SDK v3.6.8 – see the video tutorials or read the technical notes about the use of CMake. Your ported project folder will be located at the top level of the SDK root. RackAFX no longer requires that you “prepare the SDK” as with the previous version. Your VST3 ported project will build its own base (and other) libraries at compile time and link properly with them when you build.

The newest SDK v3.6.8 is available here: https://www.steinberg.net/en/company/developers.html

You still need to enable the VST2 portion of the SDK manually (Steinberg disables it by default) and this is very easy to do. Follow the instrucitons here: Enable VST2 in VST3 SDK

Windows C Runtime (CRT)

See the Forum note here about the new dynamic linking to the Windows CRT in v6.9 and later (for Visual Studio exported projects only):

VS2015 Redistrubutables:

If you do NOT have VS2015 installed on your computer, you need to install the VS2015 redistributables (RAFX is now compiled with VS2015). For 32-bit systems, only install the 32-bit redistributables; for 64-bit, install both redistributables. Also, you should manually restart your computer after installing the redistributables.

32-bit: 32-bit Redistributables

64-bit: 64-bit Redistributables

Keyboard Modifiers

v6.8.1.9 fixes all issues with key modifiers for VST, AU and AAX so that the specified combinations work correctly for each API paradigm. For example, in Pro Tools, CTRL-ALT-CMD and clicking on a control pulls up the automation window. The proper fine-adjust and go to default value have also been fixed to work properly for each API paradigm:

Fine Adjustment:

– AU: SHIFT + drag mouse
– AAX Mac: CMD + drag mouse
– AAX Win: CTRL + drag mouse
– VST Mac: SHIFT + drag mouse
– VST Win: SHIFT + drag mouse

Go to Default Value:

– AU: ALT + left click mouse
– AAX Mac: ALT + left click mouse
– AAX Win: ALT + left click mouse
– VST Mac: CMD + left click mouse
– VST Win: CTRL + left click mouse

v6.8 Release Notes

v6.8 Release Notes

Previous RackAFX Release Version: (old main UI graphics)

RackAFX Installer: RAFX v6.6.4.1 Installer

Visual Studio

To use RackAFX, you will need a Visual Studio compiler. Currently, the best performing compiler is Visual Studio 2015 Community. RackAFX currently supports:

VS 2015
VS 2017

Make sure you download and install the proper Visual Studio compiler that includes Visual C++ (sometimes they name it “… for Windows Desktop”).

Download VS2015 Here: Visual Studio 2015 Community