Re: [CinePaint] strange handling of SIGTERM

Milan Knížek <knizek.confy-VIXq6x/[email protected]> Tue, 18 Aug 2009 08:15:40 +0200
Newsgroups gmane.comp.video.cinepaint.user
Message-ID <1250576140.3981.27.camel@athlon>
Gene Selkov píše v Út 18. 08. 2009 v 00:11 +0100:
> 3. While zooming in or out with '+' or '-', the window does two
> strange things: (1) it grows; and (2), it re-positions itself. I end
> up chasing the window all over my screen. I wonder whether this
> behavior is optional and can be turned off.
> 
This is in settings (Interface tab) - change window size on zoom
(loosely translating from a localised version).
> 7. I feel I ought to put this question in a separate post, because it
> is so different from everything I've observed so far, and it's by far
> the most important one. It may be that I haven't really begun
> understanding color management. Whatever I tried to do during the last
> couple days left me with a suspicion that my display profile is
> applied twice. First when it is loaded into my display's LUT. And the
> second time, when Cinepaint opens my image. The reason I believe so is
There are two different things a display profile can do: (a) it sets the
display to a calibrated state (via changing LUT) and (b) it describes
the calibrated display colour space.

(a) is done with dispwin and other LUT loaders. Cinepaint cannot do
that.
Some of these tools also update the XICC property of X.org with the
actual profile data so that some application can utilise the "system"
display profile and do not require the user to set it specifically in
Preferences (GIMP, EoG, UFRaw and few others can do it, but CinePain
can't). From its principle, also colour non-managed application may
benefit from a calibrated display (if it was calibrated close to sRGB
gamma and its colour space is close to sRGB).

(b) is used by colour aware application like CinePaint. What CinePaint
does is that it converts on-the-fly from the Image profile to a display
profile. You can do the same e.g. with ImageMagick tools ("convert
-profile AdobeRGB.icm input.tif -profile display.icc -intent Perceptual
image_for_display.tif") and then display the image with colour non-aware
application (I guess evince, gThumb and ImageMagick's "display") and
compare.

> my camera isn't too bad either. Now, when I open that image in
> Cinepaint (regardless of the profile assigned), It looks too bright
It happens to me that sometimes CinePaint ignores the embedded profile
and assigns the working colour space instead. You'd better check with
Image / Profile Information.

> There is something profoundly wrong in my toolchain, because when I
> consider all these effects together, they add up to something like
> Escher's straircase. Does any of this seem familiar to anyone? Is
> there a rational way of sorting it out?
> 
As Frank recommended, use some synthetic profile for various testing to
make it obvious when things do not work. I use BRG.icc (it has swapped
colour channels so that the image in BRG space is displayed completely
wrongly in colour-non-aware application). It is available here for
download:

http://hoech.net/files/BRG.icc


regards,

Milan Knizek
knizek (dot) confy (at) volny (dot) cz
http://www.milan-knizek.net - About linux and photography (Czech
language only)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Cinepaint-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cinepaint-users