Massive X is blacklisted in Cubase 10 Pro [en-us]
Pinned AnsweredMassive 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
-
Official comment
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 -
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...
-
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.
-
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
-
Hey Jim Bean,
Wrong thread, please follow or post in this one :
MASSIVE X not working with non AVX compatible processors
-
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
Please sign in to leave a comment.
Comments
83 comments