This is the full version of Rapture, and I've also downloaded & installed the Digital Sound Factory Filmscore expansion.

Any project with this in is cashing - but only in 64 bit Sonar, 32 bit seems fine.

The project will play up to a point, then it will stop and I get a nasty, fairly low pitched grinding noise from the monitors. At this point, Sonar is totally unresponsive and the only way to kill it is through Task Manager.

I have uninstalled Rapture & reinstalled it a couple of times, but it doesn't make any difference.


Any clues about this one anyone?

Just to add, freezing Rapture cures the problem, though this is far from ideal.

I vaguely remember an issue with the "Filmscore Expansion" and the full version of Rapture being discussed here fairly recently (some months ago). Unfortunately, searching these forums for recent posts seems to be..., problematic for some reason. Maybe you'll have better luck.

AFAIK, an expansion pack could only consist of wavetables, samples, sfz files and element setups..  with the obvious preset .prog's built from that content...
So my question is, "why would an expansion pack cause Rapture to crash, any more than just loading a "factory sound," or using the factory wavetables to design a sound?

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.

Bristol_Jonesey


Just to add, freezing Rapture cures the problem, though this is far from ideal. 

I have noticed this too.  I believe that is because the synth is, "put to sleep," when frozen.  ( For lack of a better phrase. )

Bristol_Jonesey


This is the full version of Rapture, and I've also downloaded & installed the Digital Sound Factory Filmscore expansion.

Any project with this in is cashing - but only in 64 bit Sonar, 32 bit seems fine.

The project will play up to a point, then it will stop and I get a nasty, fairly low pitched grinding noise from the monitors. At this point, Sonar is totally unresponsive and the only way to kill it is through Task Manager.

I have uninstalled Rapture & reinstalled it a couple of times, but it doesn't make any difference.


Any clues about this one anyone?

I see..  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



IMHO..  This is worth verifying.  Even if you think you have 1.2.2 installed..  I had a lot of trouble getting that installation proper.  For many months I thought I had 1.2.2 and it was really 1.2.1 and I thought it was 64, but it was really 32.

I had lot of trouble with 1.2.1..  I had a ton of trouble with 1.2.0.  I am doing OK with the 1.2.2 64 bit.  Things are not perfect..  ANd I am not using Rapture in Sonar per se..   I am using Rapture loaded in my Rewire Slave.  I know that does not help..  but..  I imagine that the 64 bit 1.2.2 is ok in Sonar.  Are you 100% sure, what you've got there is 1.2.2?

There are instructions on this page..  to install the 1.2.2  ---------  I READ THESE WORD FOR WORD DURING MY LATEST INSTALL OF RAPTURE PROCESS.  WORD FOR WORD....  http://www.cakewalk.com/Support/kb/reader.aspx/2007013167

When you verify the .dll, if it is anything less than 1.2.2 file version 1.2.2.7..  than i highly suggest a complete uninstall.  including registry folder delete.

Than..  1.1.0, 1.2.0 ( I skipped 1.2.1 with no problem. ) 1.2.2  ( read the 1.2.2 install instructions. )

I also suggest..  Only installing the 32 bit on 1.1.0..   the 1.2 + installers give you a choice for 32 or 64..  I only installed 64.


So..  I've finally got Rapture 1.2.2, file v1.2.2.7 64bit running on my system.  It still has a problem, specific to my Renoise ( rewire/slave) that has to do with popup boxes..  ( This for me, is not a mission critical bug. )

I have not had a crash with Rapture 1.2.2 yet.  Knock on wood!

So, I can definitely confirm that 1.2.2 is running solid.

I had such a mess with 1.2.1 and 1.2.0 that I even tried 1.1.0 for a week, till I finally gave up, and said, "damn, I need to get the 1.2.2 installed proper."  To do that..  I had to read the directions, and follow them to a T.


I sure hope that helps,

Cheers

Thanks so much for posting up those details.

I can confirm that I'm running 1.2.1 so I need to download the updated version.

Cheers mate! 

Well I've downloaded & installed version 1.2.2 but still get the same problem, so I'm wondering what to do next.

The only solution is like I said before, to freeze Rapture before playing the project, but this isn't exactly conducive to a creative workflow.

Also, opening the same project in 32 bit Sonar results in an instant BSOD.


Less than happy with Rapture.

Back to Dim Pro for now.

If forum search are giving you bad results use google.

Just type in:

site:http://forum.cakewalk.com/ some search words here

I've been able to dig up stuff I was looking for a lot easier that way and a lot more relevant results.

Thanks, Kenneth, but there's not a lot relating to my particular problem.

Hi Jonesey, I have the same problem with version 1.2.2.  I've discovered that I can safely run one instantiation of Rapture safely, but more will bring the program to a halt.  As you noted, freezing Rapture is the work around, and I can run numerous instances of Rapture (or Dim Pro) if I freeze as I go along.  If I need to edit a part, I just unfreeze it, edit, and refreeze.  It's kind of a PITA, but it does work.

Thanks Lynn.

I think for now I'll stick with it and see what X2 brings to the table.