Exporting plugin with expansions?
-
Hi everyone,
I’m preparing to export my instrument and I want to make sure I’m structuring everything correctly before release. I’ve read the documentation and some forum threads, but I’m still unsure about the correct workflow in this situation.
Here is my current project setup:
- Main Project
All samples are stored in the MAIN project (Samples folder)
I also have AudioFiles such as:
-
Wavetables
-
Monolith files
-
One Reverb IR file in WAV format
-
Expansions
I have two expansions
Inside each expansion I only have:
-
SampleMaps
-
Presets / metadata
The actual samples used by those samplemaps are in the MAIN Samples folder
When I compile the plugin:
The expansions and presets appear correctly
But no samples load inside the presets
So I’m trying to understand the correct workflow for exporting and packaging the project.
My questions:
Is it valid to keep all samples in the MAIN project, while the expansions contain only SampleMaps and presets?
If yes, what is the correct way to export samples and expansions so that the compiled plugin can properly locate the samples?
Should the expansions also contain their own Samples folder, or is referencing the main Samples directory acceptable?
What is the recommended export workflow in this situation?
Compile plugin
Export Samples for Installer
Expansion packaging
Are AudioFiles like wavetables and a convolution IR (.wav) safe to keep in the main project without converting them to monolith?
Any advice on the proper folder structure and export workflow would be greatly appreciated.
Thanks!
-
@filipalex96 said in Exporting plugin with expansions?:
The actual samples used by those samplemaps are in the MAIN Samples folder
The expansion's samples should be in the expansion's folder.
-
@David-Healey Thank you for the reply, I really appreciate the help.
Sorry if this is a stupid question, but I want to make sure I understand correctly.
When you say “The expansion's samples should be in the expansion's folder”, do you mean that each expansion must contain its own Samples folder with the actual audio samples inside it, like this?
Example structure:
Expansion1
Samples
SampleMaps
Presets
Expansion2
Samples
SampleMaps
Presets
Right now in my project all the samples are stored in the MAIN project Samples folder, and inside the expansions I only have SampleMaps and presets that reference those samples.
-
@filipalex96 said in Exporting plugin with expansions?:
do you mean that each expansion must contain its own Samples folder with the actual audio samples inside i
Yes.
I made a video a while back about expansions that you might find useful:
I also posted a video on Patreon a couple of weeks ago about building an expansion installer.
-
@David-Healey I watched the tutorial and followed the steps shown there, but I think I must be doing something wrong somewhere.
Do I need to export the expansions in a specific way, or is there an extra step required before compiling the plugin?
Also, in Expansion Type I selected Full Expansions. Maybe this is where I made a mistake?
Sorry if this is a basic question, I’m just trying to understand the correct workflow and I might be misunderstanding something.
Thanks for the help!
-
@filipalex96 The docs cover most of what you're asking: https://docs.hise.audio/working-with-hise/project-management/expansions/index.html
You probably don't want Full Expansions, you probably want Encrypted.
-
@David-Healey Thanks, I’ll take a closer look tomorrow and get back with an update.
