![]() Unfortunately, I was unable to manually catalog all the blocked plugins, because Cubase refuses to run any longer. Cubase also blocked a number of my other 64-bit mainstream plugins. This is the first blocked plugin that I reactivated. Thus far, I was only able to observe Cubase continually crashing after I ‘reactivated’ Komplete Kontrol from the VST Plugin Manager. I am not stating my issue is exclusively a Komplete Kontrol or NI plugin problem in general. Since I use NI’s Native Access to run updates, as I understand, Native Access takes care of everything other the hood. Yes, I have all the latest versions installed. This is a strange issue though, I don’t think anyone else reported having issues with NI’s plugins recently. If updating the plugin using Native Access doesn’t work, you’ll probably have move the plugin file to another folder. Thank you in advance for your help in this matter.Īre you using the latest version of Komplete Kontrol and other NI plugins? Cubase’s plugin scanner/blacklist isn’t that sensitive, it only blacklists plugins that seriously misbehave during scan, or redundant VST2 versions of the plugins. I really do not want to reset and purchase yet another DAW… 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 would appreciate feedback from Steinberg and the Steinberg community at large. Given I am new Cubase user, I’ll assume that my novice status prevents me from seeing an obvious fix to this problem. With both these DAWs, I was confident that I would be able to cover all my capability and workflow requirements.Īlas, Steinberg’s Cubase, with its over-restrictive blacklist feature, is making it impossible to stay loyal. I chose Cubase in addition to my first DAW, because its feature set complemented my other DAW’s feature set. I took the same steps in researching my purchasing decision for my first DAW, which I still faithfully use. I am EXTREMELY IMPRESSED with Cubase, and I spent quite a bit of time researching my purchasing decision. Steinberg is being overly protective with its Cubase blacklisting strategy, and this will drive away customers - myself included. Yes, I continue to use another DAW with which I, thus far, have no serious issues running EVERY plugin that I thrown at it. 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. 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 purchased both Cubase 9.5 Pro and Absolute 3, and I have (well, at least until most recently) my eyes on Nuendo. In fact, recently I decided to take a dive into all things Steinberg, at least on the software side. I dropped a nice chunk of change on Cubase 9.5 Pro. Unfortunately, I cannot check its blacklisted status, since Cubase WILL NOT LOAD ANY LONGER. Not sure if it’s blacklisted, but it would be comical if it is. In fact, I could not even find Steinberg’s own Retrologue in its VST Instruments list. In fact, Cubase seems to be quite picky about its plugins. I get it that Cubase blacklists 32-bit plugins and what may be considered ‘questionable’ plugins, but Native Instrument plugins? Come on, Steinberg. I made several attempts, trying all the options, but Cubase will no longer run. Click Report to see more detailed information and send a report to Apple. I receive the following error dialog box:Ĭlick Reopen to open the application again. When I reactivated this plugin, Cubase 9.5 Pro crashed and since then was never able to relaunch. Surprisingly, NI Komplete Kontrol is one of those plugins. Sadly, Cubase blacklisted a number of 64-bit VST 2 plugins. I recently purchased Cubase 9.5 Pro, and I am in learning mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |