All controls are common to all plugins (FL native & VST), while the plugin options ( 7) only appear on Wrappers hosting VST format plugins. The Wrapper is a software interface/layer between instrument / effect plugins and FL Studio. Some insight: When trying to load the plugin, FL Studio comes back saying: 'The Fruity Wrapper plugin has caused a critical error while loading its state.' Presumptively, FL Studio flagged the plugin with an 'ok' status, it knows the plugin is a VST3 plugin and 64 bits. I am afraid FL studio might have black-listed it? What other explanation could there be if the plugin works on Reaper but not on FL Studio? (Both on Windows) On both cases it does not load on the mixer. FL Studio is able to recognized the plugin on both VST3 and VST2 format (.dll). I went ahead and tested it in my DAW of preference, FL Studio and I am having issues there. I tested it with a extremely simple volume plugin in Reaper.
vst3 filed after compiling the solution file.
In other words: RackAFX prototyping, ASPiK export (for VST only), CMake on the exported files, and generated a. I recently picked up the FX book and wanted to do a quick mock run of all the plugin development cycle.
