Reference 4 plugin does not show up in DAW

The plugin should show up in your DAW as Sonarworks Reference 4. If you can't see it, please try relaunching your DAW/restarting your computer (suggested for macOS) and/or rescanning your DAW's plug-in list.


NB Reference 4 supports VST2, AAX, RTAS (Windows), and AU (MacOS) plug-in formats


Please make sure that your DAW is scanning the correct locations for your plug-ins. Reference 4 plug-ins will be installed in the following directories: 




C:/Program files/VSTPlugins/Reference4_x64.dll

C:/Program files(x86)/VSTPlugins/Reference4_x86.dll


C:/Program files/Common Files/Avid/Audio/Plug-Ins/Reference4.aaxplugin

C:/Program files(x86)/Common Files/Avid/Audio/Plug-Ins/Reference4.aaxplugin


C:/Program files(x86)/Common Files/Digidesign/DAE/Plug-Ins/Reference4.dmp




/Macintosh HD/Library/Audio/Plug-Ins/Components -> Sonarworks Reference 4 plugin.component


/Macintosh HD/Library/Application Support/Avid/Audio/Plug-Ins/Sonarworks Reference 4 plugin.aaxplugin


/Macintosh HD/Library/Audio/Plug-Ins/VST/Sonarworks Reference 4 plugin.vst



Legacy Software:

Reference 3 plugins are displayed as "Sonarworks Reference 3".

Was this article helpful?

16 out of 132 found this helpful

Have more questions? Submit a request



I need to install the VST to a custom folder (C:/Program files/Common Files/vst/) because that's where my Ableton Live looks for VST2 plugins and where all my other plugins are installed. During the installation I click customize and browse to that folder, but the VST is still installed to the default location (C:/Program files/VSTPlugins/) which means Ableton Live can't find it since it only lets you set up one VST2 plugin folder.


Hi everyone! 


Just a quick heads up on anybody else getting stuck with this problem: Rickard's case was resolved by uninstalling the previously installed VST version, and then reinstalling again using the custom location option in the installer (see the screenshot below).


We are not exactly sure what caused the problem - probably the installer automation of assigning the previously installed location was triggered for some reason, that way discarding the assigned custom location. Getting rid of the originally installed VST fixed it, and from there, the custom location option did the trick! 



Please sign in to leave a comment.