Size Per Module?!!!

[Natan]

Hey Hise Community

Wondering, How Much Each Module Adds Weight To The End Exported Dll File,
Did anyone try To Collect This Data, Or Is There Any Lines That Mention This?

For Example:

• Gain Module >>> 1 M.b
• Parametric Eq >>> 750 K.b

Thanks

[Casey Kolb]

Hmm, I could be wrong but I'm not sure it works quite like this. Most of the size comes from embedded image files, impulse responses, and the core HISE code. I'm not sure that adding or removing modules will make a dent in the weight of the plugin binary.

[Natan]

@Lunacy-Audio Just Try With / Without Ipp Included, The Size Will Go Up Down By 8 M.b Or So.

[d.healey]

@Natan IPP is not a module...

[Natan]

@d-healey Yeah, But I Mean, Why Not Having A Cheat Sheet For Refrence, So We Can Undrestand That
What Module Adds More Weight, More CPU.
Kinda A User Experienced Data Center.

[Christoph Hart]

Yeah, that's not how it works. It doesn't matter whether you add the parametriq EQ or not, the C++ code will always be compiled for every module in the HISE codebase. Just think at the possibility of dynamically adding effects - if it wouldn't have compiled every module already, this wouldn't be possible.

However the actual code size for each module is neglible (I would thing something around 2-3kB). What really eats up binary size are embedded resources (most of all the images), so if you care about a small plugin size, that's the spot where you can save the most.

[Natan]

@Christoph-Hart That Was Clear :) Thank You Christoph