https://youtu.be/nJvX1aiDfAo
 
In this video, I demonstrate that some Rapture Pro patches cause issues at 44.1 causing the Synth to seize.
 
At 96 the same patches crash so badly they force the user to close and re-open Sonar.
 
A few of the patches that cause this issue for me include...
Dark Angelic 2
Dramatic Resonance
Lush Guitars F5
Multipulse & Brass
 
I have called Support. They recommended I re-install Rapture Pro, which I did. After re-installing the first time, the problematic patches just stopped making noise all together.
 
I then uninstalled and re-installed and the patches were back and not functional.
 
Again, at 44.1 the Synth seems to recover if you wait long enough. At higher sample rates, the synth never recovers and the project has to be closed and re-opened.

i assume this is in splat, have you tested in other hosts, or standalone?

No. I've only done it in Sonar Platinum.

Rapture Pro takes an absolute age to load on my system.
Splat even white screened on me yesterday while RP was loading, though it did recover after about 3 minutes of doing nothing

Bristol Jonesey...
 
Check out this link...
http://forum.cakewalk.com/FindPost/3213436
 
I found that the virus scanner scanning all the new files was what caused the whitescreen on my side. I have been able to work around that by adding an exception to Windows Defender.
 
I have excluded these from Windows Defender...
C:\Cakewalk Content\
C:\Program Files\Cakewalk\
C:\Program Files (x86)\Cakewalk\
 
I also excluded the wave file type. 
 
and set this as an excluded process.
C:\Program Files\Cakewalk\Sonar Platinum\SONARPLT.exe

BTW, I'm happy to pull this video once things get worked out.
 
I'm *not* trying to slam Sonar. I'm just pointing out my issue.

Thanks for that Jeff.

gswitz
 
I'm trying to slam Sonar. I'm just pointing out my issue.

You mean "I'm not trying to slam Sonar...."   don't you?  (that's how I read it)

Sure hope Cake releases a quick fix soon. This is a crappy release that obviously was rushed out the door without thorough testing. I became so disgusted with Rapture Pro I've uninstalled it for now. Freezes, glitches, crashes, etc... I don't usually complain much and I am fairly patient but this is really ridiculous!

I do believe there was insufficient testing, but it does sound like it's been in the hopper for a long time.
 
Rapture Pro is significantly more efficient than Rapture on my computer.
 
Maybe testing was broken up in many little iterations over time and there was not a full regression before the release. I don't know. Certainly, releasing it brings about a free regression test. :-) (as long as the results don't hurt sales).
 
** One of the real bummers is that this may actually take best talent off other projects for damage control. And sometimes managers make choices to cut features that can't easily be fixed in order to keep other things on schedule. In general, software teams work best when not in a state of emergency. **
 
If I could send a message to the Bakers it would be to not flip out. Keep steady on. Improve and fix as you can. And a request to please not forget about us over the long term. I don't want this to be the last Rapture release.