Was tinkering with 32bit mix opened on new 64bit compute (details in sig), and got each time on addition of track using, respectively, DimPro, Rapture, S.I.Drummer, SessionDrummer3, milky white screen with oblong message: Sonardpr.exe has stopped working, along with deep, grinding noise from monitors. Only way then to re-open X1 Producer Expanded is to re-boot computer. Never happened in 32bit version. What have I done, or am I doing wrong?? Don't want the whole thing to go t*ts-up!!

I have been using Rapture in my Rewire Slave..  Both Rapture and my Slave are confirmed, "very latest, and properly installed version."

I do have stability with Rapture, but!  A few issues:  The first issue.  In an image below, A is Rapture as a Microhost, B is Rapture in my Rewire Slave.  As you can see...  64 bit, 1.2.2 Rapture will not show pop up boxes, detailing certain information, in Renoise 2.8.1

Ok.. But I have stability, and I have an inkling as to why that may be..  Renoise allows for several options on, "how to run your vst plugins."  There are specifically two separate windows on this regard where you can tweak settings.  Window 1.. Gives the option to, "run all plugins in Sandboxes, ( separate processes. )  This is great!  I get a lot more stability from all my plugins with this option chosen.  However, I give up a major feature!  When this option is chosen, I can not cut and past between things like Rapture Instance 1 and Rapture Instance 2...  Ok..  No matter though, cause I like the stability!

I have looked in Sonar X1 to find this, "run all plugins in sandboxes," option.  I can not find it..  If it exists, I suggest, "we try this."  If you find this option, can you please post a screen shot in this thread!  

Another Plugin Options Window Renoise has, is very much like, "the Cakewalk Plugin Manager."  In this window Renoise gives several options..  I am also putting an image below...

With all that said..  I tested Rapture in Sonar X1..  I tested four instances, and got a crash when I turned on an Arpegiator...   I am sure there are other crashes....

Rapture needs to be fixed!   It is very important that it is fixed!  It is also, "my biggest complaint."

I too am upgrading to Sonar X2...   But I really, really, really want Rapture working!  Its got some bugs, they can be confirmed...   Please Cakewalk, work on this synth!

Cheers

Gives the option to, "run all plugins in Sandboxes, ( separate processes. )

 
I think Repear has something similar.   It would be nice to have something similar in SONAR at some point.  Not that it would fix anything broke in Rapture, of course.
 
Does anyone have this problem with a single instance?   Just curious since I've never run more than one, and haven't had any real issues with it.

I think the answer is: Rapture has some very mission critical, and noticeable bugs.  Regardless of .prog loaded, expansion packs bought, user designed sounds from factory or after market wavetables, sfz files, or other type of content that can be loaded into a Rapture Element.  Have you owned Rapture for a while, or did you recently upgrade?  Are you 100% sure you are running 1.2.2?  This can be verified by right clicking on a Rapture .dll --- > properties ---> details

I have Rapture 1.2.2 and have had issues since I bought it several months ago on the $20 deals. 
I also bought the filmscore patch and couldn't get it to run for more than a few minutes without crashing X1.
I wound up uninstalling both and only installed Rapture 1.2.2...now I just get a grey screen in the Rapture UI...got tired of dicking around with it and found stuff in Z3ta 2 that sufficed.
I should also confess I haven't even contacted support so I can't complain... but I guess I've been hoping more threads like this would come up so that maybe CW will take notice.

Thanks for all your feedback people, seems it's not just me with these problems.

As far as I can tell, there's only issues with Rapture when there's more than one instance in a project. As noted above, freezing all but one instance usually fixes the problem, though this is a workaround at best and doesn't address the underlying bug(s) within Rapture.

There also seems to be a correlation with the Filmscore add-on pack, certainly in a 64 bit environment.

Now here's another lump of food for thought - I have Sonar X1 installed on my general internet/office/email/gaming machine downstairs. I only have the 32 bit versions of all the software installed - including Rapture, and this installation behaves properly and has NEVER crashed.

This in itself has made me raise my eyebrows as the computer has not been optimized for running DAW software in any way - it's a straight forward home build running Win 7 on an i7 cpu and 24Gb RAM.

Interesting bit of text in the Readme:




"When installing Rapture VST on 64-bit Windows systems, only the 64-bit or 32-bit VST can be installed at one time.  If multiple installations occur, only the more recently installed VST will appear in your host."

Bristol_Jonesey


Interesting bit of text in the Readme:




"When installing Rapture VST on 64-bit Windows systems, only the 64-bit or 32-bit VST can be installed at one time.  If multiple installations occur, only the more recently installed VST will appear in your host."

Yes, I remember seeing that when I upgraded from 32 to 64.

Now, the interesting thing is, I have both installed and they seem to work perfectly.
The same with DP, I have both 64 + 32 bit versions installed and they work fine.

I have folder shortcuts between DP and Rapture samples too, so the samples from each are available in both DP and Rapture.

I didn't do any registry hacks to get things working, though at the time I installed the 64 bit versions (at 8.5.3) I wondered if I might have to. In which case I wouldn't have bothered. Not really into fiddling with that if I don't have to.

I think I made some scribbly notes when I did it, so I'll see if I can find them.
Not that I'd recommend you or anyone else try it ... it's not supposed to work :-)

I'll come back if I can find those notes - and decypher them.


Cheers - Cliff

That would be helpful Cliff - thanks!

Such a great synth too...  Will do absolutely anything and everything.  

@ Bristol_Jonesey,

What about signing up as a beta tester?  Would you have time for it?  Because they way I am using the synth, and having a confirmed 1.2.2 install, I don't think I would be much help as a beta tester.

We would need people hosting it in Sonar...  Although I reckon, before X2 is released, I ought to call support again, and lodge a complaint about my pop-up box problem...

I really hope this synth makes it to 1.5 and beyond, but I've got no idea what is going on, "behind the scenes," in the Cakewalk offices....

Are you now 100% sure, that after your re-install, you've got 1.2.2?  You rechecked the .dll, and its all confirmed and everything?

Its a real source of aggravation for me too, only because, "I like this software so much."  That makes it all the more of a problem.  If I wasn't so happy with Rapture, and Sonar, every single thing inside Sonar from the ProChan to the ancient DX Gizmos from "Cakewalk 1.0." or whatever...  + Z3ta 2.0...   I like all these things so much..  so I hope, hope, for a few more Rapture updates, and definitely a 1.5, and eventually, a 2.0



Cheers

Yeah it's definitely 1.2.2

I renamed the old one and added .old to the fiename, so it wouldn't pick it up.

Wouldn't have the time for any Beta testing mate - I can barely get quality studio time as it is