Is it possible to bundle all samples in the plugin?

[dannytaurus]

@bendurso Thanks for the info.

I'm looking for the simplest install method for both me and my customer.

That means ideally [1] me not having to create installers for each platform and [2] delivering a single VST/AU to the customer.

I currently use Maize where I have to deliver a VST/AU plus a folder containing the presets. But since this folder goes right next to the VST/AU in the normal plugin folders it's reasonably easy for my customers. For example:

Plugins/VST3/MyPlugin.vst3
Plugins/VST3/MyPlugin.instruments

What I don't want is either my customers having to dive into system folders to place the sample monolith, or for them to have to choose the location of the sample monolith when first using the plugin.

Do you have any advice to help me achieve this?

[bendurso]

@dannytaurus

Mm I also used Maize a while ago and did that.

But things in Hise are a little different. It's a transition from Maize to Hise; and you have to learn a few things, but it's worth every penny.

The easiest option for you would be to deliver the vst3 / au file, along with the samples folder.

You can disable the Install Samples dialog, and enable the "Locate Samples" dialog. Users only need to select the samples folder and that's it.

[d.healey]

@dannytaurus said in Is it possible to bundle all samples in the plugin?:

I'm looking for the simplest install method for both me and my customer.

You could use Rhapsody.

[Orvillain]

@bendurso said in Is it possible to bundle all samples in the plugin?:

You can disable the Install Samples dialog, and enable the "Locate Samples" dialog. Users only need to select the samples folder and that's it.

Reply

How do you do this out of interest?

[bendurso]

@Orvillain said in Is it possible to bundle all samples in the plugin?:

How do you do this out of interest?

Insert this into Extra Definitions

HISE_SAMPLE_DIALOG_SHOW_INSTALL_BUTTON=0
HISE_SAMPLE_DIALOG_SHOW_LOCATE_BUTTON=1

And then you just deliver the folder with the monolith files inside.

[dannytaurus]

@d-healey said in Is it possible to bundle all samples in the plugin?:

You could use Rhapsody.

I checked out Rhapsody, it looks very nice. However it's not really suitable for my needs.

I've spent time building a brand and a business around my plugins and I don't want to introduce a third party into that.

I did think about forking Rhapsody because I do rather like the idea of only having to notarize a player once and then further products can just be expansions, but I'm not sure if it would be worth the work.

[d.healey]

@dannytaurus If you can notarize one plugin it's not much more effort to notarize 1000 plugins (but you'll have to wait a while :) ).

Basically you can use a bash script to automate everything.

[dannytaurus]

@bendurso said in Is it possible to bundle all samples in the plugin?:

Insert this into Extra Definitions

HISE_SAMPLE_DIALOG_SHOW_INSTALL_BUTTON=0
HISE_SAMPLE_DIALOG_SHOW_LOCATE_BUTTON=1

And then you just deliver the folder with the monolith files inside.

Thanks for the tip, but it still ultimately leaves it up to the user to manage the sample location.

Is there any way to hardcode the plugin to look in the current directory for the monolith?

Something like

HISE_SAMPLE_LOCATION=MyPlugin/Monolith.ch1

so it looks for the samples in a folder named MyPlugin in the same folder as MyPlugin.vst3.

[d.healey]

@dannytaurus said in Is it possible to bundle all samples in the plugin?:

so it looks for the samples in a folder named MyPlugin in the same folder as MyPlugin.vst3.

Generally you don't want to be putting samples in the user's VST3 folder. The user should be able to select the location for the samples - especially important for large libraries, less so for small libraries.

[bendurso]

@dannytaurus said in Is it possible to bundle all samples in the plugin?:

Is there any way to hardcode the plugin to look in the current directory for the monolith?

For small sample libraries (like 100mb or so), I ship the linkOSX file with the installer. So the user just run the installer and that's it. The linkOSX file is the one that contains the samples path. So, I ship both the samples and the linkOSX file with the installer.

But for bigger libraries, the only option I know is giving the user to choose the sample folder. Generally users don't like if you send a big file to a place where they don't want.