About these files

Mirage is the VST/AU engine that powers some of our products, such as Wraith or Phoenix. These downloads are for that engine – they do not contain any libraries, just the Mirage engine plugin files, and sometimes presets. You can find more information on what Mirage is here.

These are pre-release versions. This means they might not be ready for production yet. There might be bugs. Your help in testing these versions is very much appreciated.

How to check what version you are running

Please verify that you are using the latest version by clicking on the gear icon at the top of Mirage’s GUI, and then selecting ‘About’. The version there should match the version that you have just downloaded. If not, please have a look at the following paragraphs.

What to do if the version is not up-to-date

The Mirage installers have the version displayed on them. Please double-check the version is the right one. If not, grab a new file using the buttons on this page and run it.

If the installer version is correct too, your DAW might somehow be loading the old version. In which case you might have to manually remove the old files. This is not really relevant on Mac as the installer does not let you pick an install location.

However, on Windows, you might have chosen custom locations to install the VST files. In this case, it is important to pick those same locations again so that the installer can overwrite the files. If you cannot remember the locations you chose before, or want to remove Mirage for another reason you can follow the steps below for manual uninstallation.

How to manually uninstall Mirage

This should almost always be unnecessary since running a new installer will overwrite the old Mirage files (if the same installation location was chosen). To account for the edge cases, the manual uninstallation steps are given below.

On Windows, Mirage installs 2 files. These are VST plugin files. One for 32-bit applications and one for 64-bit applications. These files are called mirage32.dll and mirage64.dll. The default location for these is ‘C:/Program Files (x86)/VSTPlugins’ and ‘C:/Program Files/VSTPlugins’. However, if you chose another location when installing Mirage, they will be found there. Simply delete these files to uninstall Mirage.

On Mac, Mirage also installs 2 files. The first is a VST plugin file called Mirage.vst. This can be found in /Library/Audio/Plugin-Ins/VST. The other is the AudioUnit (AU) plugin file called ‘FrozenPlain Mirage.component’. This is found in /Library/Audio/Plug-Ins/Components. Deleting these files will remove Mirage from your Mac.

If your DAW is showing an old version or Mirage even though you have just installed a newer one, you can look in your DAW settings, often DAWs search in multiple locations for plugins. The old version of Mirage must be in one of those locations in order for the DAW to have found it.

Where to find debug log files

In the case of a bug or crash, you might be asked to send log files. These are files that log what Mirage is doing. They can be very helpful in diagnosing and fixing problems. They can be found in your Documents, and then in the folders ‘FrozenPlain/Mirage/Logs’. There might be multiple log files there. They are all useful to send.

If they cannot be found there, then there is a fallback location for them. On Windows, this is the root of your C: drive. For example C:/Mirage_Log_VST.txt.

On Mac, this is your ‘/tmp’ folder. This is a hidden folder. To find it, open Finder and navigate to MachintoshHD. Then you need to show the hidden folders. This is done by pressing Cmd+Shift+. (period). You should see many folders appear, including one called tmp. You can press that key combination again to hide the folders when you are done. The Mac installer also writes its log file to this tmp folder.