Yes, as Phil mentioned, it’s hard to help without knowing your configuration, no one can just guess what’s happening without knowing more about your system & configuration. Please update us with the followings :
OS Type/Name/version : i.e → MacOS High Sierra 10.13.6 (17G14042)
DAW Name & Version : i.e → Cubase Pro v11
KICK 2 version : i.e KICK 2 v1.1.4
Then other important points like if you’re using a 32bit or 64bit version of the plugin matching your system ( especially if you’re on Windows ) and is the problem happening when using the VST or the AU plugin instance of Kick 2.
Knowing if that’s happening after a new Kick 2 installation or if it’s following an OS or DAW update can help to troubleshoot this as well a step by step description of the issue you’re having.
New Kick 2 installation, just bought and installed last week.
Step by step? I thought that was evident from my first post. Making changes to the parameters causes the VST to crash, but not in every instance. When I restart Cubase (v Pro 11) I’m alerted that Kick 2 x64.ddll caused the crash.
Do the uninstall first and I also recommend to use the free CCleaner to perform both registry & left over files clean up, then reboot your PC. Make sure you’re up to date with the latest version of Cubase Pro 11 and major Windows updates. Start Cubase once and close it, then go through a new KICK 2 installation.
On Windows it’s important that you only run the x64 installer, run it as Administrator.
Then run Cubase again and have it to re-scan your Kick 2 plugin and check if that solves the issue. It’s often tricky to be sure if it’s a plugin or a DAW issue, especially when DAWs got recent updates, so a clean uninstall/install procedure is a good point to start IMO.
Sorry, tried that. Win 10 is up to date, as is Cubase, latest version.
Even just now in a new project after reinstall, no other synths or FX loaded, editing a preset for 2 -3 minutes, I click the right arrow button to change the sound in click module 2, Kick 2 hangs, and a second or 2 later Cubase bombs entirely. This doesn’t happen with any other plugin I own.
I’ll just try and get a refund, will be easier. Thanks for your help
(PS Please don’t recommend Ccleaner, it has a terrible reputation!)
You’re giving up easily IMHO, look there’s always 3 sides of things for Plug-ins to work correctly : Your Computer “health” in terms of installation, updates & junk files maintenance as well as best setup for an audio rig, then your DAW and then the Plug-in itself.
Those 3 things can sometime be difficult to troubleshoot but it’s not likely that the plug-in is the one responsible for the issues. In your case, you’re using a brand new version of Cubase, that’s also a potential issue.
If the manual uninstall/install procedure did not solved your issue, I would suggest to refer to Steinberg support threads in order to clean up Cubase plug-ins cache & database and even thinking about a complete Cubase Reset or clean installation.
I’m running hundreds of plugins with multiple DAWs on my end, and when I’m facing issues like this, I try to follow this way to proceed, step by step. Reinstalling the Plug-in first, then forcing a clean complete Plug-ins re-scan and then resetting or re-installing the DAW giving issues.
As for CCleaner, I’m running the free version since edges and never had one problem with it, IMO it really helps to clean up a lot of junk files and especially left over and unnecessary registry keys that really stack up on your PC and slow down and seriously affect Windows performances.
I’m not running Cubase myself, so I’m not able to perform any testings on my end, so I guess there’s not much more I can suggest here via the direct help from the forums. Suggest that you open a support ticket with S.A then as well as reporting the issue to Steinberg support and send them your Cubase Log.
For S.A team → @phil_johnston any insight on this one ? Some testings on Cubase Pro 11 on your end ? Not much I can do here without using Cubase. Thanks.