Dealing with sample installation.

[Moidb]

Hello, I would like to know what are the best practices to deal with the installation of sampler libraries.

1. Is there a way to make the instrument locate and install the library automatically when opened in the DAW or Standalone version?

2. if I install the library on my system and I share the folder where the library was installed along with the VST3//AAX files etc. it is possible to make the instrument always read that pre-installed folder, to avoid that a new client has to assign the samples folder again

3. If option 1 and 2 are not possible, what is the best recommendation for these cases?

thanks for any help!

[d.healey]

1. No.

2. I don't understand the question.

3. Simplest solution is to use the HR1. Export >> Export samples for installer. Most flexible solution, use zip files.

[Moidb]

@d-healey My intention would be to create an installer that I would do with a different application, when the user installs the instrument. the files are deposited in their corresponding folder.

It would be great if we could somehow establish a folder with the samples already pre-installed which when we open the Standalone or Daw application, the manual installation of the library (samples) is not necessary, because there is already a pre-assigned location from the script.

anyway. this works for now.

Simplest solution is to use the HR1. Export >> Export samples for installer. Most flexible solution, use zip files.

[d.healey]

@Moidb I think you'll hit problems trying to create an automated system. You can script your own installer that extracts zip files. This offers more flexibility than the hr system, especially for issuing updates.

[Matt_SF]

@Moidb
On PC, creating what you want it pretty straightforward with InnoSetup : ask the user where he wants to put the samples and then create the link-file your plugin need to find them.
On Mac, it's a bit more tricky because you can't prompt the user to define a custom folder. You'll have to define it yourself but it's possible to create the kind of installer you want.
Search the forum for installer scripts and processes, there're a few threads which discuss the matter.

[Moidb]

@Matt_SF sounds hopeful thanks for the info!

[DanH]

@d-healey said in Dealing with sample installation.:

@Moidb I think you'll hit problems trying to create an automated system. You can script your own installer that extracts zip files. This offers more flexibility than the hr system, especially for issuing updates.

When you script for zips etc can you write the link file in the AppData folder with HISE? OSX permissions make this impossible in my mind but perhaps you know different.

[Matt_SF]

@DanH HISE can easily write the link-file in the AppData folder. This shouldn't be a problem : when doing so on OSX, the user is supposed to be prompted to allow the plugin writing permissions. It's similar to write the user info in a file during the plugin's authorization process.

[d.healey]

@Matt_SF

user is supposed to be prompted to allow the plugin writing permissions.

This only works on Catalina and newer as @Lindon and I found out.

[Matt_SF]

@d-healey you're right, worth mentioning. I remember the thread.

[Lindon]

@d-healey actually if I recall correctly, its not a problem for the Linkfile - as this lives in a user-based folder, the problem is the plug-in itself - which should go in the system folders
~/Library/Audio/Plugins/Component and ~/Library/Audio/Plugins/VST3

so (like you suggested David) I now place the plugins in the user equivalent

~User/<user name>/Library/Audio/Plugins/Component and ~User/<user name>/Library/Audio/Plugins/VST3

But generally - yeah you get to come across a whole range of permission based problems building your own installer...