Massive X is blacklisted in Cubase 10 Pro [en-us]

Pinned Answered

Comments

82 comments

  • Official comment
    Avatar
    Jeremy @ NI (Edited )

    Hey dear users,

    For some users this fixed the blacklisting in Cubase :

    1. Uninstall Avast (if installed on your system)

    2. Deactivate Windows Defender

    3. Navigate to : C:\Users\"Your User Folder"\AppData\Roaming\Steinberg\Cubase 10_64\.

    4. Delete these files :

    • Vst2xPlugin Blacklist Cubase.xml
    • Vst2xPlugin Infos Cubase.xml
    • Vst2xPlugin SearchPaths Cubase.xml
    • Vst2xPlugin Whitelist Cubase.xml

    5. Launch Cubase and rescan your plug-ins.

    If that works, don't forget to reactivate Windows Defender.

    Comment actions Permalink
  • Avatar
    Stefan Bock

    I'm also running Cubase Pro (version 10.0.30) on Windows 10 Home (64 bit).

    Massive X is not blacklisted here and works. VST Plug-in Manager shows it as VST 2.4.

    1
    Comment actions Permalink
  • Avatar
    Roy Brickley

    ok, thankyou, I will try re-install.

    0
    Comment actions Permalink
  • Avatar
    Gunther Hasse

    It is blacklisted in my Cubase 10 pro (V 10.0.30) as well. The plugin manager shows it as a VST2.4 but still it got blacklisted.

    I reactivated it and now it works... in principle. It cannot find the factory library, I think because it looks into the Massive X folder, wich cannot be changed.

    But: It works within Komplete Kontrol. (Though the strangely new version of Komplete Kontrol also got blacklisted an had to be reactivated.) But it worked for me to load Massive X into Komplete Kontrol and then it also finds the presets.

    Though I think I also tried it in Komplete Kontrol standalone mode first, which might be neccessary because of the scan...

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey roy,

    Please let us know if re-install worked for you or if you need assistance on this. 

    0
    Comment actions Permalink
  • Avatar
    Peter Beauchamp (Edited )

    Its blacklisted in my Cubase 10.0 30 Windows 10 Pro and is shown as VST2 -64. I have tried re-activating it and it will not have it. Also not working in Komplete Kontrol.

    Not sure what i do from here some advice would be very welcome.

    Thanks

     

     

    0
    Comment actions Permalink
  • Avatar
    Matti Näsälä (Edited )

    Hi
    Massive X is blacklisted in Cubase 10.0.30 Pro (Win 10 Pro) and is shown as VST2 -64. Reinstalled and reactivated.

    0
    Comment actions Permalink
  • Avatar
    Roy Brickley

    I managed to get it reinstated finally and seems to be working ok, and is showing as VST 2.4. Though it is classed as a 're-instated plugin' and highlighted as such in plugin manager.

    0
    Comment actions Permalink
  • Avatar
    Michael Dunn (Edited )

    Blacklisted here too, in Nuendo 10 :-(

    0
    Comment actions Permalink
  • Avatar
    Peter Beauchamp

    Did you reinstall over the top of the existing or delete it first?

    0
    Comment actions Permalink
  • Avatar
    Jeremy Dumouchel (Edited )

    I've got the same issue here to on Windows 10, blacklisted as VST 2. Tried reinstall but alas no change.

     

    I've had similar issues with other plugins from the Collector's Edition suite.

    0
    Comment actions Permalink
  • Avatar
    Peter Beauchamp

    @Jeremy Dumouchel Well if you have tried that and it also did not work I am unsure how this will be resolved then. I am somewhat hacked off after waiting all this time and something like this happens.

    0
    Comment actions Permalink
  • Avatar
    N/A N/A

    blacklisted here too, Cubase Pro 10.0.30... thinks its 32bit or something, but still lists it as 64bit after that in the blacklist list.

    I had to re-activate the plugin, and then manually drag it into the collection folder to be able to load it.

    Please patch

    0
    Comment actions Permalink
  • Avatar
    Rom Apelbaum

    Same here, Blacklisted on cubae 10.0.30. Any suggestions?

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hello dear users,

    Did you move the dll file after installation ? Did you install Massive X with Native Access ? What installation destination did you choose when installing ? Please make sure you didn't copy the files or installed them in a VST 32 bit folder or a VST3 folder. By default the dll is installed here :

    C:\Program Files\Native Instruments\VST Plugins 64 Bit

    You can change the destination within Native Access :

    Setting Install Locations in Native Access [VIDEO]

    Please alsoread this article carefully :

    Plug-in Administration in Cubase 9 (and higher)

    If you still have the same issue afterwards, please post screenshots of the installed locations you chose in Native Access preferences and a screenshot of the VST folders choses in Cubase. 

     
    0
    Comment actions Permalink
  • Avatar
    Matti Näsälä

    Hi

    Uninstalled and reinstalled Massive X, and the VST -path is set to C:\Program Files\Native Instruments\VST Plugins 64 Bit. Now Cubase gives this error message:

    Reactivating crashes Cubase.
    ------------------------------------------------------

    Win10 Pro (1903), 32Gb RAM, i7 9700K 3.6 GHz, ASUS TUF Z390-PLUS GAMING, ASUS GeForce GTX 1060 DUAL OC - 6GB GDDR5 RAM, Focusrite Scarlett 6i6, Komplete Kontrol MK2, Cubase 10 Pro, FLStudio 20, Reason 10, Komplete 12 Ultimate Collector's edition

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Can you post a screenshot of the destination folders chosen in Native Access ? Can you also post screenshots of cubase's Plug In manager ?

    0
    Comment actions Permalink
  • Avatar
    Matti Näsälä

    Here:

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Matti,

    We contacted you by email, we need more information, please check your inbox.

    0
    Comment actions Permalink
  • Avatar
    Matti Näsälä

    Hi
    Thank you. I'll send the info zip to you later today.

    0
    Comment actions Permalink
  • Avatar
    Jim Bean (Edited )

    Hello all,

    Just buy a new PC with AVX/AVX2 support!

    Thank you for that Native Instruments! Way to go! :-(

    1
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Jim Bean,

    Wrong thread, please follow or post in this one :

    MASSIVE X not working with non AVX compatible processors

    0
    Comment actions Permalink
  • Avatar
    Pessi Levanto

    I have the same problem. Plugin showing as VST 2 64bit. If I try to re-activate it, Cubase 10.0.30 crashes. I'm on a Mac Pro Late 2013 "black trashcan" running OS 10.12.6. It is AVX compatible.

    The same thing happens with Ableton Live. It cannot scan the plugin without crashing.

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Pessi Levanto,

    We contacted you by email, we need more info.

    0
    Comment actions Permalink
  • Avatar
    Dai Kwon Shin

    I have the same problem. Plugin showing as VST 2 64bit. If I try to re-activate it, Cubase 10.0.30 crashes.

    i'm on a Win 10 pro




     

    0
    Comment actions Permalink
  • Avatar
    Tobias Korell

    Have the same Problem with Mac Cubase 10.0.30 Pro and Massive X.

    Here the header of my Apple-problem-report (would send you the complete report per email if you want - contact me):

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    Process:               Cubase 10 [885]

    Path:                  /Applications/Cubase 10.app/Contents/MacOS/Cubase 10

    Identifier:            com.steinberg.cubase10

    Version:               10.0.30.236 (10.0.30.236)

    Code Type:             X86-64 (Native)

    Parent Process:        ??? [1]

    Responsible:           Cubase 10 [885]

    User ID:               501

     

    Date/Time:             2019-07-02 14:38:35.706 +0200

    OS Version:            Mac OS X 10.13.6 (17G7024)

    Report Version:        12

    Anonymous UUID:        ————

     

     

    Time Awake Since Boot: 1300 seconds

     

    System Integrity Protection: enabled

     

    Crashed Thread:        0  Dispatch queue: com.apple.main-thread

     

    Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)

    Exception Codes:       0x0000000000000001, 0x0000000000000000

    Exception Note:        EXC_CORPSE_NOTIFY

     

    Termination Signal:    Illegal instruction: 4

    Termination Reason:    Namespace SIGNAL, Code 0x4

    Terminating Process:   exc handler [0]

     

    Application Specific Information:

    /Library/Audio/Plug-Ins/VST/Massive X.vst/Contents/MacOS/Massive X

     

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey, to all the people who have posted here, we contacted you by email, please check your inboxes. 

    -1
    Comment actions Permalink
  • Avatar
    Barry Short

    Can you send the email it to me as well please. I am also having the same problem. Massive. Maschine 2. Reaktor and Komplete Kontrol. If I reactivate KKontrol in Cubase 10Pro it stops Cubase from closing. It hangs. Remove KK and it's fine. 

    0
    Comment actions Permalink
  • Avatar
    Ron van Genechten

    @Jeremy, same problem here!

    0
    Comment actions Permalink
  • Avatar
    Paul van Anen (Edited )

    Contact me by email too please! 
    I have installed the Demo version but also blacklisted in Windows10 / Cubase 10

    I checked to upgrade my system, and it will cost me arround € 550,- I think that is not cool! And I don't have the money for that! 

    0
    Comment actions Permalink

Please sign in to leave a comment.