Someone to Compile on Windows For Me
-
@d-healey ok got Hise up and running on my windows PC...loaded up the project file...everything is working fine in HISE...when I export however it exports as a .VST3 instead of a .DLL ....how can I make it export as a .dll?
-
@johnmike You need to add the VST2 SDK but if you haven't signed an VST2 agreement in the past you're not allowed to distribute VST2 plugins.
Why do you want a VST2?
-
@Christoph-Hart I can't get the VST3 to read in Studio One for some reason...but the .dll files I have work fine
-
trying to figure out what im doing wrong over here lol...
-
@johnmike VST3s have the .vst3 extension.
-
@d-healey Right...I know that...I guess this is where the "debugging" and all that comes in...cause for some reason my VST3 exports aren't reading in the DAW...Ill keep tinkering around
-
@johnmike Try multiple DAWs (especially Reaper).
-
@d-healey Reaper got me closer! it actually opened up! gotta figure out why it isn't opening in Studio One Specifically...Thanks a lot!
-
@johnmike This tool might help as well - https://github.com/Tracktion/pluginval/releases
-
@d-healey interesting...is this a plugin testing tool of some sorts?
-
@johnmike Yes
-
I will be happy to Compile Windows Plugins VST3 and .dll. If you @johnmike need let me know.
-
Googling Studio ONE + VST3 yields this:
https://answers.presonus.com/41480/studio-one-load-vst3-from-different-folder-than-the-default
Try putting the vst3 in the default folder.
-
@Christoph-Hart Exactly... I use Studio One & Live 11 for my Trance music production. I have no issue with .VST3 for Studio One
-
@Christoph-Hart tried that....still not working for some reason...working fine in Reaper and Ableton tho...I Put it in the same folder as the HISE VST...HISE Loads fine...wont read mine...gonna keep tinkering around...Im sure it's something simple im missing...it always is...
-
@johnmike Make a new project, add a sinewave generator and an on screen keyboard. Export it as a VST3 and try and load it into various DAWs. If it works then the problem is with your plugin, if it doesn't work then the problem is in some other part of your workflow.
-
@johnmike Where are you placing your VST3 plugin?
-
@d-healey will try this in a few...Great idea...didnt think about that...
-
@gorangrooves Ive placed it in a few places...all default VST folder paths that the DAWS suggest plus even custom paths that I added myself..
-
@johnmike They should go in the standard Steinberg locations - https://helpcenter.steinberg.de/hc/en-us/articles/115000177084-VST-plug-in-locations-on-Windows
