VST export failed
-
@Christoph-Hart what is the password and why is there a password? it says nothing anywhere about it
-
@mwplugs Have a look at the 2nd post ;)
-
so which sdk are we supposed to be using now. 3.6.7? the repository links to 3.6.6
-
@mwplugs Well, I never succeeded using the last from Steinberg, but the one that is coming with Hise works...
-
@ustk soooo do you use the vst sdk linked in the repository and then extract the sdk.zip because everything was fine before now im getting errors flock.cpp and the vstheader something
-
c:\users\tlw.msi\desktop\hise-2.1.0\juce\modules\juce_audio_processors\format_types\juce_vst3headers.h(119): fatal erro r C1083: Cannot open include file: 'base/source/flock.cpp': No such file or directory [C:\Users\TLW.MSI\Documents\!PLUG INS!\Sixteen\Sixteen\Binaries\Builds\VisualStudio2017\Sixteen_VST3.vcxproj]
then
c:\users\tlw.msi\desktop\hise-2.1.0\juce\modules\juce_audio_processors\format_types\juce_vst3headers.h(119): fatal erro r C1083: Cannot open include file: 'base/source/flock.cpp': No such file or directory [C:\Users\TLW.MSI\Documents\!PLUG INS!\Sixteen\Sixteen\Binaries\Builds\VisualStudio2017\Sixteen_VST3.vcxproj]
-
c:\users\tlw.msi\desktop\hise-2.1.0\juce\modules\juce_audio_processors\format_types\juce_vst3headers.h(119): fatal erro
r C1083: Cannot open include file: 'base/source/flock.cpp': No such file or directory [C:\Users\TLW.MSI\Documents!PLUG
INS!\Sixteen\Sixteen\Binaries\Builds\VisualStudio2017\Sixteen_VST3.vcxproj] -
@mwplugs Yep, just like that, and drag the VST3 SDK folder in the SDK directory, that's it...
-
@ustk I am suffering with exactly the same issue as yours now. (Redefinition of "iid".)
Using VSTSDK3613(20190804, Xcode 10.3, macOS 10.14 Mojave 2nd Supplemental Update. macOS SDK is the one shipped with Xcode 10.3 update.
HISE Source Code git commit number is 8ef678e with only the replacement of the Projucer app itself (5.4.4).The whole industry's attitude towards VST3, while being unchanged since the recent 10 years, is becoming more and more problematic, regardless that similar attitudes of Hart (for example only) and Native Instruments (who refuses to give VST3 a fk constantly even if developing Kontakt 6) is not blamable due to the nature of humanity.
VST2 plugins are nightmares to Steinberg Dorico, which is my main app for music composition and arrangement. Native VST3 plugins runs fine with Dorico 3, but whitelisted VST2 plugins (including some VST2 plugins renamed as VST3) and certain universal-SDK VST23 plugins (like plugins generated by Maize Sampler) can let Dorico crashes like a hell after once successful load. Everytime you start your system and run Dorico, load a plugin like that, it runs fine until you want to turn off Dorico, and you will see Dorico hangs. Then you will find that Dorico is not runnable until you restart your system.
Please, please support VST3 by default. Otherwise I guess it really is the time to let the Cubase / Nuendo / WaveLab product line give up their support of VST2.
-
I put the folder pluginterfaces at the root of the Hise program,vst export works.Linux os.
Download pluginterfaces -
@ShikiSuen I don't understand. Hise supports VST3. I just had troubles with the last version from Steinberg, but the sdk that is coming with Hise works...
-
@ustk Doesn't work on my side. I dunno why.
Now I am gonna perform the plugininterfaces trick.As I see, blaming someone won't work. I just feel really pissed of wasting 12hrs the whole day but still cannot get my virtual instruments compiled in VST3. Really pissed off.
-
@ustk If using the 2016 sdk shipped from the HISE repository (the "repo SDK"), it says the lack of flock.cpp and its h file. I copied them from the latest SDK to the repo sdk, found more numerous build errors.
If I use the latest official SDK, then the issue of [Redefinition of "iid"].
-
@ShikiSuen I'm sorry you're pissed off. Unfortunately my knowledge about this is very limited. I can just tell you what I've done, like extracting the
HISE/tools/SDK/sdk.zip
, drag both folders one level above, and tickVST3 support
in the prefs of HISE.
Aside from that, I can't help much I'm afraid. Calm down, I'm sure you'll find a solution... -
I did everything you said (except that VST3 support is checked through Projucer preferences of the HISE standalone project), it doesn't work.
I don't think it is because of you personally. Instead, if VST3 is being respected enough by this world, things shouldn't be terrible like this.
What's the exact git commit number of the HISE source code you are using? What VST3 SDK version are you using for your successful compilation of VST3-supported HISE (still 3.6.6)? What's the version of Projucer you are using? What's your macOS system build number? What's the Xcode version you are using? Which macOS SDK?
-
HISE itself build succeeded.
Using VSTSDK3613(20190804, Xcode 10.3, macOS 10.14 Mojave 2nd Supplemental Update. macOS SDK is the one shipped with Xcode 10.3 update.
HISE Source Code git commit number is 8ef678e with only the replacement of the Projucer app itself (5.4.4).Solution: If seeing lines triggering the "Redefinition of iid" issue, simply comment out those lines.
The new problem is that I don't know the further steps within the HISE environment to build VST3.
-
@ShikiSuen said in VST export failed:
I don't think it is because of you personally.
I hope so. I'm not Hise dev...
-
Can anyone help with this flock.cpp issue?
c:\program files\hise-scriptnode\juce\modules\juce_audio_processors\format_types\juce_vst3headers.h(119): fatal error C 1083: Cannot open include file: 'base/source/flock.cpp': No such file or directory
I've gotten this in the past when trying to export VST3 format (currently on PC), but decided to ignore it until it was needed.
I'm using the sdk from scriptnode. -
@dustbro Double check that you actually have the file in there. If you do, try to specify the absolute location. If that doesn't work, just comment out that part of the code in the juce_vst3headers.h and see what happens.
I had to comment out about 3 various lines of code that we giving errors and was able to compile after that. Give it shot and let us know how you go. -
@dustbro try this:
https://forum.hise.audio/topic/1856/compile-error/5