Helpful ReplyRapture Pro Update 4 Demo Crashing in 32bit

Author
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
2016/05/19 20:59:13 (permalink)

Rapture Pro Update 4 Demo Crashing in 32bit

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
 
 
 
post edited by abacab - 2016/06/10 19:34:26

DAW: CbB; Sonar Platinum, and others ... 
#1
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 21:15:40 (permalink)
There are a few programs too large for 32bit Windows. For example RPro > Atmospheric > Atmos Harp needs 2.4 GB of RAM.
#2
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 21:53:57 (permalink)
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)
post edited by abacab - 2016/05/19 22:24:22

DAW: CbB; Sonar Platinum, and others ... 
#3
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 22:21:06 (permalink)
I am aware of the system requirements for RPro and the limits of 32bit Windows.
#4
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 22:41:38 (permalink)
Agreed, but since this problem doesn't appear to be related to the 32-bit limits, should I file a bug report?

DAW: CbB; Sonar Platinum, and others ... 
#5
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 22:43:45 (permalink)
that would be your call
#6
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 23:01:42 (permalink)
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.



DAW: CbB; Sonar Platinum, and others ... 
#7
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 23:15:05 (permalink)
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.
#8
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/05/19 23:41:49 (permalink)
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.
 

DAW: CbB; Sonar Platinum, and others ... 
#9
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing 2016/06/04 16:53:35 (permalink)
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.

DAW: CbB; Sonar Platinum, and others ... 
#10
sako
Max Output Level: -90 dBFS
  • Total Posts : 2
  • Joined: 2014/12/20 13:27:43
  • Status: offline
Rapture Pro Demo Crashing in 32bit 2016/06/10 14:49:25 (permalink)
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.
 
#11
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 14:59:44 (permalink)
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.
#12
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 17:24:41 (permalink)
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???

DAW: CbB; Sonar Platinum, and others ... 
#13
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 17:39:59 (permalink)
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?

DAW: CbB; Sonar Platinum, and others ... 
#14
sako
Max Output Level: -90 dBFS
  • Total Posts : 2
  • Joined: 2014/12/20 13:27:43
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 20:42:26 (permalink)
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.
#15
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 21:37:54 (permalink)
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.
post edited by abacab - 2016/06/10 22:33:17

DAW: CbB; Sonar Platinum, and others ... 
#16
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 22:27:19 (permalink) ☄ Helpfulby pwalpwal 2016/06/11 05:04:20
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.

DAW: CbB; Sonar Platinum, and others ... 
#17
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Rapture Pro Demo Crashing in 32bit 2016/06/10 22:37:08 (permalink)
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.

DAW: CbB; Sonar Platinum, and others ... 
#18
Jump to:
© 2022 APG vNext Commercial Version 5.1