I recently purchased Cubase 9.5 Pro, and I am in learning mode. Sadly, Cubase blacklisted a number of 64-bit VST 2 plugins. Surprisingly, NI Komplete Kontrol is one of those plugins. When I reactivated this plugin, Cubase 9.5 Pro crashed and since then was never able to relaunch. I receive the following error dialog box:
Cubase quit unexpectedly.
Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.
Ignore / Report… / Reopen
I made several attempts, trying all the options, but Cubase will no longer run. I rebooted by system but still no luck.
MacBook Pro (Retina, Mid 2012)
2.7 GHz Intel Core i7
16 GB 1600 MHz DDR3
OS X 10.13.3 (High Sierra)
I get it that Cubase blacklists 32-bit plugins and what may be considered ‘questionable’ plugins, but Native Instrument plugins? Come on, Steinberg. In fact, Cubase seems to be quite picky about its plugins. In fact, I could not even find Steinberg’s own Retrologue in its VST Instruments list. Not sure if it’s blacklisted, but it would be comical if it is. Unfortunately, I cannot check its blacklisted status, since Cubase WILL NOT LOAD ANY LONGER.
Really. I dropped a nice chunk of change on Cubase 9.5 Pro. In fact, recently I decided to take a dive into all things Steinberg, at least on the software side. I purchased both Cubase 9.5 Pro and Absolute 3, and I have (well, at least until most recently) my eyes on Nuendo. I value ‘time’ as the most precious commodity, and when my workflow gets disturbed by software, it forces me to re-evaluate my software choices. I am certainly willing to get around Cubase’s blacklisting of 32-bit plugins and ‘questionable’ plugins by using a rewire slave that handles them without issue. Yes, I continue to use another DAW with which I, thus far, have no serious issues running EVERY plugin that I thrown at it.
Steinberg is being overly protective with its Cubase blacklisting strategy, and this will drive away customers - myself included. Don’t get me wrong. I am EXTREMELY IMPRESSED with Cubase, and I spent quite a bit of time researching my purchasing decision. I took the same steps in researching my purchasing decision for my first DAW, which I still faithfully use. I chose Cubase in addition to my first DAW, because its feature set complemented my other DAW’s feature set. With both these DAWs, I was confident that I would be able to cover all my capability and workflow requirements.
Alas, Steinberg’s Cubase, with its over-restrictive blacklist feature, is making it impossible to stay loyal.
Given I am new Cubase user, I’ll assume that my novice status prevents me from seeing an obvious fix to this problem. I would appreciate feedback from Steinberg and the Steinberg community at large. Barring a complete reinstall, how can I quickly and effectively resolve this problem? For instance, is there an XML configuration that I can hand-jam to get me back on track?
I really do not want to reset and purchase yet another DAW…
Thank you in advance for your help in this matter.