VST export failed
-
@Christoph-Hart said in VST export failed:
you don't need to care about the VST SDK anymore
Do you mean we don't need to put them in the SDK folder anymore, and recompile Hise?
Because I am not able to export VST3 either...
The only thing I get now is the "VST SDK is missing" warning -
@Christoph-Hart Any clue on this? Is the VST3 implemented or on track to be implemented maybe? I am not interested in exporting VST2, so I'm just waiting for VST3, but I don't understand if it's ready at the moment or not...
-
Theres a box you need to tick in the settings to enable VST3 export.
-
@Christoph-Hart I wondered that, but I didn't find... sorry but I have to ask for more precision
-
Enter VST3 in the search bar of the settings window :)
-
"When the sage points at the moon, the fool looks at the finger"
-
@Christoph-Hart Ok, now I'm a burden...
I tried to redownload/recompile a proper version of Hise (the last master)
I did it without, then with the VST SDK
I ticked the VST3 support in preferencesNothing works: "VST SDK is missing"
-
Does VST3 export work for anybody?
-
@ustk I have not tried it yet
-
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.
-
@gorangrooves Thanks, but my build actually works using xcode, it's when I export the my Hise project in VST that I have the missing SDK
-
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... -
-
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?
-
@ustk Yep, I'm pretty sure you're right about that.
-
...strange
Might be a flag in the Projucer, or when compiling Hise? -
@ustk Did you try searching for the file with the relative path as @gorangrooves suggested?
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey that's what I don't understand...
What file? Where? -
@ustk The file should be mentioned in the error message.
-
That is what I thought at first but here's what I got:
