Getting multiple errors with the Cmake export (namely: "CMake Error at cmake/vst_cmake/CMakeLists.txt:24 (include): include could not find load file: [Multiple file instances]"), which I am currently assuming is to do with the fact I only have VST sdk version 3.6.11, with no VST2 SDK as it has been discontinued by Steinberg.
From what I can gather, only SDK 3.6.9 is supported in current exports with RackAFX and not 3.6.11, which would be fine however I can't for the life of me find SDK 3.6.9 due to steinberg not having access to any archive versions. Can anyone send me the files for 3.6.9 or otherwise help with this issue?
Yeah this is a real pain and Steinberg is aware of it (the issue pops up repeatedly on their Forum). It appears that they immediately delete old SDKs and remove links from older Forum threads as well...
I am working on a new version for 3.6.11 support (as well as the latest AAX SDK, which also did the same thing and broke existing projects... sigh).
Use the contact form on the bottom of the main webpage here and email me directly and I'll try to find a 3.6.9.
I updated RackAFX to v22.214.171.124 and started using the CMAKE universal exports for AAX, AU, and VST. I am using VST3 SDK v3.6.11
AAX and AU plugins are building without issues and I am getting this error for CMake on the VST phase:
"Make Error at /Users/Merril/Development/Plugins/ALL_SDK/VST_SDK/VST3_SDK/cmake/modules/AddSMTGLibrary.cmake:112
the variable public_sdk_SOURCE_DIR IS NOT SET. Please specify the path to public.sdk's source dir."
I am using the standard Universal Folder tree..
Is this related to using VST SDK v3.6.11? I think I should be using v3.6.10 based on other threads here but can not locate the older SDK download.
Yes, this is related to 3.6.11 - Steinberg added another CMake variable to one of their CMake modules. This is one of several issues that caused me to sunset RAFX1:
You can manually edit the exported project's outermost CMakeLists.txt file to add this new variable around line 104:
# --- new in 3.6.11
# --- VSTGUI4: NOTE: we use our own VSTGUI4 folder - portable to new SDKs where you
# may not want to update VSTGUI just yet and won't interfere
# with VST3 SDK whatsoever. You do NOT need to customize this path!
However, there are a few other issues:
- Steinberg now defines the constant "pi" in a way that conflicts with the same #define in the RAFX1 pluginconstants.h file as well as the pluginobjects.cpp file that uses it; you can redefine it if you like in pluginconstants.h (e.g. #define rafx_pi) or just get rid of it and substitute the actual value 3.1415926..... in both of those files.
- VSTGUI4.7 (which ships with SDK 3.6.11) once again has changed stuff (significantly) which breaks the code in the RAFX1 plugin files GUIViewAttributes.h and GUIViewAttributes.cpp -- these are only used with Custom Views, so in most cases you can remove these files from the RAFX1 project without too much pain (of course you'll need to remove any #include "GUIViewAttributes.h instances as well)
- VSTGUI4.7 also breaks even more code in the RafxEditor files for the AU and AAX ported projects (these are not used in the VST3 ports)
Those issues were the final nail in the RAFX1 coffin (thanks Steinberg?)
However you can still use SDK3.6.10 instead with the last RAFX1 release (be sure to CMake the sample projects first to make sure your setup is good).
As you saw on the "sunsetting" thread above, RackAFX7 projects (and the ASPiK projects it exports) use the built-in, VSTGUI4-approved mechanisms for generating the GUI, rather than the RafxEditor and custom-view support files from RAFX1; in addition the "pi" constant is defined in a different manner as kPi and kTwoPi to eliminate conflicts with other libs that use "pi" as the constant.
Most Users Ever Online: 55
Currently Browsing this Page:
Guest Posters: 1
Newest Members:Ray C., Jon R., Pat, Jan, Ben_1, shane, teknojunque, David Richter, Nick45, EEkros
Moderators: W Pirkle: 325
Administrators: Tom: 69, JD Young: 80, Will Pirkle: 0, W Pirkle: 325