yeah it seems the sdk was refined more for mac use in my experiences..Mark Vera wrote:The path is set in the project to the global VST3 path the SDK mentions. Silly place, and puzzles me why user path is omitted officially under Windows when it's "supported" in Mac. Especially now that Vista may have limitations on installings stuff to global paths.VitaminD wrote: in other news.. I *was* compiling and getting the plugin, the problem was its labeled as a *.vst3 so I didn't realize what it wasIt was also on an entirely different drive than the one with my SDK on it..
![]()
in other other news.... I just realized that my host of choice (orion) doesn't recognize vst3 plugins nor when they're relabeled as DLLs... so all of this was pointless to me
But you're right no VST3 under Orion, quite obvious that the SDK was released just hours ago.
oh and well I was hoping that (somehow I knew it was highly unlikely) the vst3 plugins would be backwards compatible to vst2.4 but obviously this isn't the case
