Export Error - JUCE VST3 Wrapper
-
@trillbilly said in Export Error - JUCE VST3 Wrapper:
Does HISE need any other files deleted to completely remove previous versions?
No.
Stick with 64bit only.
Are you using the latest commit (today) of new_layout? -
@d-healey Yes, just downloaded and compiled about 30mins ago. I downloaded and did an "overwrite" of the previous new_layout file I had. IDK if overwriting instead of saving a new file has anything to do with it.
Also, I used the project file of another instrument to generate the "shell" of this one. Could that potentially cause issues in anyway?
-
@trillbilly It sounds like there could be issues in a few places.
Delete every copy of the HISE source you have completely.
Download the new_layout branch.
Rebuild HISE.
Open HISE
Create a new project
Then create a new file in that project. File >> New
Add one knob to the UI
Save the file
Export as VST3
Tell me what happens -
@d-healey I removed all HISE Sources and Files, recompiled HISE & saved OneKnob Project. I then exported as "VSTi 64bit" but have the same result.
include_juce_audio_plugin_client_VST3.cpp g:\02 hise\hise-new_layout\hise-new_layout\juce\modules\juce_audio_plugin_client\vst3\juce_vst3_wrapper.cpp(66): fatal error C1083: Cannot open include file: 'pluginterfaces/vst2.x/vstfxstore.h': No such file or directory [C:\Users\newna\ Desktop\New Hise\Binaries\Builds\VisualStudio2017\New Hise_VST3.vcxproj]
-
@trillbilly said in Export Error - JUCE VST3 Wrapper:
C:\Users\newna\ Desktop\New Hise
Is this the path to your new project?
Did you set the HISE path and Visual Studio version in the project preferences?
-
@d-healey Correct, that is the New Project Path.
Visual Studio 2017 selected.
Hise Path is selected.
I compile without IPP so I have also de-selected "Use IPP" option.
-
@trillbilly I don't understand why it's looking for vst2.x stuff if you have the VST3 flag checked. Did you install the VST2 SDK in the tools/SDK folder?
-
@d-healey Yes, both VST2 and VST3 SDKs are saved in tools/SDK
VST2 SDK File Name: ASIOSDK2.3
VST3 SDK File Name: VST3 SDKAre these file names correct?
EDIT: I should mention that I also re-downloaded the SDKs today when I downloaded HISE new_layout. The file names were different at download, but I changed them to what they were for previous HISE version.
-
-
@trillbilly said in Export Error - JUCE VST3 Wrapper:
VST2 SDK File Name: ASIOSDK2.3
VST3 SDK File Name: VST3 SDKASIO SDK is the ASIO SDK ;)
VST3 SDK that comes with HISE (in the sdk.zip folder) is the VST2 SDK even though the folder name is VST3. Delete the VST3 folder you have there, you don't need it. There is another one in the JUCE folder that is used automatically when exporting VST3 plugins.
-
@d-healey Am I missing something? Trying to extract the sdk.zip in order to use the SDKs that came with HISE. It is telling me the files are password protected.
-
@trillbilly No you don't need to use it. That's for VST2. Just delete the VST3 folder and try to export again.
-
@d-healey OK.
Right Now my tools/sdk folder looks like this.
ASIOSDK2.3
VST3 SDK
sdk.zipI deleted the VST3 SDK folder, leaving my tools/sdk folder looking like:
ASIOSDK2.3
sdk.zipWhen I try to export like this, it says "VST SDK File Is Missing"
-
When I try to export like this, it says "VST SDK File Is Missing"
So a different error to the previous one?
-
@trillbilly Go to the VST3 SDK folder, do you see this structure? You should see "pluginterfaces" folder and it's folder structure like this:
-
Go to the VST3 SDK folder, do you see this structure
No, that's for VST2, he's exporting VST3 which doesn't use that folder. It uses the SDK that comes with JUCE that's inJUCE/modules/juce_audio_processors/format_types
You do not need the VST3 SDK in the tools/sdk folder. -
@d-healey Are you sure?
If you see the error it says this:
error C1083: Cannot open include file: 'pluginterfaces/vst2.x/vstfxstore.h': No such file or directory
So it means the pluginterfaces folder in JUCE SDK?
-
@orange Ignore me. Apparently that folder needs to be there before HISE will let you export. But it isn't used when exporting VST3 as far as I know. @Christoph-Hart ??
-
This post is deleted! -