Upload vst3 in the interface

[Matt_SF]

@Abyss yes, it doesn't matter who downloads the new version : the user or the app. The result will be the same, the old plugin will be overwritten by the new one. You'll have to take into account the file/folder permissions though.

[Abyss]

@Matt_SF I have a question about it : if my instrument is exported in VST3, will it be possible to change specific files whithout the user having to download the whole plugin again ? (like adding samples maps and changing scripts). Because my project size might be around 25Gb. Thank you.

[Matt_SF]

@Abyss adding samples / sample-maps would be possible but not scripts. Scripts are part of your plugin so adding new features for example is not possible without recompiling it.

[Lindon]

@Abyss use Expansions.

[Abyss]

@Matt_SF OK thanks

[Abyss]

@Lindon Like which one?

[Matt_SF]

@Abyss https://docs.hise.audio/working-with-hise/project-management/expansions/index.html

[Abyss]

@Matt_SF @Lindon it's very usefull. And do the extensions also have to be installed via an external app, or can they be added directly from the vst3 interface?

[Lindon]

@Abyss said in Upload vst3 in the interface:

@Matt_SF @Lindon it's very usefull. And do the extensions also have to be installed via an external app, or can they be added directly from the vst3 interface?

you need to build your own installer...I built mine in HISE, not too hard I think.

[d.healey]

@Abyss expansions can be added from within the plugin. But you still can't add new scripts because these have to be compiled into the plugin.

[Lindon]

@d-healey said in Upload vst3 in the interface:

@Abyss expansions can be added from within the plugin......

But you would need to write the code (either in an installer or in the plugin ) to do this - there is no default installer like there is for samples...