Can Anyone Help Me to Build VST3 Plugins from HISE

[A Former User]

https://www.youtube.com/watch?v=GG1tKPELS4M
Can Anyone Help Me to Build VST3 Plugins from HISE ?
Here in this detailed screen capture I have shown all the errors and difficulties I have found for building VST3 plugins. I have tried to capture all the steps, no steps are skipped.
I have used HISE ScriptNode branch. I have tried MS Visual Studio 2017 & 2019. I tried VST3 SDK both Hise recommends or JUCE recommends. Still no luck.

[Casey Kolb]

Can you compile without the VST3 Support enabled? I've had trouble compiling the VST3 as well, so I've just opted for the regular old VST format. The difference between the VST and VST3 is probably very negligible depending on how complex the plugin is.

[A Former User]

Did you install IPP? The errors indicate that HISE can't find it.

[A Former User]

@iamlamprey Yup. I have installed IPP. Otherwise HISE Standalone would have not been compiled.

[A Former User]

@Lunacy-Audio Yes. I can compile legacy VST 2 . But VST 3 is not being compiled. In the other hand I use JUCE 6 (mainly for learning) it compiles VST 3 smoothly.

[ustk]

@Tania-Mosh What VST SDK have you installed in the SDK folder?

[Lindon]

@Lunacy-Audio said in Can Anyone Help Me to Build VST3 Plugins from HISE:

Can you compile without the VST3 Support enabled? I've had trouble compiling the VST3 as well, so I've just opted for the regular old VST format. The difference between the VST and VST3 is probably very negligible depending on how complex the plugin is.

-- that and the licensing issue...

[A Former User]

@ustk I have tried "vstsdk366_27_06_2016_build_61.zip" and also "vst-sdk_3.7.1_build-50_2020-11-17.zip"..but no luck. It can only compile legacy VST 2.

[ustk]

@Tania-Mosh Use the SDK that is in the sdk.zip (password 4321)
and move the ASIO and VST3 folders in SDK, not in a subfolder

[d.healey]

Open Projucer and point the VS studio exporter to the VST3 SDK that is inside the JUCE folder that comes with HISE (I'm not at my computer now but when I am I'll post the full path).

I have a pull request waiting to be merged that should fix this issue for good.

[d.healey]

@ustk That one doesn't work for VST3 without modification (there is another thread about it).

[ustk]

@d-healey Strange, I always used it on my mac to compile VST2 and VST3 successfully

[d.healey]

Here is the path to the VST3 SDK that works /JUCE/modules/juce_audio_processors/format_types/VST3_SDK

This is the info about modifying the SDK in that zip file - https://forum.hise.audio/topic/1444/vst-export-failed/75

[A Former User]

@ustk Thank you so much.. I will try.

[A Former User]

@d-healey Ok. I am trying.

[A Former User]

@d-healey Do I need to Rebuild the HISE Standalone again, with the modified path?

[d.healey]

@Tania-Mosh Nope. Just set the path in the .jucer file for your project. In the image below it says (Legacy) SDK but it won't say that for VST3 it will just say VST SDK or something similar:

The other option is to use the version that comes with HISE, the one that ustk mentioned, and make the modifications in the link I posted above.

[A Former User]

@d-healey Uh.. little hard to understand for a startup user and specially for a non programmer like me. Ok I am trying what I have understood from your post by my little brain. .

[A Former User]

@d-healey When I'm opening my demo project with Projucer it sets the legacy folder to like this..!

[A Former User]

@d-healey Do I need some modification in Global path?