It is currently Thu Feb 27, 2020 4:59 pm


Hauptwerk Memory Management

Using the CODM to create your own organ definitions, exchange CODM organ definitions, ...
  • Author
  • Message
Offline
User avatar

chr.schmitz

Member

  • Posts: 324
  • Joined: Mon Aug 26, 2013 12:49 am

Hauptwerk Memory Management

PostFri Aug 26, 2016 7:02 am

I have two questions regarding Hauptwerk memory management.

1. Does every screen provided by a sample set occupy memory or only the screen(s), which are currently displayed?

2. Does it make sense to compress graphic files (E.g. http://compresspng.com. I tried different tools, but this was by far the most effective.) in order to decrease the memory footprint of the displayed image set?

Thanks in advance!

Best,
Christoph
Offline
User avatar

mdyde

Moderator

  • Posts: 11604
  • Joined: Fri Mar 14, 2003 2:19 pm
  • Location: UK

Re: Hauptwerk Memory Management

PostFri Aug 26, 2016 2:13 pm

Hello Christoph,

chr.schmitz wrote:1. Does every screen provided by a sample set occupy memory or only the screen(s), which are currently displayed?


All images specified in the organ definition are loaded whenever you load the sample set. (That's necessary for sufficient real-time performance.)

chr.schmitz wrote:2. Does it make sense to compress graphic files (E.g. http://compresspng.com. I tried different tools, but this was by far the most effective.) in order to decrease the memory footprint of the displayed image set?


As far as I know only the image size and bit-depth (8-bit colour, etc.) affects the memory footprint, since I believe the image is stored in memory uncompressed (again for real-time performance reasons). The underlying multi-platform library and operating system handle those things. File format and compression are only relevant for loading/saving images (disk space, loading speed, etc.).

I wouldn't really worry too much about it anyway, since image files are usually tiny compared to the sample data. I'd suggest just using PNG files, which are reasonably well compressed anyway (and thus may load slightly faster and take up less space in installation media), loss-less, and support transparency.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.

[Please use email or the Contact page if you need to contact us privately, rather than private forum messages.]
Offline
User avatar

chr.schmitz

Member

  • Posts: 324
  • Joined: Mon Aug 26, 2013 12:49 am

Re: Hauptwerk Memory Management

PostSat Aug 27, 2016 12:44 pm

Hello Martin,

thank you very much for the rapid response!

Christoph

Return to Custom Organ Design Module (CODM)

Who is online

Users browsing this forum: No registered users and 1 guest