Hi,

I am trying to figure out which lcms functions are the
memory/time-expensive ones in order to integrate it in an efficient way. 
I gathered that profiles are not kept in memory when opened, so I should
be able to load loads of them. However, once you generate a transform
from two profiles, I assume from a few glances at the code that all its
tables are kept in memory which means I shouldn't have too many open at
the same time. Is that right?

What I'd like to do is have a whole bunch of images displayed at the same
time, each of them possibly requiring a different transformation and each
of them being transformed on-the-fly for screen display.
However generating the transform every time before rendering the image
would probably be too time-consuming. Generating all the transforms in
advance would be very memory-consuming. (If I understand things right).
Would storing the transform on disk (in a temporary device-link profile)
and loading the pre-calculated profile/transformation whenever necessary
speed things up, you think?

Any pointers would be very welcome. If not, I'll go ahead experimenting
myself and will report back what worked best for me.

Thanks
Stefan


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Lcms-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/lcms-user

Reply via email to