On Apr 25, 2014, at 7:48 AM, Martin Kytzia <m.kytzia(a)uni-wuppertal.de> wrote:
Thanks, i already profiled mobile devices and compered
it with the eciRGB_v2 (see screenshot)
Green: Samsung Galaxy S5
Blue: Tablet Sony Xepria Z2
Red: eciRGB_v2
I have tested much more mobile devices and the results look the same like with these two
devices. So i think a new workingspace would be necessary because of new display
technologies like AMOLED etc.
Why not ProPhoto RGB (ROMM RGB)?
Some manufacturers of display technologies are diverging from sRGB. But since they
aren't converging on something else, any chosen intermediate space meant for such a
class of products will necessarily need to be large.
That means the intermediate space itself won't approximate the color space of a
specific device. Until there's color management in the device (e.g. as an iOS and
Android API) to compensate for the difference between intermediate and display spaces,
such an intermediate space is unsuitable for encoding images delivered to the device.
Further, we also need a reliable way to determine the display color space of a specific
device with sufficient accuracy (i.e. not perfect or lab quality, but "helpful"
accuracy rather than "oh nice we just made things worse, thanks a lot"),
otherwise color management in the device can't help. And this goes not just for mobile
devices, but it's still a problem with desktop displays which routinely contain bogus
chromaticity information in EDID and don't contain tone response information at all.
So I'm not really understanding what problem a new intermediate space is trying to
solve.
Chris Murphy