RSS/Atom feed Twitter
Site is read-only, email is disabled

pushing color management further

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

pushing color management further Sven Neumann 27 Oct 21:51
  pushing color management further Alastair M. Robinson 28 Oct 00:17
Sven Neumann
2007-10-27 21:51:48 UTC (about 17 years ago)

pushing color management further

Moin,

another task that should be put on the agenda, perhaps even for 2.6:

Currently only the image display is color-managed. The color selectors and the previews in the core and in plug-ins aren't. This should be changed and it should be possible to reuse the existing ColorDisplay filters to do this job.

Reusing the display filters for this is probably the way to go. We would hovever have to make an optimization in the lcms module then. Currently each display filter loads the color profiles and creates a transformation object to convert between colorspaces. If we extend this to all previews and color selectors, then we will have to avoid this. So either we reuse the same display filter for all previews or we introduce a transformation cache. Perhaps doing both would be the best solution as multiple displays on the same image would also benefit from a transformation cache.

If anyone wants to work on this, please talk to me. I have some more thoughts spent on this already. So far I only wanted to have this brought up so that it isn't forgotten....

Sven

Alastair M. Robinson
2007-10-28 00:17:26 UTC (about 17 years ago)

pushing color management further

Hi,

Sven Neumann wrote:

either we reuse the same display filter for all previews or we introduce a transformation cache. Perhaps doing both would be the best solution as multiple displays on the same image would also benefit from a transformation cache.

I've implemented a Transform Cache in PhotoPrint - I think I've mentioned before that as a "signature" for matching the correct transform I use an MD5 hash of both source and destination profiles (excluding headers), as well as the rendering intent. Just throwing that in, in the hope it might be useful.

All the best, --
Alastair M. Robinson