Rapture VST Plugin Error on Sonar Start (Solved I Think!)

[Pte Jack]

I upgraded from X3 to Platinum and had procured Rapture Pro separate before the upgrade. Now when I load Sonar (P) Rapture X64 is erring out. The Fail Point is Main Call. (which is probably because of the way I allowed the upgrade to install.)

It looks like the failing VST being scanned is located in my c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vstplugins\Rapture\ folder and is the Rapture x64.dll Library.

As I had a ton of VSTs installed through X3, and now with the upgrade and Rapture being placed in new folders, how do I go about fixing this.

Looking at the CWPM (Plugin Manager) I find that if I allow the plugin to enable, I am getting Rapture x64 in my VST Audio Effects, I am also getting Rature Pro and LE in my VST(i), as well as Rapture Pro and Rapture Session in my VST3(i) listings.

According to the CWPM

Rapture x64 VST Audio Effects is coming from c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vstplugins\Rapture\Rapture x64.dll

Rapture LE VST(i) from c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vstplugins\Rapture LE\Rapture64LE.dll

Rapture Pro VST(i) from c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vstplugins\Rapture Pro\RapturePro_64.dll

Rapture Pro VST3(i) from c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vst3\Rapture Pro\RapturePro_64.vst3

and

Rapture Sessions VST3(i) from c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vst3\Rapture Session\RaptureSession_64.vst3

I am not seeing what is causing this start up error as the files are in their proper place.

Anyone else have this problem after an upgrade??? If yes, how did you fix it?

[Pte Jack]

Just a quick update, the 32bit version of Sonar does not create the error (and yes, I know, that the error is pulling a 64 bit dll for the 64 bit sonar version) I'm just saying that the 32 bit version does not error out when loading.

[Pte Jack]

Ooooh, Rapture Session created a Fatal Error in 32bit!

[Pte Jack]

The fix, as far as I can tell, was that I had not ran Rapture in standalone mode to register the program, after I did the upgrade. After I ran Rapture by itself, I am not getting the Plugin Error when starting Sonar.

[Polly Esther]

I had the same problem when upgrading, Rapture threw errors.

Seth pointed out for run in stand alone however I got problems there too, a Reinstall (of Rapture not SONAR) fixed mine up.

If you get drop outs afterwards it's because Rapture doesn't auto activate after reinstall as a VST and runs in demo mode, running it once as stand alone and activating via the drop down sorts that out.

Edit;

Just running it once via stand-alone from STEAM should activate the VST, no need to activate manually I think, but if not run at least once after reinstall/repar, it may stick in demo mode and give the cut outs.

[Pte Jack]

I was just wondering about that as a matter of fact. I was playing a bit and the audio was dropping like flies in a mist of raid. I'll give the activation thing a try.

Thanks!

If anyone needs help getting Active Drums setup, I've figured that one out too!! lol (uhm, without using Seth's guide, I didn't find that until AFTER I got AD set up! DOH!)

[Polly Esther]

NP! I thought I'd found the "Windows 10 Anniversary update freeze issues", but Rapture just dropped into Demo mode.

As a side note, if you're on the current W10 build, remember to re-check all the privacy stuff!

All mine got switched back to "On" and performance dropped hugely.

Cortana was choking out my CPU while recording via a MS account login, Changing to Local, disabling ALL background apps (edit; in the Background Apps settings window, not Services, tho a few of those had to be reset to Manual/Disabled after the update too) and as much "Privacy" settings as we now can to avoid hitching is a must do...

[Pte Jack]

Microsoft needs a good whack long side of the head for this. After EVERY update Tuesday, I go through and check the privacy settings. You would be surprized at just how many are magically "Reset" to send telemetry back to MS after an update (especially the big ones).

[Polly Esther]

They can indeed be a killer, I tracked mine down to Cortana updating and downloading all the Background Map data for the Maps App (which it re-enabled for me...) when it figured there's no one using the PC.

IE, let go of mouse and pick up a guitar for 2 mins... crackle!

To be fair, it not only gimped my SONAR, but was getting huge lockups in GTA5 and FO4 from it too, seems Cortana/MS Background whatevers have no "throttles" and will fire up and do what they need to regardless of activity.

Gotta keep those tiles noone looks at updated!

[Pte Jack]

Yup, unfortunately, some of the "Charms" included in Win10 just can't be turned off. I attempted a few fixes on my own by turning off services and through the PowerShell command line you can use to disable some of them, but now my system gives me the big "OMG THere's an ERROR somewhere DING" when I reboot the computer. Other than doing a complete Clean Install of Win10, I can't figure out just what is causing it as my devices are registered and working and all services seem to be doing their job. I don't seem to have any other problems other than that Beep on Boot (BoB, which is now what I call this machine! lol).

[Polly Esther]

Again had a very similar experience, Ding on boot, tracked down to Razer Synapse... it doesn't update properly after the "upgrade" (it pops up mid upgrade on a second monitor, if no dual it most likley hides it), loses it's .dll files and errors on Windows Login 'till a reinstall.

Check the Startup tab in the task manager and see if any of your device apps need a reinstall (Logitech cam stuff, Mouse/Keyboard apps, Soundcard mixer apps and stuff), failing that maybe see if Autoruns has a W10 update and shut off all the startup apps/drivers properly!

Can probably find the issue in the Event Manager (sort it by time and check just after login) for a bit of a clearer idea.

GL!

[Pte Jack]

Thanks. All drivers are up-to-date, I'm very religious on that and I don't have Razer, therefore not the problem. I've been through the EventManager (and we all know just how confusing that can be) and have seen a couple of kernel errors. But, like I said, the only way to truly fix it is to do a clean install of Windows 10... I did the upgrade/keep settings from 8.1pro method when I upgraded, and I'll bet there's still something hanging from that. Way TOO much on this machine to do a clean install, and you can NEVER get a machine to feel right after doing something like that. So, for now and until something else breaks, I'll just keep it the way it is... Good ole' BoB!