VST export failed

Christoph Hart

What if you extract the SDK from the .zip file in the repo?

gorangrooves

@ustk Can you verify if the file is actually there on your computer or truly missing?

gorangrooves

@Christoph-Hart To compile my plugin, I had to comment out the problematic line within the file.
I also had to comment out 4 lines in order to compile HISE, as there was some sort "duplicate" with regards to SDK downloaded and what is included with JUCE.

ustk

@Christoph-Hart said in VST export failed:

What if you extract the SDK from the .zip file in the repo?

Well, it works!
I don't understand though since the .zip doesn't contain VST3 SDK innit?

@gorangrooves said in VST export failed:

@ustk Can you verify if the file is actually there on your computer or truly missing?

The file in question is not present in the VST3 SDK I just downloaded from Steinberg, but it is in the zip from the repo

Christoph Hart

@ustk said in VST export failed:

The file in question is not present in the VST3 SDK I just downloaded from Steinberg, but it is in the zip from the repo

Yes that is because Steinberg removed the VST2 SDK from their distributed VST3 SDK, but if you know the secret password, you'll get the ol' but good one :)

ustk

@Christoph-Hart Well, I did not understand that:

this one is the good one
and that we needed the VST2 files for compiling the VST3

Though there's one thing I understand, it's that I don't understand much...

mwplugs

@Christoph-Hart what is the password and why is there a password? it says nothing anywhere about it

ustk

@mwplugs Have a look at the 2nd post ;)

mwplugs

so which sdk are we supposed to be using now. 3.6.7? the repository links to 3.6.6

ustk

@mwplugs Well, I never succeeded using the last from Steinberg, but the one that is coming with Hise works...

mwplugs

@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

mwplugs

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]

mwplugs

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]

ustk

@mwplugs Yep, just like that, and drag the VST3 SDK folder in the SDK directory, that's it...

ShikiSuen

@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.

EDELWEYS

I put the folder pluginterfaces at the root of the Hise program,vst export works.Linux os.
Download pluginterfaces

ustk

@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...

ShikiSuen

@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.

ShikiSuen

@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"].

ustk

@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 tick VST3 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...

VST export failed

25

1.8k

10.4k

90.7k