Plugin performance (ram usage)

[Natan]

@UD-AUDIO
Hise Includes All Its Modules, No Matter You Use Or Not.
Ipp Also Adds An Extra 11 Mb Weight To The Dll Aswell :/

And There Is No Way To Remove Unused Codes To Free Up Some Space For Better Usage, Such As Using More Convolution Files.
Or More Png's.

That 29 Mb Is A Lot IMO.

[UD AUDIO]

@Natan I agree with you! So many things like svg or paint routines which are efficient..
But this would be a cherry on the cake.
In music production I'm very experimental and mostly not minimalistic.
Sometimes I need to route to a second mixer channel
just for using more fx plugins :D Reasons why I like lightweight vst..

[d.healey]

@Natan said in Plugin performance (ram usage):

Hise Includes All Its Modules, No Matter You Use Or Not.

I don't think this is true.

@UD-AUDIO

empty hise fx plugin

So this is a completely empty project with no modules?

[Natan]

@d-healey

@Christoph-Hart said in Size Per Module?!!!:

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.

[d.healey]

@Natan Oh interesting! But still 2-3kb so not the problem here.

@UD-AUDIO Are you doing release builds or debug builds?

[UD AUDIO]

No files inside the project subfolders etc.
No module or code !
But Content.makeFrontInterface(800, 600);

nothing else..

Made the empty plugin test with a release build.

[d.healey]

@UD-AUDIO

Made the empty plugin test with a release build.

But is the plugin a release build or debug build? If you just exported directly from HISE and didn't go into VS or XCode then it's a release build ;)

[Natan]

@d-healey said in Plugin performance (ram usage):

2-3k?

Wait, Your Empty Exported Plugin's Size Is 2-3 Kb?
No Way!!!

Mine At Least Is 28 MB, Like UD Said.

[d.healey]

@Natan No, but in that quote you posted Christoph says each of the modules when compiled comes to about 2-3kb.

[UD AUDIO]

@d-healey Yes, exported from HISE as FX plugin. No VS!

[d.healey]

@UD-AUDIO Try disabling IPP for plugins that don't need it.

[UD AUDIO]

@d-healey Yes I should! Do I need IPP for using the plotter as visualizer?

[d.healey]

@UD-AUDIO Not sure...

[UD AUDIO]

@d-healey
Plotter does work without IPP!
RAM usage is the same.
But the plugin file size decreased from 26 to 19MB.
And with IPP activated, HISE is crashing after compiling successfully.

And no matter if IPP on or off, I get this weird bug:

Those peaks disappear as soon I make the plugin window detached in my DAW.
But tweaking knobs does nothing to this bug.

[Natan]

@UD-AUDIO Plotter Has Nothing To Do With IPP :) Turn It Off With Confidence :)

[UD AUDIO]

@Natan Aye! :)

[UD AUDIO]

@Natan The bug is persistent! Looks like this now:
(Inside DAW)

There is a hidden options panel on top of that visualization.
That shouldn't be a problem, but idk.

I think this bug is almost the same as this one:
(Plotter in HISE)
Just make a new project, add a simple gain + LFO on gain modulation.
and also connect the plotter to gain modulation.

Can't say if this was a thing in earlier HISE versions.

[Natan]

@UD-AUDIO It Was There Since I Used Plotter.
It's A Grapgical Issue And Sometimes Goes Crazy, And Sometimes Fixes By It's Own.