[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 148382] overexposure indication already when fully "saturated"
From:       Gilles Caulier <caulier.gilles () gmail ! com>
Date:       2010-01-05 6:44:37
Message-ID: 20100105064437.AFFFB2F14C () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=148382





--- Comment #15 from Gilles Caulier <caulier gilles gmail com>  2010-01-05 07:44:34 ---
Jens,

HSV is not exactly HSL, but in this case, we don't care.

http://en.wikipedia.org/wiki/HSL_color_space

H is not color component but the Hue.

HSL or HSL are not RGB. It's different color space.

>When will Value be 0.0? If all RGB components are 0.

yes

>When will Value be 1.0? If one of the RGB components is max.

no. R = max && G = max && B = max

Go to gimp, edit foreground color properties and select V component (Set 
components H=0 and S=0). Change V from min to max, and look RGB values.

This is want mean that we don't need to convert for RGB to HSV to check
under/over exposed pixels... ouf...

>Following this argumentation we should have (R=0 && G=0 && B=0) for >underexposure 

yes

>and (R=max || G=max || B=max) for overexposure.

no (R=max && G=max && B=max) 

This is the current implementation do.

Gilles

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]