Can someone please give me a rundown on how to export a plugin properly? Along with the plugin's samples and images as directories?
-
I'm about to export a project but when It found out that I was using an absolute directory,it aborted. So I want to know how to put everything in a zip so it's accessible to the plugin when the user has it on their own computer. Should I place folders of the same name containing the assets of my plugin into the HISE-master folder or is there another more efficient way?
-
First covert your sample maps to monoliths, then go to the export menu and export as a VST. The output (assuming all goes well) will be a .DLL file - on windows. You give this to the user along with the monolith samples which will have a .CH extension. That's the simplest method.
-
Also you shouldn't be using HISE-master, it's ancient, build scriptnode instead - latest commit is buggy though so might want to wait until Christoph's next commit
-
@d-healey said in Can someone please give me a rundown on how to export a plugin properly? Along with the plugin's samples and images as directories?:
First covert your sample maps to monoliths, then go to the export menu and export as a VST. The output (assuming all goes well) will be a .DLL file - on windows. You give this to the user along with the monolith samples which will have a .CH extension. That's the simplest method.
Can you explain this in more detail?
And how do I build scriptnode? I'm dumb at this. -
@d-healey I tried exporting it after I made the samples monoliths but now it says there's no image directory. I'm using the Images folder in my project folder though. Am I supposed to copy and paste it somewhere?
-
You need to build HISE from source. I have a few tutorials on YouTube about this, they're a little out of date now but should give you the gist.
This is the commit you should build - https://github.com/christophhart/HISE/tree/56681b27b02960d9a20eb40ffe89a49451e23404
Tomorrow it may be a different commit that I recommend :p
-
@d-healey Aight thx!
