Not used PNG´s on interface.

[Matt_SF]

@danh said in Not used PNG´s on interface.:

@matt_sf I think I tried that once and it removed all the images!

Yes IIRC it did the same to me

[Christoph Hart]

@d-healey said in Not used PNG´s on interface.:

There is no point in compressing your images.

Not 100% true, they are embedded into the binary as PNG, so your plugin will be smaller.

[d.healey]

@christoph-hart said in Not used PNG´s on interface.:

Not 100% true, they are embedded into the binary as PNG, so your plugin will be smaller.

Oo that I did not know, very good!

[DabDab]

@lalalandsynth @d-healey @DanH @yall @Matt_SF How do you compress HISE exported plugins? A Simple Gain plugins with 20 kb PNG Knob Strip becomes 27 MB when it is Exported. This is a main Drawback of HISE. Where as core JUCE simple gain Plugins is 7 MB. Why such extra file Size?

[lalalandsynth]

@yall I guess I can go over 50mb using /bigobj.
I am currently making a plugin at 200% size and using 200mb of impulses.

I would rather not have the images or impulses exposed to the user , but if there are any problems with doing it with everything embedded, do tell. :)

[lalalandsynth]

@dabdab Why is that a drawback ? I mean, does that occupy more memory or are you thinking of download size ?

[d.healey]

@lalalandsynth said in Not used PNG´s on interface.:

I guess I can go over 50mb using /bigobj.

You can also put the image and audio files in a separate .dat file.

[lalalandsynth]

@d-healey What are the pros and cons of embedding versus a dat file ?
Also , how would I make the dat file if I exclude the image and audio files from the plugin export ?

[d.healey]

@lalalandsynth

What are the pros and cons of embedding versus a dat file ?

Smaller plugin size. I don't know but I suspect also in the case of audio files that it doesn't need to load them all into RAM when the plugin is opened but can just load them as they are needed from the data file - @Christoph-Hart is this correct?

Also , how would I make the dat file if I exclude the image and audio files from the plugin export ?

This is all I know - https://forum.hise.audio/topic/2794/audioresources-dat-file?_=1637758415384

[lalalandsynth]

@d-healey said in Not used PNG´s on interface.:

This is all I know

I see. If anyone has any further info that would be helpful.

I assumed I would need to copy the audio and image files into the appdata folder BUT I wonder if you select to not embed if it automatically creates these dat files that can then be placed into the appdata files ?
I would guess so.

@d-healey said in Not used PNG´s on interface.:

I suspect also in the case of audio files that it doesn't need to load them all into RAM when the plugin is opened

That would be cool.

[Matt_SF]

@lalalandsynth here you go : https://docs.hise.audio/working-with-hise/menu-reference/export/index.html#export-pooled-files-to-binary-resource

[DabDab]

I mean, does that occupy more memory or are you thinking of download size ?

@lalalandsynth In JUCE we can remove unwanted module that is not needed. For Example A simple Delay or Reverb plugin You don't need Juce Crytography, etc etc module, so it reduces file size. But In HISE all module gets compiled during VST /AU export. That is why it produces approx 27-30 MB .dll/VST3/.component Files no matter what kind of Plugins you design. My point is why every modules get compiled when it is not necessary?

Suppose you are making a EQ Plugins. Then what is the point to embed Delay, reverb etc etc modules?

[Christoph Hart]

@dabdab said in Not used PNG´s on interface.:

My point is why every modules get compiled when it is not necessary?

Because the bookkeeping and overhead on codebase management doesn't justify a file size difference of a few megabytes.