Have you checked the output settings of the standalone when you open it to check it is pointing to the correct inputs and outputs?
I have Rapture Pro and have no problems with it.

^^ please check this in the standalone version. If a program visually responds but has no sound, it is often a routing issue (sending audio to something not really on).

Also, you didn't happen to install the Rapture Pro's multisamples to a custom directory ? because I have seen an update for CCC change your custom settings without notice, not sure if then reinstalling Rapture Pro again as you have would change where it looks for those.

Thanks for trying to help me.
 
I did not change the install location in Command Control from the default either time that I installed Rapture Pro (or anything else that it installed. The plug in manager says they are here:
 
 
c:\program files\common files\vt3\Rapture Pro\RapturePro_64.VT3
 
Rapture session is in a similar directory and it works in Sonar Professional
 
c:\program files\common files\vt3\Rapture session\RaptureSession_64.VT3
 
In Sonar, the midi track has no input, but is routed to 1rapturepr1. Rapture Pro has an input of OMNI and an ouput of Master. And Master has no input and an output of the speakers in my computer. If I add some notes via the staff menu to either the midi track or the rapture track, nothing plays.
 
If I do the same set up with Dimension Pro or Rapture Session, I get sound.
 
In the stand alone, the output is grayed out. If I click on one of the sample rates, then the output becomes active, but clicking on it does nothing. Should there be a list or something when you click on output? When I click on one of the sampling rates, if I go back and check it doesn't get checked. I would have thought clicking on one would have checked it. But like I said the Output menu becomes active but has no entries. 
 
I am not using the ASIO. I have tried using it a couple of times, but when I switch to it, then I don't get any sound from anything in Sonar when using ASIO. Maybe I'm missing a step.
 
And I did load a program (or instrument) to Rapture Pro when I tried to use it in both Sonar and the stand alone.
 
I do have Sibelius 7 First and Notation that I use for creating sheet music. I know they have their own instruments. Don't know if it is possible to try and use Rapture Pro in them.
 
Thanks again.

Just wanted to add...
I only had Rapture Pro for about a month. The first couple of days I tried to use it (with the previous version of Sonar), I would only get intermitent sound. It would play a few notes and then drop some. Then I got a notice that Rapture Pro was running in demo mode and that I should open Command Center to activate it. It said it would drop notes like it was. I opened the command center and I could see that rapture pro was completely installed and I could see my serial number, but I couldn't find any way to activate it. I went back to Sonar Professional and looked for a way to enter the serial number, but found no way. But then Rapture Pro started working and the sound was amazing. It worked for about a week and then I installed the new update and now it gives me no sound at all.
 
I am running Windows 10. I know that if you don't run a program as administrator, that sometimes the serial number doesn't get written to where it needs to go and then you have to enter the serial number each time you run the program. At least this used to happen in previous versions of Windows. I am sure I installed the original version of Command Center using Run as administrator, but I am not sure what happens when it installs the programs. That's why I wondered if it might still be running in demo mode. Anyway to check?
 
*****Hey,...I just tried it in Sonar X3 and it rapture pro works there. It says that it is running build 209. I don't know if the Command Center updates Sonar X3 or not. But I get sound following the same steps I described above.****

Kev914 -
 
Rap Pro continues to work fine in the new Sonar release for me too. 
 
Since yours seems to be an isolated case, the Cakewalk support guys might be able to help.

Kev914
Just wanted to add...
I only had Rapture Pro for about a month. The first couple of days I tried to use it (with the previous version of Sonar), I would only get intermitent sound. It would play a few notes and then drop some. Then I got a notice that Rapture Pro was running in demo mode and that I should open Command Center to activate it. It said it would drop notes like it was. I opened the command center and I could see that rapture pro was completely installed and I could see my serial number, but I couldn't find any way to activate it. I went back to Sonar Professional and looked for a way to enter the serial number, but found no way. But then Rapture Pro started working and the sound was amazing. It worked for about a week and then I installed the new update and now it gives me no sound at all.
 
I am running Windows 10. I know that if you don't run a program as administrator, that sometimes the serial number doesn't get written to where it needs to go and then you have to enter the serial number each time you run the program. At least this used to happen in previous versions of Windows. I am sure I installed the original version of Command Center using Run as administrator, but I am not sure what happens when it installs the programs. That's why I wondered if it might still be running in demo mode. Anyway to check?
 
*****Hey,...I just tried it in Sonar X3 and it rapture pro works there. It says that it is running build 209. I don't know if the Command Center updates Sonar X3 or not. But I get sound following the same steps I described above.****

Hi, kev914,
Rapture Pro was a separate purchase, it didn't come free with Sonar, at least, I had to buy it...

Yes, I bought it too.

Kev914
I am not using the ASIO. I have tried using it a couple of times, but when I switch to it, then I don't get any sound from anything in Sonar when using ASIO. Maybe I'm missing a step.

You should try that again if your interface has native ASIO driver, and have the forum help troubleshoot if problems persist. In the mean time, try lowering your WDM buffer if you can. The combination of WDM and a high buffer size can cause problems like this.
 

I called Tech support and he did a support session into my computer and he checked various things. He thought maybe the sounds weren't loading, but he said they were. Then he went to a panel in Rapture Pro and there was a setting somewhere called cc12 and I think he turned it off. Not sure if he then turned it back on or not. He said that it was blocking the sound. He said it was a known bug and it would be addressed in the next update. He did try reloading Rapture Pro to make sure that the change would stick and it did. I wished I could give better details. He showed me what he did but after we disconnected, I wasn't able to find the setting again. But he did say he would send me the details of what he did.
 
And I apologize for being a little torqued in my first post. I was upset because I finally got Rapture Pro to work and then almost as suddenly it didn't work again.
 
Have to say that Rapture Pro sounds amazing. And I really like Sonar too.