On March 3, 2017 Steinberg released v3.6.7 of their VST3 SDK.
As with 3.6.6, they changed a lot of stuff compared with the previous version. And, as with 3.6.6, the older VST3 plugin code will not compile properly in the new SDK. This includes the Steinberg sample code as well. This seems to be a pattern, but it is all in the name of progress, I suppose. They also removed the Visual Studio and XCode sample project files (not the sample project code, but the compiler setup files) requiring you to use CMake to generate these files if you want to use the sample projects. This binds your VST3 SDK to your compiler version (2013 or 2015) as well as your chosen bit depth (32 or 64).Â
I've been working with the new SDK and I am still in development with it, for the next release of RackAFX.
One thing I have already done is to modify the base project's vcxproj files to at least be able to compile in either 32 or 64 bit mode, which is not possible (I think) when you use CMake as you must choose the compiler project generator's bit depth when you run the software. If anyone knows how to use CMake and get both the 32 and 64 bit projects at once, please let me know. You can use the contact form on the main page.Â
Until then, RackAFX v6.8.1.x still uses the 3.6.6 VST3 SDK for the Make VST functionality. Once the new SDK is solidified, I will incorporate it into RackAFX. Most likely, I will need to obsolete the 3.6.6 code and force everyone to move to 3.6.7 rather than trying to support multiple versions. At this point, 3.6.6 is now obsolete and I don't think they will support any questions regarding it anyhow.
I do have the Make VST projects running with the new SDK - the changes they made are not overwhelming and the also cleaned up the base library project so that it uses about 1/2 of the files. They did make changes to some objects, deleting the TArray and TDictionary objects and replacing them with vector based stuff - this messed up the custom code for Presets. They made a change in the compiler settings for the Runtime Library - also not a big deal, but it means that the vcxproj files will change. I have not yet checked the VSTGUI4 code, but it does compile without changing anything there.Â
The larger issue I have is with setting up theÂ SDK - I need to make this as painless as possible for end users, I'm guessing many have never used CMake. Most likely this will involve the user needing to create a couple of directories and placing the base vcxproj files in there (which is what happens with CMake).Â
Yeah, I've never used CMake before, and it's probably been about 20 years since I've used "make" back on Unix.
Even though the last VSTGUI changes required some re-writes for everyone I think the changes were for the best. There were several fixes and consistency improvements with the graphics drawing. Sounds like this may be true for the SDK as well, other than the CMake stuff.
Here are the release notes:
Details about preparing the VSt3 SDK 3.6.7 for use are here:
After make vst I get error when preparing the VSt3 SDK 3.6.7 using visual studio 2017,
I follow the steps fromÂ http://www.willpirkle.com/prep.....7-for-use/Â but i have visual studio 2017 instead of 2015 and 2013 , any way to solved using VS 2017?
usingÂ SDK 3.6.6 works good with VS 2017!
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Moderators: W Pirkle: 689