Has anyone installed Rapture Session on their system alongside Rapture Pro without issues? I have deliberately not installed Dimension LE and Rapture LE from the Sonar Professional Manchester bundle because I already have the Pro versions of both installed. Rapture Session however boasts a simplified interface and a wealth of sounds so I thought it might be a useful addition.

If you already own Rapture Pro, there is nothing new in Rapture Session content.

Yes, but I haven't re-installed the original Dimension Pro or Rapture. There is absolutely no need.

I have both Rapture Pro and Rapture Session installed (because I test on both platforms) under Windows 10 without issues.

FYI - I just tested multiple instances of RP vs. RS to see if Session drew less CPU...they seem more or less equal. As far as I can tell there's no CPU penalty for using RP.
 

I can do you all one better. I have DM Pro Rapture, Rapture Pro and Rapture Session all installed.  I have no problem with any of them.

For reasons of backwards compatibility, I continue to have Dimension LE, Dimension Pro, Rapture LE, and Rapture installed as VST2s alongside Rapture Pro and Rapture Session installed as VST3s. I have no operational issues caused by this arrangement.
 
The only problem I have found is of my making, in that in a moment of housekeeping zealotry, I purged the .wav files from the Multisamples, where .flac replacements exist, completely forgetting that this would cause "multisample not found" probs in some of the older projects. In these cases, I tend to substitute-in Rapture Pro, rather than waste time tracking down and reloading the .wavs.
 
As an aside, I have no idea why Rapture Pro and Rapture Session appear only as VST3s in my set-up, as the VST2s appear to be installed, but are not detected by Sonar's plug-in scan. I decided just to live with that.

ChristopherM
 
As an aside, I have no idea why Rapture Pro and Rapture Session appear only as VST3s in my set-up, as the VST2s appear to be installed, but are not detected by Sonar's plug-in scan. I decided just to live with that.

Hi. I think you have "replace vst2 with vst3" checked in vst settings.
All the best.

No, that's not it, Zargg71. I have that unchecked as a matter of principle, because I don't trust automatic substitutions. The VST2 versions are being ignored by the scan for some reason, but I'm not going to waste time investigating. I just mentioned it in a spirit of full disclosure.