Ok, Got the Rapture Pro upgrade sale, great price I thought why not. Ran the Cakewalk Command Center and installed without a problem. I have been having a problem opening Sonar Platinum (issue may be related) so have been using Sonar X3 Producer which I like so I kept it installed when I upgraded to Platinum. Opened Producer and the vst scan ran and showed the Rapture pro being scanned and it tells me there are no errors. When I open the insert synth drop-down menu Rapture Pro is not on the list ( neither is Rapture Session or Z3TA 2) or many other vst I know are installed and work in other programs. I have both the 64bit and 32bit versions installed. Also the standalone versions do not open (Z3TA 2 and Rapture Sessions do work standalone) I am beginning to suspect that the vst scan for sonar is wonky, it may the culprit that is crashing Platinum and maybe there is something that I need to do to get the scans to acknowledge the vst that are in the vst folder for Sonar.
 
Any ideas what could be causing this, anybody else having this problem.
 
Bruce
 
I am running Windows 10 Pro 64 bit, Intel Core i5-4200 CPU @ 2.50, 8 GB Ram. Prosonus AudioBox USB or Guitar port on occasion

If the stand alone versions do not work, that indicates either an install problem or an authentication problem. Both RPro and the updated Z3ta+2 require using the Command Center to authenticate.
 
Also check the VST3 synth list. Depending on the VST3 migration settings in preferences, the VST2 versions may not appear in SONAR.

scook
If the stand alone versions do not work, that indicates either an install problem or an authentication problem. Both RPro and the updated Z3ta+2 require using the Command Center to authenticate.
 
Also check the VST3 synth list. Depending on the VST3 migration settings in preferences, the VST2 versions may not appear in SONAR.

 
I used the command center and as far as I know they were authenticated. Z3TA works fine in standalone it is just Rapture Pro that does not. I tried reinstalling 2 times and the same results. Also checked in VST3 and they do not show up there either. The folders are present in the Cakewalk folder so I know they installed. I have had several Windows 10 updates the past couple of days so maybe there is a problem there.

Well did a reinstall and then re scanned for vst in all my DAW and it now is showing up. Still the stand alone does not work. Checked my firewall settings and it does not show up on the list. I guess I will try a few other things but can now use it as a plugin.

I have problems too with Rapture Pro. I bought it, download it and want to start ... Bam! Rapture Pro crashes instantly, Windows popup the bug report window. The same, when I try to open Rapture Pro VST3 Plugin in Sonar. Sonar crashes, when I try to insert the Plugin.
 
I installed Rapture Pro with Cakewalk Command Center without problems, all looks fine, but I can not use it!

scook Both RPro and the updated Z3ta+2 require using the Command Center to authenticate.

is this also true for updating an already installed/authenticated z3ta+2?

Hi all,
 
I removed Rapture Pro complete, it was a 64Bit installation. After that, I install the 32BIT version. The stand alone Rapture crashes too, but the VST Plugin in Sonar works. When I load an program into Rapture, nothing happens, no sound... I'm frustrated at the moment...

OMG!!
All works fine now! I remove Rapture Pro again, reinstall the x64 version. First start -> crash. Than, I start the Rapture Pro stand alone app with admin rights - wuaaaah ... It starts! Crazy!

penryn
OMG!!
All works fine now! I remove Rapture Pro again, reinstall the x64 version. First start -> crash. Than, I start the Rapture Pro stand alone app with admin rights - wuaaaah ... It starts! Crazy!

Looks like you might have weird permissions set up on your PC.
Either your files or user account.
You could try creating a new user account in windows and see if you experience similar issues or not.
You don't run anything like cccleaner do you?

Doktor Avalanche

penryn
OMG!!
All works fine now! I remove Rapture Pro again, reinstall the x64 version. First start -> crash. Than, I start the Rapture Pro stand alone app with admin rights - wuaaaah ... It starts! Crazy!

Looks like you might have weird permissions set up on your PC.
Either your files or user account.
You could try creating a new user account in windows and see if you experience similar issues or not.
You don't run anything like cccleaner do you?

I really don't know what was wrong here. I had to start Rapture Pro for the first time with admin rights. Now all works fine and I do not need to start Rapture Pro with "run as administrator". Great virtual instrument with lot of sounds... I'm playing...