@David-Healey said in Exporting plugin with expansions?:
@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.
Well..... not the way I do it....you can put the samples in the Linkfile directory - where all your factory samples are, so in your sample map it just looks sorta normal e.g.
FileName="{PROJECT_FOLDER}fatty_F#4.wav"
Essentially the sample map tells HISE where the sample data is by using this {PROJECT_FOLDER} token, which means "the folder wherever the end user decided to keep the samples, who's location can be found in the Link file"
You just need to tell your sampler where the sample maps are.... it already knows about your factory sample maps - they are shipped in the plugin, so you just need to tell it where each expansions maps are...
So you will need some meta data to differentiate your "factory" maps from each of your expansion maps, so my factory meta data for this location looks like this:
{
"VoiceMapName": "FireBreak"
}
note theres no actual location data in here, HISE, and your product already know about this map so none is needed.
whilst my expansion meta data looks like this, for an expansion called AlarmSemaphores:
{
"VoiceMapName": "{EXP::AlarmSemaphores}AS_Absentees"
}
OK so another of these token things.. this time {EXP::expansion folder name}, which tells HISE, and your product to go look in the expansions folder for a sub folder called AlarmSemaphores, and there to look in the SampleMaps folder
So at this point you only need to set the expansion type to FilesOnly and have a way to place each expansions folder structure, which is entirely empty except for the sampleMaps folder which holds all the sample maps for your expansion.
So your Expansion installer will need to:
copy the sample data (.ch1 files) to the Linkfolder
Create a folder structure in the products Expansion folder
Here's an example:
c05bee1c-3a62-45af-be64-e770c392ae99-image.png
Inside each expansion folder create the std expansion folder structure:
6cf9a22c-a4ba-4744-bfdd-634d0a309ec4-image.png
inside the SampleMaps folder add the sample maps:
34e59a36-b8f8-4049-940d-1a2c2f3e392f-image.png
Create some meta data file that describes these maps and where they are so your product can find them...
If all of this is "too hard" then once the Asset Manager is up and running I will add a (for fee) version of this system so getting up and running should be pretty painless...I've been using it on HoriZEN, and now Atmosia 3 for over a year and it seems to work fine.
