I posted this 2 weeks ago...
http://forum.cakewalk.com/FindPost/3213436which helps explain some of the issues.
Once scanned though, it's unlikely that this remains a very big problem.
For me, in Windows Defender, I open the settings tab and exclude locations like...
C:\Cakewalk Content\
C:\Program Files(x86)\Cakewalk
C:\Program Files\Cakewalk
and my folder where I keep my projects.
This prevents the virus scanner from scanning all my wave files every time I hit STOP in Sonar.
I also added to excluded processes
C:\Program Files\Cakewalk\Sonar Platinum\Sonarplt.exe
Still, it does take a moment to open Rapture Pro. I'm not sure why.
Additionally Rapture Pro seems to only handle single point touch (you can't turn two nobs at once).
The stuff about the Synth not working well (it freezes fairly often or stops playing - this used to be called the Rapture 'Silent Treatment') is true. Lots of patches don't play at all and this seems like a problem with the installer. Some of the issues are deeper than the installer.
All of the work runs on a single processor (at least I have never seen it shared across processors). I think this is because it is a single VST3. For some reason, it doesn't seem possible for it to take advantage of available CPU across the processors which is a huge bummer since all of the load falls on the first processor and as soon as that processor reaches close to 80% you will get glitching and maybe a drop out. Lots of other work also falls on the first processor, so it's the processor with the least headroom to start with.
The plugin and Sonar do not recover well from over-driving that first processor. You must close and re-open Sonar in most cases to fix the issue.
This one is pretty subjective and I may be just wrong: Rapture Pro seems to throw in odd glitches when not being over-driven. I've heard periodic click that sound for all the world like a sample being cut-off at a non-zero-crossing. It may have to do with voices/polyphony and playing a new note that cancels an old note. But still, it sounds bad and it shouldn't do it. I don't remember Rapture doing this - or I never heard it. I haven't heard anyone talking about this, but I'm betting I'm not the only one hearing it.
This is my short list of stuff...
- Problem playing some patches at all (they don't install properly)
- Problem playing lots of patches due to processor overloading
- Problem playing lots of patches do to a clicking sound that seems associated with playing new notes and is not related to the attack of the new note
- The VST is designed for performance and I was surprised that it is not multi-point touch enabled.
- The VST does not resize and the lists are small
- when using the search box to find a patch, there is no easy way to clear the search and no way to access the rest of your patches until you do.
The good is that the plugin is really fun to make music with.