ChristopherM
BTW, I was a little surprised to find that Rapture Pro has no VST2 and comes as VST3 only.

RPro includes both VST2 and VST3 formats

scook
 
RPro includes both VST2 and VST3 formats

... and I'm surprised to hear that, because I came to my conclusion when I realised that I couldn't find a VST2 version of it, and so I took a look at Cake's own Product page about it and saw there that it says "NOW AVAILABLE IN VST3 | AU | AAX" and nowhere on the site does it seem to mention any other flavour of VST. So I gave up looking for it. Although I am not doubting what you say, Steve.

I believe you may be looking at the Mac info, for details see http://www.cakewalk.com/P...re/System-Requirements
The VST2 version is used by the stand alone minihost. The default path to both the dll and minihost is "C:\Program Files\Cakewalk\Vstplugins\Rapture Pro"
 
edit: fixed link

Christopher, where are you looking for the VST2 version?
 
If you're only looking in Sonar's media browser it might not be visible, depending on what you've got set here:
 

Steve: your link returns a colourful Page Not Found, but I had found the reference exclusively to VST3 simply by using the Products pull-down at the top of Cake's home page. I confess I didn't spend too much time researching it but just put 2 and 2 together and made 4 (or rather I couldn't see 2 at all but could see 3). I can see the dll lurking next to the mini-host now, but I am not seeing it in Plugin Manager, although it lies in one of my scan paths (along with umpteen other CW VST2s that are available). I don't have the time to delve deeper into this mystery today, regrettably.
 
Jonesy: I have left both of those boxes unchecked, because experience tells that typically any such glib automation methods often work fine most of the time, but when they occasionally get it wrong, the mess outweighs any advantage. Hmm ... sorry ... I must be in an atypically cynical frame of mind today: I'll be better after breakfast, I promise.
 

the link above is fixed

ChristopherM
Jonesy: I have left both of those boxes unchecked, because experience tells that typically any such glib automation methods often work fine most of the time, but when they occasionally get it wrong, the mess outweighs any advantage. Hmm ... sorry ... I must be in an atypically cynical frame of mind today: I'll be better after breakfast, I promise. 

 
No need for apologies, but it does explain why you are seeing both the VST2 & VST3 versions

It may also be worth noting that, unless a fix has gone in since the last time I checked, FX Chains do not play well with VST3 plugins.

VST3 and VST2 are different plugin authoring standards. Its really a misnomer that its called VST3 since its not even close to being the same thing as VST2.
VST3 has a more modern design for software development but it abandoned a few more traditional mechanisms for MIDI data. There is no notion of MIDI SYSEX or controller events in VST3 for example. Its replaced by generic parameters. There are a few new extensions in VST3 such as built in mechanism for having client server based plugins, and for multiple MIDI output ports.
For most practical purposes VST2 and VST3 plugins work and sound the same and almost all vendors have a lowest common denominator implementation of VST3. IOW only VST2 compatible capabilities are available for the vast majority of VST3 plugins.

Noel Borthwick [Cakewalk]
There are a few new extensions in VST3 such as built in mechanism for having client server based plugins, ...

 
That'll take us to a whole new level of having to be online and logged in.