# 7. Mac - Installed Plugins not shown in the Plugin List

<span data-identifyelement="471" dir="ltr">The MP host will read the plugin files but not do an in-depth scan like the DAW, so it only takes a few seconds:</span>

- <span data-identifyelement="476">the AU plugins in /Library/Audio/Plug-Ins/Components </span>
- <span data-identifyelement="478">the VST2 plugins in /Library/Audio/Plug-Ins/VST</span>
- <span data-identifyelement="480">the VST3 plugins in /Library/Audio/Plug-Ins/VST3</span>

<p class="callout info"><span data-identifyelement="485" dir="ltr"><span data-identifyelement="473" dir="ltr">scanning will read and display just the filenames at first, and fully scan a plugin once you choose to load/use the plugin</span></span></p>

<span data-identifyelement="485" dir="ltr">If the VST3 plugins are not shown in the MP Host list, navigate to the host.properties folder and rename it or delete it.</span>

<span data-identifyelement="487" dir="ltr">Close any MP Host instances you have running and the DAW.</span>

<span data-identifyelement="491" dir="ltr">Then reset the permissions on the VST3 folder by running in the Mac terminal:</span>

<div data-identifyelement="492" id="bkmrk-sudo-chmod--r-777-%2Fl"><span data-identifyelement="493" dir="ltr">*sudo chmod -R 777 /Library/Audio/Plug-Ins/<wbr data-identifyelement="495">VST3/</wbr>*</span></div><div data-identifyelement="496" id="bkmrk-enter-your-password-"><span data-identifyelement="497" dir="ltr">enter your password and hit enter. It should not produce any output on the terminal.</span></div><div data-identifyelement="498" id="bkmrk-then"><span data-identifyelement="499" dir="ltr">Then</span></div><div data-identifyelement="500" id="bkmrk-sudo-chmod--r-777-%2Fl-1"><span data-identifyelement="501" dir="ltr">*sudo chmod -R 777 /Library/Audio/Plug-Ins/<wbr data-identifyelement="503">VST3/\*.vst3</wbr>*</span></div><span data-identifyelement="505" dir="ltr">enter your password and hit enter. It should not produce any output on the terminal.</span>

<span data-identifyelement="505" dir="ltr">Then run in the terminal:</span>

*<span data-identifyelement="505" dir="ltr">sudo chown -R "$(whoami)":staff "/Library/Audio/Plug-Ins/Components"  
sudo chown -R "$(whoami)":staff "/Library/Audio/Plug-Ins/VST3"  
sudo chown -R "$(whoami)":staff "/Library/Application Support/Avid/Audio/Plug-Ins"</span>*

<div data-identifyelement="508" dir="ltr" id="bkmrk-and-hit-enter.-it-sh"><span data-identifyelement="509" dir="ltr"><span data-identifyelement="505" dir="ltr">and hit enter. It should not produce any output on the terminal.</span></span></div><div data-identifyelement="508" dir="ltr" id="bkmrk-"></div><div data-identifyelement="508" dir="ltr" id="bkmrk-then-reopen-the-mp-h"><span data-identifyelement="509" dir="ltr">Then reopen the **MP Host Audio FX plugin** and click on the Plugin List button and choose Quick Scan at the bottom. It should show all the VST3 and AU plugins in the plugin list.</span></div><span data-identifyelement="512" dir="ltr">As you may have noticed it has generated a new host.properties file.</span>

<span data-identifyelement="516" dir="ltr">For more information please see [this article](https://kb.mpmidi.com/books/mp-controller-documentation/page/5-finding-your-existing-third-party-plugins) on how the MP Host scans and finds plugins.</span>

<p class="callout warning"><span data-identifyelement="521" dir="ltr">Plugins also may be removed from the plugin list (after you scan or try to try to load them once) if they are not universal binaries (Apple Silicon ARM and x86). You can find if a plugin is built for both architectures by running lipo -info PLUGIN\_PATH in a terminal  
</span><span data-identifyelement="523" dir="ltr">For example: *lipo -info /Library/Audio/Plug-Ins/<wbr data-identifyelement="525">VST3/reverbA.vst3</wbr>*</span></p>

---

<div id="bkmrk-macos-plugins-in%C2%A0%7E%2Fl"><span dir="ltr">**MacOS Plugins in ~/Library/ and /Library/** </span></div><span dir="ltr">It is possible to </span><span dir="ltr">have the plugins in the user Library as well.</span>

<span dir="ltr">This may result in duplicate plugins.</span>

<div id="bkmrk-check-this-location%3A">Check this location: **<span dir="ltr">~/Library/Audio/Plug-Ins/</span>**</div><div id="bkmrk-if-you-have-plugins-">if you have plugins here delete them or move them to:</div><div id="bkmrk-the-correct-location">The correct location is **<span dir="ltr">/Library/Audio/Plug-Ins/</span>**</div>---

##### **<span data-identifyelement="529" dir="ltr">Force Ableton Live to find new plugins on MacOS and Windows</span>**

<span data-identifyelement="531" dir="ltr">If you have a large number of plugins and Ableton does not show the new version of the MP Host try the following methods:</span>

##### 1. Rescan Plugins in Ableton Live:

- Open Ableton Live.
- Navigate to `Live` &gt; `Preferences` (or `Options` &gt; `Preferences` on Windows).
- In the Preferences window, go to the **Plugins** tab.
- Click the **Rescan** button to force Ableton to rescan the plugin folders.

##### 2. Clear Plugin Cache Manually:

- On macOS, the cache files are located in: 
    - `~/Library/Preferences/Ableton/Live x.x.x/`
- On Windows, the cache files are in: 
    - `C:\Users\[Your Username]\AppData\Roaming\Ableton\Live x.x.x\Preferences\`

Inside these directories, locate and delete the file `PluginScanV2` (this file holds cache data for your plugins).

##### 3. Rescan AU/VST if Using macOS (for Audio Units only):

- If you're using Audio Units (AU), resetting the cache may also involve rescanning AU plugins: 
    - Open a Terminal and run the following command: ```
        killall -9 AudioComponentRegistrar
        ```

This will force the macOS to reload the list of installed AU plugins.

After these steps, Ableton Live should detect the new versions of your VST plugins properly.