Why is Massive not showing up in my Ableton VST2 folder?

greatwhitestark
greatwhitestark Member Posts: 1 Newcomer
edited October 2024 in Massive X & Synths
I recently got a new laptop and when downloading all my native instruments plugins, I noticed that Massive is not showing up in Ableton under the VST2 category. It is there in the Finder VST2 folder, but it does not show up in Ableton. However, the VST3 plugin shows up and works perfectly fine. Thanks!

Best Answer

Answers

  • Monochrome
    Monochrome Member Posts: 1,383 Expert
    Answer ✓

    VST2 plugins are not supported on Macs running Native mode. You will need to open Ableton in Rosetta mode in order to access VST2 plugins.

  • reffahcs
    reffahcs Member Posts: 848 Guru

    Minor point of clarification. NI dropped VST2 support with some of their recent software updates. Ableton Live is more than happy to run Arturia or other 3rd party VST2's on Mac ARM M1/M2 (and m3?) systems.

  • Lovelight
    Lovelight Member Posts: 6 Member

    Im an Ableton user as well Live 12 supports VST2 without any issues. The chaos after this with VST2 and the KK3 has been a nightmare. Ive done the installation with both KK 2.9.6 and 3.X but its still not good since it overwrites every earli version after any updates, so you need the complication installing 2 versions of KK again and again. Because i use 2 versions of KK is my apperently old MK2 S61.

    im loosing my patience using KK at all on new projects since its only a lot of trouble. There must be a lot of people with projects filled with VST2 instruments, and now shall go through a labyrint of lost presets and so on. Why isent NI VST3 instruments not backward compatible or maybe im wrong and just frustrated.

  • iNate
    iNate Member Posts: 269 Pro
    edited April 2024

    Some DAWs will automatically disable/hide a VST2 if the VST3 has also been scanned.

    Instead of showing both, they default to the VST3, because that is the newer standard and the one that will continue to be compatible into the future. If you use VST2, then you run the risk of projects not loading properly in a future version that may drop support for the old VST2 standard - which has long been superceded.

    Studio One and Reason also do this for many plug-ins. That may be what's happening.

    The only time both show up is when the VST2 hasn't been updated to use the same vendor information, which is the case for some of Native Instruments' VST2 plug-ins which still have vendor as "Native Instruments GmbH" instead of "Native Instruments" (VST3).

    Normal behavior for those DAWs.

    The only time you should care about the VST2 is if the DAW or production software you're using does not support VST3. I would just ignore this.

This discussion has been closed.
Back To Top

Categories