Hello, I am stumped!
 
Hoping that some of you smart folks can shed some light on this. I have tested this with all security software uninstalled, and I run a locked down version of Windows 7 with unnecessary services disabled. The standalone version uses the ASIO drivers from my sound module by default, and I have Sonar setup to use WDM/KS drivers. I have tried two different keyboard controllers using unique USB-MIDI drivers. Same problem with either audio or USB-MIDI drivers in use ...
 
I am trying to give some love to Rapture Pro, but it seems not to like me! I love the new patch browser! I have Dimension Pro and Rapture classic, and the consolidated Rapture Pro GUI seems to be an enticing new way to use these tools! I also have all of the other Cakewalk synths, as well as some 3rd party VST synths that run like clockwork in my rig, never crashing, ever!
 
I have searched the forums, but it seems like I am the only one having this issue!
 
What doesn't work ... I have the same problems with the standalone Rapture Pro mini host, as well as the Rapture Pro VST using installed versions of Sonar 8.5, X2, and X3, as well as Project5.
 
Here is what I have determined that works. If I only browse the user imported D-Pro or the Rapture Classic patches, everything works fine. It is only when I browse the Rapture Pro Factory Library in any host or standalone mode that the issue occurs. I may get a few patches to play, but then bam! When switching to a new patch, using the standalone Rapture Pro, it can crash immediately.
 
While using the Rapture Pro VST, it works until I hit a patch that seems to hang while loading ... then when I close Sonar I get the crash dialog. In all cases, this is the code that is shown - - Exception Code:    c0000005, referencing RapturePro_32.dll
 
Thanks for any input!
 
Here is the Event log info:
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    RapturePro_32.exe
  Application Version:    0.0.0.0
  Application Timestamp:    568579db
  Fault Module Name:    RapturePro_32.dll
  Fault Module Version:    2.0.4.25
  Fault Module Timestamp:    569d3936
  Exception Code:    c0000005
  Exception Offset:    0017bf3b
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789
 
 
  Event Viewer
 
  Log Name: Application
 
  Sourse: Application Error
 
  Event ID: 1000
 
  General
 
Faulting application name: RapturePro_32.exe, version: 0.0.0.0, time stamp: 0x568579db
Faulting module name: RapturePro_32.dll, version: 2.0.4.25, time stamp: 0x569d3936
Exception code: 0xc0000005
Fault offset: 0x0017bf3b
Faulting process id: 0xea4
Faulting application start time: 0x01d1b1fd8cce266b
Faulting application path: C:\Program Files\Cakewalk\Vstplugins\Rapture Pro\RapturePro_32.exe
Faulting module path: C:\Program Files\Cakewalk\Vstplugins\Rapture Pro\RapturePro_32.dll
Report Id: f60d42e8-1df0-11e6-8d6e-f7be690d535d
 
 
 

There are a few programs too large for 32bit Windows. For example RPro > Atmospheric > Atmos Harp needs 2.4 GB of RAM.

Hey thanks, scook!
 
But that's not it.
 
I have loaded other patches, that work once or twice, but then they don't. My memory allocation never goes over the 3.46 my 32bit system has available. 
 
For example I just tried to load "Atmospheric>Atmospheric Nightmare" and it hung. I closed the synth properties window, and re-opened it. Loaded the same program and it now works! I still have 1.7 GB RAM available, even with Firefox and this forum open on my PC. 
 
By the way, closing the synth properties window works temporarily. But I still get the appcrash when I close the project or Sonar, following the "hang" while loading a program in Rapture Pro.
 
See what I'm talking about?
 
BTW, the Cakewalk page has this listed as requirements for Rapture Pro ( ref: 32bit):
Formats: VST2i, VST3i, AAX, Standalone Version (32 or 64Bit)

I am aware of the system requirements for RPro and the limits of 32bit Windows.

Agreed, but since this problem doesn't appear to be related to the 32-bit limits, should I file a bug report?

that would be your call

scook
that would be your call

OK, but I do understand it's not practical moving forward with development to continue support both 32 & 64-bit on the latest versions of applications. I ran into that recently with Adobe Photoshop Lightroom, which is only supporting 64 bit systems now. I would just prefer that if that's the direction Cakewalk is taking, that they do state that in the system requirements.

It is just a matter of time. Cakewalk has been encouraging adoption of 64bit for some time. IIRC, Cakewalk switched from 32bit to 64bit as their primary test platform around 2010.

Well since everything else works fine, I guess I will just skip the upgrade to RPro.
When I upgraded to a modern PC platform several years ago, I gave serious consideration to the 32 vs 64bit question.  I decided that since I did not yet need the memory map size provided by 64bit, I would stick with 32bit for now, for the legacy driver compatibility.  There is really very little proven performance advantage of 32 vs 64bit. That's a myth. It's all about memory.
 

Update: I have tried this Rapture Pro demo again with a demo version of Sonar Platinum (x86), which I expect will soon be my next Sonar upgrade (lifetime).  I cannot seem to crash Sonar anymore, but the VST still hangs randomly while loading a Rapture Pro Factory Library patch.  Closing the VST GUI and re-opening it seems to clear the hangup.  Then the same patch loads OK.  This problem seems harder to reproduce in Platinum vs. X3, but is still there.
 
I have also tried installing the Rapture Pro multisamples on either my C: or D: drives, with no improvement either way.  Rapture Pro is installed in the path D:\Cakewalk\Rapture Pro. That is the default and is grayed out on the installer, so I cannot change it. I have some of my other Sonar content aimed at D:, so the installer must have picked up on that.
 
As far as the standalone version goes, it is still fairly easy to cause an appcrash while auditioning the Factory Library patches.