VST quite large

[coupe70]

Hi everyone,
this is my first post here.

I tried out HISE and made a very simple plugin with 3 buttons that
switch a lowcut between 3 different frequencies. No graphics, no
samples or anything. For the lowcut I use the 1st order filter integerated
in HISE.

When I build this VST2 plugin, it is 22MB big.
Seems a lot for such a simple plugin.
Am I doing something wrong...?

[Christoph Hart]

@coupe70 nope, ~20MB is the baseline for the stuff included in HISE. Why is that a problem?

[It_Used]

@coupe70 there are no limits on the size of loadable plugins in Daw, but it's important to understand that graphics are there anyway, default Juce resources fall into your plugin during assembly, if you add a lot of Pngs, your plugin will quickly pass the 50-100 MB mark.

[d.healey]

@coupe70 You should use VST3 instead of VST2

@Christoph-Hart Maybe the VST3 checkbox should be enabled by default for new projects?

[Christoph Hart]

@d-healey good idea. Done.

[coupe70]

Alright, thank you for your replies.
20MB is not a problem. A friend built a similar plugin using iPlug2 and his
plugin has 1,1MB, so we were just wondering if I made some newbie mistake. :-)

[Christoph Hart]

@coupe70 ah yes, iPlug has a notoriously small binary size and a very basic feature set if you compile a minimal example. Any JUCE made plugin has at least ~12MB of size because there are more things included (graphics frameworks, plugin wrappers, other stuff). HISE adds some things onto that - even if you just compile a effect plugin with a simple filter, the binary will include the code for the streaming sampler module, the scripting engine and all the rest.