VST export failed

[ustk]

Back on this problem...
It is probably trivial, but the idiot I am can't figure out how to export VST3
Can someone please assist me on how to do it properly on mac?

Here's where I am:

• I enabled VST3 support in the project pref
• when I export my VSTi, I just have the "VST SDK is missing" message
• I'm using the last scriptnode

@gorangrooves said in VST export failed:

Guys, the issue with SDK files missing can be sorted by editing the file which is referencing to them, then editing the relative path to the absolute path on your computer. When your VS2017 compiling fails, it gives you a list of files with errors. Open the file and find the lines of code in question. They will contain the relative path. That's what I did when compiling of HISE failed with the latest branch.

I don't understand what file I have to edit...
It might be because I am exporting directly into Hise, not via Xcode, you see, I'm lost...

[Lindon]

@ustk did you look in:

/tools/SDK/

and find

VST3 SDK

?

[ustk]

I don't have anything but what comes with Hise
Since I don't need VST2 anymore I didn't put anything in there
Also, I thought that everything now comes directly with Hise, isn't it?

[d.healey]

@ustk Yep, I'm pretty sure you're right about that.

[ustk]

...strange
Might be a flag in the Projucer, or when compiling Hise?

[d.healey]

@ustk Did you try searching for the file with the relative path as @gorangrooves suggested?

[ustk]

@d-healey that's what I don't understand...
What file? Where?

[d.healey]

@ustk The file should be mentioned in the error message.

[ustk]

That is what I thought at first but here's what I got:

[d.healey]

@ustk Oh, yeah add the VST2 sdk to the SDK folder as Lindon suggested and that should go away. Seems like it's a bug because when you enable VST3 export I would have thought this message would be suppressed.

[ustk]

Ok so I found a way to at least not to have this error message, but it didn't work with VST2 SDK but by decompressing the sdk.zip, which have a VST3 SDK folder...

But when compiling, here's what I get:

And when going into the juce_VST3Headers.h file, it is apparently a version issue, because I don't have base/source/flock.cppfile anywhere:

[d.healey]

@ustk Actually the VST3 SDK folder is the VST2.4 SDK ;)

I'm not sure about the flock.cpp thing

[ustk]

@d-healey said in VST export failed:

@ustk Actually the VST3 SDK folder is the VST2.4 SDK ;)

Yep you're right, but since there is also a VST2 folder that exists I want to make it clearer...

@Christoph-Hart any thought about this VST3 problem that persists?

[ustk]

Also, do we need to recompile Hise every time we change something in the SDK folder?

[d.healey]

@ustk No

[ulrik]

@ustk That is exactly what I get as well when trying to compile for VST3, if disabling VST3 it compiles fine.

[ustk]

Bump Bump

[orange]

@ustk @ulrik
Actually Since Hise uses VST3 SDK, I am using that and I can compile both vst2 & vst3 plugins without any issues with this sdk. This is my folder structure - download the sdk and rename it like that;

VST 3 SDK Version 3.6.6

[Dan Korneff]

I have not been able to successfully compile vst3 either

[orange]

@dustbro Are you getting a warning while compiling? Or the host doesn't detect vst3?
It works on both mac and pc. Vst3 works.

Sometimes if you have multiple vst versions for one plugin (like vst2 & vst3), some hosts are very picky. Especially Studio One. It sees only vst2, not vst3 for me. But I didn't see a problem in Ableton, Reaper and Cubase about detecting vst3 plugins.