I've had rapture pro 32 bit installed for about 12 months now, and I gave up using it, virtually a day or 2 after installing it, as it crashed all the time.
 
I hadn't opened it, until half an hour ago, and still having same crash issues, despite now having 16gb of ram in my pc.
 
The patch causing the problem this time, is 'Ambiant Acceptance' or 'AmbiantAcceptance' (yes there are 2 patches, one has a space), from the rapture pro factory library.
 
After a crash, I note that RapturePro_32.exe still appears in my task manager and I can't end the process, as 'access is denied'
Eventually, after abot 10-15 minutes, the process disappears from the task manager, and I can open rapture pro again.
 
I'm now running windows 10, but I was running windows 7 before, and rapture pro still crashed back then.
 
No help I'm afraid, but at least you know you're not alone.
 

Most machines which 16GB of RAM run a 64bit OS otherwise there would be no reason to have that much RAM. I would recommend using the 64bit exe in this case. Not sure why "Ambiant Acceptance" would crash the 32bit version. It is a very small program and runs fine for me in 64bit RPro. I do not have a 32bit OS to test and do not want to mess with installing 32bit software on a machine running 64bit unless absolutely necessary.

Well I'm really glad that I tried the demo first.  I have sent the link to this forum thread to Cakewalk pre-sales support.  Still waiting to hear something back.
 
I would be really surprised if this cannot run correctly due to it being a 32-bit program. None of the demo patches are huge. In fact, most of them are relatively small.  Smaller than most of the large multi-samples I have in Dimension Pro(x86).
 
My Sonar X3 Producer(x86) is rock solid.  All of the other Cake synths(x86) are rock solid, never crashing. VST2(x86) & VST3(x86) from NI, Arturia, u-He. etc., don't give me this trouble either.
 
I can run my projects with multiple virtual instruments and effects at 48000/24 with ASIO at 1.3msec latency (I have tried bumping the buffers up, but without any improvement).
 
I usually have at least 1 GB RAM to spare, and generally never exceed 25% CPU use.  I run with a 250GB Samsung EVO SSD, with 50% free space.
 
I have re-configured all of my Cakewalk Content paths from my spinning D: drive to my C: drive (SSD) and re-installed the Rapture Pro (x86) demo.  Same issues ...
 
I even installed the SPLAT(x86) demo, which works great on my PC.  But Rapture Pro still has the same issues in the latest Sonar.
 
The fascinating thing here is that the same patch does not always cause the problem. Sometimes it will load it, sometimes not.
 
The problem occurs ONLY when auditioning patches, as it attempts to load.  If the patch loads OK, then everything stays cool.  There are a few that seem to be repeat performers, as well as some that never crash it.
 
While 64-bit is the preferred and recommended platform, and obviously the way forward, this should still work. It is listed as a supported product for x86.  Why is it just this one program???

sako
I've had rapture pro 32 bit installed for about 12 months now, and I gave up using it, virtually a day or 2 after installing it, as it crashed all the time.
 
I hadn't opened it, until half an hour ago, and still having same crash issues, despite now having 16gb of ram in my pc.
 
The patch causing the problem this time, is 'Ambiant Acceptance' or 'AmbiantAcceptance' (yes there are 2 patches, one has a space), from the rapture pro factory library.
 
After a crash, I note that RapturePro_32.exe still appears in my task manager and I can't end the process, as 'access is denied'
Eventually, after abot 10-15 minutes, the process disappears from the task manager, and I can open rapture pro again.
 
I'm now running windows 10, but I was running windows 7 before, and rapture pro still crashed back then.
 
No help I'm afraid, but at least you know you're not alone.
 

Did you get the same fault module and exception code as I showed in post #1?
 
It looks like you are running the standalone .exe version of Rapture Pro. I get the same "After a crash, I note that RapturePro_32.exe still appears in my task manager and I can't end the process" when I get a standalone crash.
 
I assume you are running Windows 10 (64-bit) currently?

abacab
 
Didn't see a fault module or exception code.
 
 
Yes I am running the standalone version of rapture pro.
 
OS: Windows 10 Home 32-bit
 
Weird thing is, I opened rapture pro a few hours later and had no issues with loading patch 'Ambiant Acceptance', but it crashed this time, on trying to load a different patch altogether.

Well as a last resort, I tested this on my Windows 8.1 (x64) laptop.  It is fully patched and there is no other DAW or audio software installed on this PC.
 
I downloaded Cakewalk Command Center and installed the latest version of Rapture Pro (x86) 2.0.4.25.
 
Launched the standalone RPro, and bazinga!  On the 2nd patch I auditioned, I got the same appcrash, with the same fault module, and exception code as I did on my DAW(Win 7 Pro x86) PC.
 
So with two different PC's, two different OS's at different bit levels(x86 & x64), the same RapturePro_32.dll gets the same error code.
 
What gives here???
 
Update: I just tested the Rapture Pro(x64) demo version 2.0.4.25 on my laptop(x64).  I auditioned every sound in the Factory Library that was included with the demo.  Solid as a rock!  Could not get it to crash.
 
I really hope that someone at Cakewalk has an answer for when the x86 version will be patched to work correctly.

sako
now having 16gb of ram in my pc.
 
No help I'm afraid, but at least you know you're not alone.

Thanks for your feedback!  But are you aware that if you are running 32-bit Windows, your system cannot access 16GB RAM. It should only see somewhere between 3-4GB.  For example my Win7 Pro(x86) only sees approx 3.4 GB of the installed 4GB.

scook
Most machines which 16GB of RAM run a 64bit OS otherwise there would be no reason to have that much RAM. I would recommend using the 64bit exe in this case. Not sure why "Ambiant Acceptance" would crash the 32bit version. It is a very small program and runs fine for me in 64bit RPro. I do not have a 32bit OS to test and do not want to mess with installing 32bit software on a machine running 64bit unless absolutely necessary.

In my testing, I do not see any correlation to the size of the patch.  Only the fact that RapturePro_32.dll seems to be the single point of failure, regardless of the patch involved. On both host either x86 and x64 Windows.