Khronos public bugtracker – Bug 93
OMX_CONFIG_SATURATIONTYPE is defined incorrectly
Last modified: 2008-10-29 09:16:07 PDT
This bug is for OpenMAX IL. For OMX_CONFIG_SATURATIONTYPE, its member nSaturation is the value for saturation. The range of values is -100 to 100. The value 0x0 indicates no saturation change to pixel data. A value of -100 produces all black pixels, and a value of 100 produces all white pixels.
This description is incorrect (It looks like definition for lightness). The widely used definition of saturation is something like:
nSaturation is the value for saturation. The range of values is non-negative. The value 100 indicates no saturation change to pixel data. A value of 0 produces gray scale pixels.
The negative values have no real meaning for saturation, even though they are mathematically feasible.
Any value larger than 100 is subject to clamping due to the nature of saturation. It's not possible to increase saturation indefinitely.
There was no OpenMAX IL product in the public Bugzilla so I added one - will
try to find someone in the IL working group to take this.
BTW, since you're from NVIDIA, you should be able to get a Khronos member
login and use the internal Bugzilla. Generally speaking that's likely to get
better response since the WGs are more accustomed to dealing with bugs there.
I second Jon's comments. I invite Khronos members to input bugs on the internal bugzilla.
/Frederic (IL WG chairman)
Reassign to Frederic, also make him the default assignee for IL bugs.