Unable to get VST3 created instruments to work in FLStudio 20 or Reason 10
Scanning for plug-ins If you have installed a Windows-compatible Antares plugin, and it is not showing up in Ableton Live 10, please follow these instructi. Tue, Oct 13, 2020 at 5:48 PM Sonar Platinum. In FL Studio: - Options -Manage Plugins, and add a Search Path in top-left to your VST folder location (e.g. C: VSTPlugins) containing Serum.dll / Serumx64.dll (Windows) Ableton Live 10: - Preferences - Plugins, enable 'VST2 Custom Folder' and set the VST2 Custom Folder location to the folder containing Serumx64.dll.
#780 Hi I'm Philip and new to this forum, Having recently purchased a S.E. license I decided to go ahead and create my first basic synth. All went well until I tried exporting it as a VST3 file. The process worked fine however when I try to open it in FL Studio 20, although it sees the plugin it reports an 'Error' but there is no information as to the nature of it. Fortunately I still have the previous version FL studio 12 installed on my PC and it works fine in that. I also tried it with Reason 10 and Ableton Live 10, and although I set the path location it does not detect it in these DAWs either. It does work however with the current version of Cubase 9.5 and I can also use it with the standalone app Savihost but not in vPlayer 2. I purchased a commercial synth Go2 by Rob Papen and that works in all of the above however I notice that this is a .dll VST file whereas the VST file created with SynthEdit has multiple files. I read another thread here that mentions Windows 10 doesn't like hidden files within the .dll file however it seems the commercial software houses are still creating these. I'm not sure if I'm just barking up the wrong tree here but could this be the reason why the VST3 file I created only works in some DAWs and some standalone apps? Not being a coder I'm not sure where to go from here. My goal is to create some basic synths for a training course I'm putting together. Any help is greatly appreciated. Regards Philip |
#784 Not all DAWs support the VST3 format, I know that Reason and Ableton Live only support the VST2 format currently. SE can output both of those formats, you just need to select which one when you go to export your plugin. VST2 uses the file the extension .dll, and VST3 uses .vst3. Hope that helps, and happy building! Cheers, On Sunday, August 26, 2018, 4:44:17 PM CDT, p.kebbell@... <p.kebbell@...> wrote: Hi I'm Philip and new to this forum, Having recently purchased a S.E. license I decided to go ahead and create my first basic synth. All went well until I tried exporting it as a VST3 file. The process worked fine however when I try to open it in FL Studio 20, although it sees the plugin it reports an 'Error' but there is no information as to the nature of it. Fortunately I still have the previous version FL studio 12 installed on my PC and it works fine in that. I also tried it with Reason 10 and Ableton Live 10, and although I set the path location it does not detect it in these DAWs either. It does work however with the current version of Cubase 9.5 and I can also use it with the standalone app Savihost but not in vPlayer 2. I purchased a commercial synth Go2 by Rob Papen and that works in all of the above however I notice that this is a .dll VST file whereas the VST file created with SynthEdit has multiple files. I read another thread here that mentions Windows 10 doesn't like hidden files within the .dll file however it seems the commercial software houses are still creating these. I'm not sure if I'm just barking up the wrong tree here but could this be the reason why the VST3 file I created only works in some DAWs and some standalone apps? Not being a coder I'm not sure where to go from here. My goal is to create some basic synths for a training course I'm putting together. Any help is greatly appreciated. Regards Philip |
#788 Thanks for your reply Lee, That's made it clearer for me. It's strange how FL Studio 20 seems to have dropped .vst3 support whereas it was available in 12. I wonder if some of the DAW manufacturers are experiencing problems with it. |
#795 Hi, The VST2 are VST3 in fact, this is why I provide only the VST3, just when you change the .vst3 to .dll extension you must place the plugin and its folder out of the VST3 plugins folder if else FL or some DAWs cannot see the plugin. About x64 VST: VST2 recommended for VSTHost: Load and Save XML presets menu does not work fine on Win 10 following the configuration used (to do list). The GUI editor of VSTHost 1.56 stays incompatible when the plug-ins are used in VST3 not in VST2. VST3 GUI works fine only with VSTHost 1.54. Fruity Loop: Select 'Use fixed size buffers' in the plug-in options to win 25% of CPU use! Reaper: Load and Save XML presets menu does not work fine on Win 10 following the configuration used (to do list). If you listen audio 'pops' when you edit something on Reaper with Asio4All. To fix it > FX windows > Compatibility settings > 'Save minimal undo steps'. To do list: Load and Save XML presets menu does not work fine on Win 10 following the configuration and the DAW used. Installation example: 1- Unzip and copy the VST3 folder in 'C:ProgramsCommon filesVST3'. 2- To operate the 64 bit (x64) KX77FREE plug-ins require MicroSoft files called 'Visual C ++ Redistributable Package'. These need to be installed only once on each PC that uses these plug-ins, get the 2015 version or the 2017 compatible version (check your already installed packages): https://www.microsoft.com/en-US/download/details.aspx?id=53587 3- In 'Users'your account'DocumentsVST3 Presetsxavier kalensky'KX MODULAD', you copy all *.vstpreset files provided with the VST3. 4- If your DAW does not support VST3, change the extension of the plugin *.vst3 by *.dll (VST2) and copy the VST2 folder in 'C:ProgramsCommon filesVST2' or in your usual x64 VST2 folder... 5- Update the database of your DAW by scanning the plug-ins. Note: 'Common Files' is a protected Windows system folder. Your DAW must be in Administrator mode to save your XML presets inside. If else you must save in your Document folder of your account or in out of protected Windows folders. |
Dll Vst Plugins Not Working In Live 10 Day
Plug-in Not Showing Up In DAW
Compatibility: Our virtual instruments are compatible with all VST and AU plugin host applications on 32-bit and 64-bit versions of Windows and macOS. Keep in mind that macOS Catalina is NOT supported at the moment. Installation: On Windows, extract the downloaded archive to your VST plugins folder (the one which is scanned by your DAW).
Please be sure that you're using a compatible DAW, and that you've installed the correct plugin format for your DAW. The latest versions of all A...
Some users have experienced Auto-Tune® Pro not showing up in their DAW after installing Auto-Tune Unlimited. In order to avoid this, make sure to unins...
Installation and Compatibility If your Antares plug-in is not showing up in Logic Pro X, please be sure that you have installed the 64-bit AU version of th...
Free Dll Vst Plugins Instruments
Installation and Compatibility: If your Antares plug-in is not showing up in GarageBand 10, please be sure that you have installed the 64-bit AU version of...
Installation and Compatibility If your Antares plug-in is not showing up in Ableton Live 10 (64-bit), please be sure that you have installed the 64-bit AU ...
Scanning for plug-ins If you have installed a Windows-compatible Antares plugin, and it is not showing up in Ableton Live 10, please follow these instructi...
Installation and Compatibility We are aware of some issues with the VST3 versions of Auto-Tune® EFX 3 and the AVOX 4 plugins in Sonar. We will be addressi...
Installation and Compatibility ***Important Note***: Our plugins (and all other 3rd-party plugins) are only readily compatible with 'Professional&quo...
Dll Vst Files
Installation and Compatibility ***Important Note***: Our plugins (and all other 3rd-party plugins) are only readily compatible with 'Professional&...