What contributes to WKP size?

[woodslanding]

I just re-laid out my gui, which involved replacing the background and a few button skins, (but mostly just resizing and moving things) and my WKP went from 65MB to 87MB.

Is there any way to tell what's causing the extra size? The new background is 3MB, but the old one was 4MB.

I'm getting memory errors more and more often when I try to save, so I'd like to figure out if there are any ways to slim my WKP memory footprint.

Also, it would be nice to have a 'save all patches' and 'reload all patches' for this situation (maybe I asked for this already?)

Thanks!
-eric

[nay-seven]

generally , preset managers can be responsible for those fat workspaces.

[senso]

yes presets but also bitmaps and other background images.

[woodslanding]

I just realized that now I am using dynamic loading for Kontakt sounds, it probably just depends on the samples I have selected at the time I save.....

No wait, the WKP doesn't have to save samples, right? Just the Kontakt preset info about where they are located, right?

I'm still stumped. I didn't change the wkp very much at all.... It's big because of the aforementioned issues, but niether of them changed in the latest version.

Oh well, no big deal. One question: am I less likely to run out of memory saving on a 64-bit machine with 8GB ram?

[woodslanding]

I have uploaded the offending patch for your amusement (and possible debugging)

It was my backdrop patch. It contained exactly one module, a panel, image module. I removed the BMP from the panel, and it was still 24MB. I removed the panel itself, and the patch was STILL 24MB!

I have uploaded the patch with the module, but no BMP. Maybe someone can figure out what happened.

http://www.sensomusic.com/forums/upload ... ground.zip

My wkp is back to usual size.

[nay-seven]

Right, seems this module keep the picture in memory, we gone to check