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

Pinned Answered

Roy Brickley

June 27, 2019 21:56

Massive X is blacklisted in Cubase Pro 10. It is listed as VST 2.0, which I believe is not supported, and needs to be VST 2.4 or higher. Is this a problem with my installation? or is Massive X a VST 2.0 plugin and, therefore, not supported?

Intel Core i7 7700 | PC 64 bit Windows 10 | Focusrite

Comments

83 comments

Official comment

Jeremy @ NI November 26, 2019 12:59 (Edited November 26, 2019 12:59)
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
Robostation June 27, 2019 22:50

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
Roy Brickley June 27, 2019 22:59

ok, thankyou, I will try re-install.

0

Comment actions Permalink
Gunther Hasse June 28, 2019 00:22

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
Jeremy @ NI June 28, 2019 10:18

Hey roy,

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

0

Comment actions Permalink
Peter Beauchamp June 28, 2019 10:38 (Edited June 28, 2019 10:39)

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
Matti N?s?l? June 28, 2019 14:12 (Edited June 28, 2019 14:34)

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
Roy Brickley June 28, 2019 20:56

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
Michael Dunn June 28, 2019 22:45 (Edited June 28, 2019 23:10)

Blacklisted here too, in Nuendo 10 :-(

0

Comment actions Permalink
Peter Beauchamp June 29, 2019 06:22

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

0

Comment actions Permalink
Jeremy Dumouchel June 29, 2019 06:43 (Edited June 29, 2019 06:46)

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
Peter Beauchamp June 29, 2019 10:29

@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
N/A N/A June 29, 2019 23:17

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
Rom Apelbaum June 30, 2019 14:50

Same here, Blacklisted on cubae 10.0.30. Any suggestions?

0

Comment actions Permalink
Jeremy @ NI July 01, 2019 14:00

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
Matti N?s?l? July 01, 2019 15:45

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
Jeremy @ NI July 01, 2019 15:51

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
Matti N?s?l? July 01, 2019 16:13

Here:

0

Comment actions Permalink
Jeremy @ NI July 02, 2019 08:18

Hey Matti,

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

0

Comment actions Permalink
Matti N?s?l? July 02, 2019 08:29

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

0

Comment actions Permalink
Jim Bean July 02, 2019 08:50 (Edited July 02, 2019 08:50)

Hello all,

Just buy a new PC with AVX/AVX2 support!

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

1

Comment actions Permalink
Jeremy @ NI July 02, 2019 09:03

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
Pessi Levanto July 02, 2019 09:40

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
Jeremy @ NI July 02, 2019 10:15

Hey Pessi Levanto,

We contacted you by email, we need more info.

0

Comment actions Permalink
Dai Kwon Shin July 02, 2019 12:04

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
Tobias Korell July 02, 2019 13:01

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
Jeremy @ NI July 02, 2019 14:30

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

-1

Comment actions Permalink
Barry Short July 02, 2019 15:59

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
Ron van Genechten July 02, 2019 18:25

@Jeremy, same problem here!

0

Comment actions Permalink
Paul van Anen July 02, 2019 20:38 (Edited July 03, 2019 03:54)

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