VST export failed

ustk

Maybe a flag in the Projucer?

alt text

ulrik

@ustk Yes I'm a mac user

orange

Also when I use new Hise version, I always clear caches of Projucer and Hise. Because sometimes old data can remain in the cache, so new Hise version couldn't work or compiled properly.

I suggest that:

Open "Application Support" folder and delete Projucer and Hise folders.
Then download the latest Hise from GitHub and recompile Hise with this SDK. Also be sure that the the renamed "VST3 SDK" folder should contain all of the sdk data under itself and this folder shouldn't have any additional sub folders. For example: the folder shouldn't be like that: "VST3 SDK > VST3_SDK > required sdk files and folders" It should be like this: "VST3 SDK > required sdk files and folders"
Then try to compile your vst3 plugin in the new compiled Hise version.

ustk

Thanks man that's a good idea!
Will try it tomorrow and give feedback ;)

orange

@ustk Also you can change your Hise folder name even. Let's say if your Hise folder is "Hise-master"
Try to change it with "Hise-master_" ;) This will break the old cache ;)

ulrik

@orange said in VST export failed:

@ustk @ulrik

Also when I use new Hise version, I always clear caches of Projucer and Hise. Because sometimes old data can remain in the cache, so new Hise version couldn't work or compiled properly.

I suggest that:

Open "Application Support" folder and delete Projucer and Hise folders.

Then download the latest Hise from GitHub and recompile Hise with this SDK. Also be sure that the the renamed "VST3 SDK" folder should contain all of the sdk data under itself and this folder shouldn't have any additional sub folders. For example: the folder shouldn't be like that: "VST3 SDK > VST3_SDK > required sdk files and folders" It should be like this: "VST3 SDK > required sdk files and folders"

Then try to compile your vst3 plugin in the new compiled Hise version.

Thank you, I will try it after some sleep :)
Regards!

ulrik

@orange ,@ustk, after deleting Producer and Hise folders in "Application Support" and getting latest scriptnode code and latest VST 3 SDK, I tried to compile for VST3 plugin and failed again, this is the terminal message:

/Users/ulrikboden/Music/Hise/HISE-scriptnode/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3_Wrapper.cpp:55:10: 'pluginterfaces/vst2.x/vstfxstore.h' file not found

#include "pluginterfaces/vst2.x/vstfxstore.h"



** BUILD FAILED **


The following build commands failed:
  CompileC build/Guerrini\ Accordion.build/Release/Guerrini\ Accordion\ -\ VST3.build/Objects-normal/x86_64/include_juce_audio_plugin_client_VST3.o /Users/ulrikboden/Music/Hise/Guerrini\ Accordion/Binaries/JuceLibraryCode/include_juce_audio_plugin_client_VST3.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

So I checked inside "pluginterfaces" folder and it didn't include the "vst2.x" folder, so I copied it there and compiled again and, eureka! It worked!
:)

gorangrooves

While I was able to successfully compile my plugin on PC every time, on Mac, I am getting the following error:

No member named 'MidiFiles' in 'hise::FileHandlerBase'

Not sure where this is coming from since I am not using any midi files within my project.

The line in question is this inside plugin.cpp file:

DEFINE_EMBEDDED_DATA(hise::FileHandlerBase::MidiFiles, PresetData::midiFiles, PresetData::midiFilesSize);

@Christoph-Hart Can you tell what is going on here?

ustk

@Christoph-Hart Still not able to compile VST3 from the last commit (commit - b4b5ab1 - 1h ago)

▸ Compiling include_juce_audio_plugin_client_VST3.cpp

❌  /Users/greg/Desktop/HISE-scriptnode 02-08/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3_Wrapper.cpp:55:10: 'pluginterfaces/vst2.x/vstfxstore.h' file not found

#include "pluginterfaces/vst2.x/vstfxstore.h"
  ~~~~~~  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


** BUILD FAILED **


The following build commands failed:
	CompileC build/ForceIT.build/Release/ForceIT\ -\ VST3.build/Objects-normal/x86_64/include_juce_audio_plugin_client_VST3.o /Users/greg/Documents/_PROGRAMMING/ForceIT/Binaries/JuceLibraryCode/include_juce_audio_plugin_client_VST3.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
Compiling finished. Cleaning up...
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

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

VST export failed

21

1.7k

11.8k

102.5k