I was watching the video on YouTube where as the first program Will creates "helloVolume". That's exactly what I was looking for to begin with. I wonder though...if we wanted to export this "helloVolume" program so that we could have an executable application and then use it as a standalone plugin how to do it? I haven't finished watching the series of videos on YouTube yet, maybe it's shown there? Thanks in advance.
"Standalone plugin" is nice 😉
If you want to "export" a plugin to a stand-alone program, you "just" need to program actually a "stand alone audio application" around it, s.th. your DSP code and UI code is no longer a plugin but linked into that program directly.
But trust me, it is not worth the effort - you will spend month until it works and you will not have learned anything about DSP. That's actually one of the reasons why RackAFX exists 😉 You don't want to bother with this stuff at the same time that you are trying to be creative with your DSP algorithms.
But there are some things that are the closest thing to "standalone plugin":
- The VST3 sdk provides the VST3PluginTestHost - it has some quirks, especially when you try to load audio files, but it works great with input from your audio device.
- There is SAVIHost, very old, I had some issues with multithreaded plugins (the SAVIHost does not stick to the VST3 rules in that regard)
- In the JUCE framework there used to be a plugin host example which can load plugins
But I think RackAFX is your best bet at this point, especially if you are not that experienced yet with debugging plugins in hosts.
So there is no way, if not complicated, to use these plugins in a daw as a reaper etc... On will's YouTube channel there is a video (old though) where he shows that he takes the dll, copies it in the folder where daw looks for plugins and renames it with ".vst3" extension. After this he opened a daw and used his "dynamic processing" plugin inside this daw without rackAFX . Is it possible to do this?
Yes, export your plugin from RackAFX as ASPiK and for VST3.
Compile the plugin and make the .vst3 in the VST3 bundle folder.
Copy the VST3 plugin into Reaper's VST folder and run it as a Plugin.
The old RAFX1 version where you could make the RackAFX plugin into a VST2 and VST3 plugin is no longer supported.
One reason is that the VST3 license does not allow me to do that. You must compile your own VST3 with the VST3 SDK as supplied by Steinberg (same is true if using JUCE). The other reason is that with each new VST3 SDK release, the base code usually changed enough to require me to do a complete new RackAFX build.
By separating RackAFX and ASPiK, I can keep two sets of software under control.
You can learn more about that split in the video here:
With RackAFX and ASPiK you can make AU, VST3 and AAX plugins but they are not the meaning of "stand alone" the way Thomas and I understand it.
A true "stand alone" plugin will run without any kind of DAW. Korg makes a lot of those as stand-alone Apps. Making one is a matter of designing an app to host the plugin of choice.
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Newest Members:Mistahbrock, Jas, Rowan, sojourn, fabhenr, rg1, Niklas, Wutru, Tim Campbell, Danny Jonel
Moderators: W Pirkle: 573
Administrators: Tom: 74, JD Young: 80, Will Pirkle: 0, W Pirkle: 573, VariableCook: 3