(if "Vst2xPlugin Whitelist Cubase" is not in the folder, relax, just rescan your Plugins in Cubase (Plugin-Manager, than refresh the Cubase 10. until the next NI Update, than do this cycle again, and again, there are no problems in performance, gui, latency, load/save or otherwise notable that i encountered.
Cubase portable windows 10#
Only tested on Cubase Pro 10.5.20 (Build May 05 2020) and Windows 10 (Versions 1909 & 2004)ġ.) Open Cubase->(dont bother to open a session)-> Studio->Plugin-Manager->Blocklist->reactivate all NI dll->check the Tabs (all reactivated Plugins are red)->Close CubaseĢ.) Go to C:\User\\AppData\Roaming\Steinberg\Cubase 10.5_64 and only delete:ģ.) Then open Cubase again and all the Reds made Homerun (no Restart/Unistall or anykind of operations needed, takes really just 2 minuts of your time) This one helps me for every NI Product that is frequently thrown to the Blocklist (Kontakt, KK, Massive X, Battery 4, jarajaraja):
To me it seems that Cubase doesn't like something that is coded into the Kontakt.dllįor the ones that are too lazy to go through the cubase post, The Muse was so kind to share (and also my approach is a little bit different) I have done what you suggested and there is no change, which means at least that the Kontakt.dll is not damaged. The only thing is, Cubase keeps on redflagging Kontakt. Now, when I start The Kontakt plugin, it works just fine. Native Acces also points to the same folder. The kontakt.dll is also in that VSTplugins 64bit folder. The path that Cubase points to for Kontakt.dll is in the Vstplugins 64bit folder. It offers audio recording and edition tools that will let you manipulate audio as you want. (other blocked plugins have the reasons 'not valid plugin' or 'not supported 32bit')Īfter I panicked, I luckily found that I can reactivate Kontakt.Īnd after reactivation Cubase puts it back on the Vst instrument list. Cubase is an audio edition platform that allows you to create your own masterpieces, mixes and improve quality of previously created tracks. Then when I go into the blocklist, it states that the reason is 'unknown'. Cubase at first stated that it doesn't support 32bit plugins when it blocklisted Kontakt,
You would simply move existing your setup to the new machine. There would be no installation, re-making/importing settings, reconfiguring plugins, etc.
Cubase portable portable#
Thanks for trying to help out, I edited my post previously. Even for those who don’t frequently work on different computers, a portable Cubase would make it much easier (at least on Windows) to migrate when you acquire a new machine.
0 kommentar(er)
