VST vs. DXi (Can't we all just get along?)

"A friend" was wondering what the difference between these two synth types really was. He was hoping for some non-technical jargon that didn't mention the actual proprietors of the format but simply explained what the differences between these were. Obviously, I couldn't explain it in such layman terms so that he (or she) could understand so I think that "my friend" is still mystified as to why a plugin has to appear twice in his P5 instrument list...and which would be better to use and why?

I figured it would be beneficial to the new initiates here if someone could explain it to them...er...someone other than me, you know... I don't wanna bore you... and...um...my "friend" would appreciate it too!

ORIGINAL: wrench45us


Micrsoft has a standard DirectX interface for 'media' of all sorts, including sound. I think its up to verson 9. So Cakewalk has this preference for dealing with sound devices through the 'native' Windows' interface DirectX, instead of through the standard vst interface specification.

i remeber more than once at early road shows hearing the Cakewalk reps indicate there were advantages to this, but I don't recall any details.

it should be noted that any given host wraps or adapts sound devices in some way to inteact with their host program. Cakewealk chooses to wrap the vst in Microsft's DirectX interface.

I don't know what's gone on with Sonar 5, but it sounds like the wrapper is now somehow attached or linked to the plug more directly so it's more portable. (that's a guess)
And given that OSX is in the future the whole wrapping issue must be occupying a few brain cells at CW these days.

ORIGINAL: Brad Abrams
So what’s WinFX? Well, WinFX is an object-oriented API that leverages the .NET framework and exposes the breadth of Longhorn, the breadth of the operating system to developers.