November 27, 2014
I wanted to ask what is the biggest difference between compiling with RackAFX and compiling an exported project. I have naively not saved older versions of the Steinberg SDK and RackAFX making it difficult to compile exported projects with the new version of the SDK and RackAFX. I understand with RackAFX we do not have access to the 4 digit plugin code and other elements that are set when exporting projects. Would you foresee issues for the end user if I was distributing VST2 and VST3 plugins that had been compiled within RackAFX if I had no requirement to edit the source files outside of your program?
Looking forward to the new version and book when you get round to releasing.
January 29, 2017
I think you are referring to the "RackAFX-DLL-as-VST-DLL" paradigm where you compile your RackAFX plugin and it automatically becomes a VST2/VST3 plugin? In that case the 4-digit code is not available but the FUID is.
This issue is one of the reasons for the end of the RAFX1 API. In order to get that paradigm to work, you had to link your plugin to a massive pre-compiled library. That library has the 4-character code embedded in it, but the FUID (which is also used in the VST2 wrapper) was generated when you created the original project.
RackAFX7 and RAFX2 have cleaned this up - so that you have to compile the plugin separately as a VST3, etc... and in this case you now have access to all of the VST magic codes.
I am planning on releasing RackAFX7 by Jan 1 2019.
Most Users Ever Online: 55
Currently Browsing this Page:
Guest Posters: 1
Newest Members:Third Audio, LRT, TomJ, Giscard, Alejandro Florez, Tomaso, Jonas, Ralph, Wayne, Steve Duell
Moderators: W Pirkle: 267
Administrators: Tom: 67, JD Young: 80, Will Pirkle: 0, W Pirkle: 267