VST VST3 Packing Software

[DabDab]

@d-healey Cool. Thanks boss.

[d.healey]

Also on Mac you'll need to learn about Notarization and Code Signing - https://www.kvraudio.com/forum/viewtopic.php?t=531663

[DabDab]

@d-healey Hello can you please tell me how to set Custom directory for .ch1 files with Inno SetUp?

I want to install it on C:\Users\Username\Documents\Horrot\OpenVoice\Samples
Here User name will be Replaced by Actual user name.
Example C:\Users\DabDab\Documents\Horrot\OpenVoice\Samples

[Tania Ghosh]

@DabDab Use {userdocs} to get the job done.

Example.....
DefaultDirName={userdocs}\MyCompanyName\VstName\Samples\

[d.healey]

Don't bundle your samples in an installer unless the sample content is tiny. Use the built in sample installer system instead.

[Matt_SF]

@d-healey what are the reasons not to bundle everything in one installer ? I've managed to build an installer asking the user where to install the plugin and the sample library and it works fine (althought I've tested it but not distributed yet). The installer creates the required path file in the appropriate Windows folder and the samples are found on the plugin first launch.
That being said, you've got way more experience than me...

[d.healey]

@Matt_SF said in VST VST3 Packing Software:

what are the reasons not to bundle everything in one installer

It might be fine in your case but if you have a large library, like 2GB+ then you're asking the user to download a single large file which is usually less reliable than downloading multiple smaller files.

If you want to issue an update in the future to the plugin you also have to redeliver the same sample content to the user which means another large download for them and more bandwidth used for you. Or if you want to just deliver the update in a separate installer you then have to provide two installers that new users need to run in the correct sequence. And of course the problem is multiplied for additional updates.

And there is no good reason not to use the built in sample installer provided by HISE :)

[Matt_SF]

@d-healey thanks David for your insights, obviously I didn't think that far
Really the only reason I had in mind, not to use the HISE installer was the end-user experience : once you've installed the plugin, you have one more operation to do to finally be able to use the plugin. Otherwise it's indeed the simpler option.

I can share the inno script though if anyone in interested...

[DanH]

@Matt_SF Yes please :) I've made my own (with lots of help) but interested to cross reference with another.

I found users preferred a more familiar approach to sample installation using recogniseable .exe / .pkg installers than the Hise method.

I have two installers, Plugin and Samples, so for updates I'll only need to supply the Plugin one.

[d.healey]

@DanH said in VST VST3 Packing Software:

I found users preferred a more familiar approach to sample installation using recogniseable

Everyone prefers what they are already familiar with ;) We have to get them familiar with something new, I've had very few issues from my customers, I think the key is good documentation/videos.

I get way more issues from Kontakt users!

[Matt_SF]

@DanH It came originally from Lindon's post here :
https://forum.hise.audio/post/10923
I just modified it but it might not be perfect.

innoInstallerScript.zip

@d-healey you're right but even by providing docs/videos I had many users who had problems installing Kontakt libraries so I thought this time I'll make everything the most simple I can

[d.healey]

@Matt_SF If you want to make it really simple you could put a downloader directly into your plugin ;)

[Matt_SF]

@d-healey yes I've thought of that and I think it can be great but I didn't found time to try it yet. This is the next thing on my to-do list !