Images Takes so Much Space on RAM!!!
-
That's not too bad. My current project hit 600mb
-
@Christoph-Hart @Dan-Korneff Thanks Guys, Glad I'm on safe side 🥲
-
@Natan I wouldn't count 600MB as a reasonable upper limit for image sizes but rather Dan going crazy on the filmstrips, so "safe side" is a bit optimistic :)
I like how I spent months of trimming the HLAC codec to bring the file size down by a few percents and allow the streaming buffers to use a smaller data type and then it's all up in smoke because of some 3D renders of a knob...
I remember doing some experiments during the PercX development of not storing the uncompressed images but decoding the PNG image in the paint routine, but that affected the UI performance to a point where I had to roll it back.
-
Comparable plug-in GUI memory usage is the 150MB range, so I'm well over a reasonable limit here. My film strips are rendered in larger areas to allow space for shadows, so I'm trying to work out a better system for that right now.
Got it down to 450MB, but I still have a ways to go. -
@Dan-Korneff Vectors not an option?
-
@d-healey I'm looking at drawing my shadows and other elements with vectors.
The other issue is I render my GUI in a 3D "perspective" view, so every component needs a separate film strip. -
@Dan-Korneff said in Images Takes so Much Space on RAM!!!:
The other issue is I render my GUI in a 3D "perspective" view, so every component needs a separate film strip.
Yeah no getting around that.
-
@Natan Where do you see this view?
-
@aaronventure It's a floating tile called Image Pool Table
-
@aaronventure Add it to the custom popups thingy
-
@Christoph-Hart would it make sense to enable this for backgrounds only? i.e. have the ability to turn it on for a panel or whatever. If I have 5 background images in a vsti, 20MB each althrough the are never all shown at the same time but change depending on parameters, each VSTi load takes up 100MB of ram just for the backgrounds?