2018-11-08, 13:53
(2018-11-08, 10:15)wrxtasy Wrote:Yes, I think Nvidia chosen the wrong path to take (using conversion), but may be it was forced due to Android 7 API limitation.(2018-11-08, 08:11)wesk05 Wrote:(2018-11-06, 13:42)outcave Wrote: @timstephens24 and @noggin I can assure you that even if the Nvidia Shield Colorspace conversion done well I'm able to see chromatic differences on my Panasonic OLED TV between "pure" Rec. 709 and Rec. 709 converted to Rec. 2020 when I put in play Rec. 709 content.BT.709 to BT.2020 gamut mapping on Shield accurately follows ITU BT.2087 recommendation. Any luminance difference that you see with Shield's mapped output on a display has to do with the display not applying BT.1886 gamma for BT.2020 SDR input.
That may be the case be there appears to be an ever increasing list of displays not applying BT.1886 gamma for BT.2020 SDR inputs and then producing unacceptable results for end users with mixed Rec.709 and BT.2020 content.
The question then becomes have NVIDIA chosen the wrong path to take ?
Should they be using Rec.709 <<-->> BT.2020 colorspace switching vs the current Oreo colorspace conversion ?
The old underlying v3.xx, modded Linux Kernel would not be helping either.
Yes, if it's technically possible, Nvidia should use Rec.709 <<-->> BT.2020 colorspace switching instead to use colorspace conversion.
On my side I'm in contact with Nvidia Level 2 support, but I'm still trying to understand if a colorspace switching is technically possible on Andriod 8.
For what I know the Apple TV do that colorspace switching and I expect it will be the possibility also for the Nvidia Shield.