Download RackAFX

RackAFX runs on Windows XP, Vista, 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 2013, 2015, or 2017
– a Windows compliant sound adapter; native ASIO drivers are preferred
– VS2015 Redistributables Installed on your computer (see below)


Current Release: v6.8.2.0

RackAFX Installer: RAFX v6.8.2.0 Installer

Preparing Visual Studio:

The v6.8 release 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.8.2.0:
– fixed bug with VU meters in AAX plugins

Release Notes v6.8.1.9:
– fixed bug with not remembering VS2017 exe path
– updated to VSTGUI v4.4
– VSTGUI zoom factor set to 10 for fine adjustments with SHIFT + Mouse Drag
– Save Project As… changed to Backup Project (see below)
– [Make AAX]: updated for SDK 2p3p0 + VSTGUI 4.4
– [Make AAX]: updated all modifier buttons for proper Pro Tools functionality (CTRL-ALT-CMD for automation, ALT + MouseClick for control default, etc…)
– [Make AU]: updated for proper modifier with ALT + MouseClick for control default
– MacOS: all MacOS targets tested with MacOS 10.12.6 and Xcode 8.3.3


Save Project As…

This feature has been renamed to Backup Project, and no longer attempts to parse your Visual Studio project to create a new one with a different name; instead it backs up your current project to a new folder, keeping everything intact. If you want to change the Visual Studio project name of the backed-up project, it is simple – just change it in the Solution Explorer (slow double-click to edit, or right-click and choose Rename).



v6.8.1.9 uses the latest AAX SDK 2p3p0 and VSTGUI 4.4 (you can install the VSTGUI 4.4 folder with Utilities -> Install VSTGUI 4.4 and then copy the folder into your Example Plugins folder in the AAX SDK.


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



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).



If you are planning on using the Make VST functionality, you will need the VST3 SDK version 3.6.6 or 3.6.7 to work properly with RackAFX You choose the SDK when you use the Make VST function. Due to changes the developers made in Version 3.6.7, you are now required to prepare the SDK for use. I’ve created an easy way to do this with instructions available at Please note that this additional step is not due to RackAFX, but to changes made at Steinberg and affects anyone using the SDK. Other changes also break the 3.6.6 projects due to the developer’s deletion of several VST3 objects needed for Presets (don’t worry, Make VST for 3.6.7 includes the necessary changes for Preset support). If you have projects in 3.6.6, you may wish to keep this SDK intact for those projects.

Future versions of RackAFX will discontinue support for out of date VST3 SDKs, so you will eventually need to upgrade to the latest version. Steinberg has removed the 3.6.6 SDK from the developer portal, but for the time being you can get it here:

The newest SDK v3.6.7 is available here:


For RackAFX v6.6.4.1 Users:

Backup all old RackAFX projects prior to using v6.8; due to the new underlying RackAFX API thread safety changes, project folders/files will *NOT* be backward compatible. You will need your backed up projects if you want to revert to v6.6.4.1


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


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 2013 (support will eventually be discontinued for VS2013 so please upgrade to a newer compiler when you get a chance)
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