Plug-ins Tips and Troubleshooting

When using third-party plug-in devices in Ableton Live, install and update them as recommended to avoid crashes, slow performance, and audio interruptions. 

This guide answers these frequently asked questions:

How to avoid the most common plug-in issues:

  • Keep all third-party software up to date. Outdated plug-ins are very often the cause of crashes and performance issues. Use the relevant plug-in manager app or check the developer's website frequently for updates and compatibility info.
  • Uninstall outdated devices. Use the plug-in manager to completely remove previous versions and incompatible plug-ins from your computer. Keep track of what you have installed in plug-in locations on Windows and macOS.
  • Install plug-ins to default locations on the local disk [HD / C:] not to an external drive or cloud storage.
  • Use the developer's plug-in manager or product portal to install, update, and uninstall.
  • Keep iLok and e-licensing software up to date.
  • Avoid using unofficial or unauthorized ("cracked") plug-ins.
  • Watch out for "Demo Mode" restrictions, like white noise and periodic silence.

If an updated plug-in is not appearing in Live, follow the steps in this guide: VST/AU plug-in doesn't appear in Live's Browser.

Do plug-in formats matter?

While the functionality of different plug-in formats is similar, in Live only one format (AU/VST2/VST3) of the same plug-in should be inserted throughout the same Set.

  • In Live 12, you can identify the plug-in's format in Live's Browser using the Format filter:

    VST AU VST3 Live12.png
  • You can also differentiate plug-in formats based on their icons:
    Audio Unit VST2 VST3
  • In Live 11 and earlier, you can identify the plug-in's format based on the categorized plug-in folders in Live's Browser.

    VST AU VST3 Live11.png
  • You can also identify the different plug-in formats by the appearance of the device. Only VST (short for VST2) includes a preset browser.

    VST AU VST3 Device.png

VST formats on Windows

  • VST3 (.vst3 files) are installed by default to the VST3 folder. The installation path of VST2s is somewhat more flexible, and can usually be selected while installing the device. However, VST2s should not be installed to the VST3 folder. VST2 (.dll) and VST3 (.vst3) files must be stored in separate, dedicated folders.
  • Do not install any unrelated or system .dll files inside the VST2 folder. Only install valid, up-to-date, authorized audio plug-ins there.
  • For detailed instructions on where to install plug-ins, see Using VST plug-ins on Windows.

Plug-in formats on macOS

  • Waves plug-ins in AU format are not supported in Live. Use Waves VST3.
  • If using Custom Folders, set each to its own unique location, and make sure the folder you specify only contains plug-ins of the relevant format (VST2 or VST3). If not needed, turn Custom Folders off.

    Custom_Plug-In_Folders_Mac.png
  • For detailed instructions on where to find or install plug-ins, see Using AU and VST plug-ins on Mac or consult the user manual or product support for the device. 

Are my plug-ins affecting performance?

  1. Test performance without plug-ins to see if they are the cause of an issue. If Live is open, go to Settings → Plug-ins and turn off all plug-ins folders, then close and re-open the Set. If the Live is not running, launch Live while holding down [ALT]/[OPTION]. This will disable the scanning of plug-ins. If performance improves or crashing stops with plug-ins ruled out, a plug-in might be the cause.
  2. Test a single instance of any suspected plug-in in a new, blank, empty Live Set, to see if the crash or issue occurs in isolation. If a specific plug-in triggers problems in an otherwise empty Set, follow the tips below to troubleshoot, or contact the developer of the device directly for support. 
  3. Performance Impact or per-track CPU meter in Live 11 and later versions can help reveal a high processing load on individual tracks. You can use this to find plug-ins incurring a heavy processing load, in order to reduce CPU usage in your Set.

    Live 12 Performance Impact

    Live 11 per-track CPU meter

    ShowCPUTrack.png

    Per_Track_CPU_Meter.png

Troubleshooting crashes:

If a Set containing a specific plug-in consistently crashes, follow these steps:

  • Update the affected plug-in to the latest version and uninstall older versions.

  • Uninstall, then reinstall the plug-in. Be sure to install to the correct location on Windows or macOS.

  • Try replacing all instances with a different format (AU/VST2/VST3). 
  • Test the device by itself in a new, blank, empty Set. 
  • If crashes persist, contact the plug-in manufacturer for support.

To work around a plug-in related crash

  • Disable plug-ins scanning by holding [ALT/OPTION] when launching Live. To re-enable plug-ins scanning, re-launch Live, or use the rescan plug-ins button.
  • You can also temporarily, or permanently, move a specific plug-in file outside the folder where it's installed on your computer, so it won't be scanned when Live launches. Then open the affected Set and delete the problematic device to avoid further crashing.

Troubleshooting and FAQs for popular third-party plug-ins in Live:

 

Waves

Native Instruments

Soundtoys

iZotope

Arturia

UAD 

More help with plug-ins in Live: 

About plug-ins (all platforms)

macOS

Windows

Troubleshooting

 

Ableton offers these in-depth help and learning resources:

Related articles