![]() ![]() I am sorry if you took that as a smoke screen.Ģ. I was making a statement about your testing methodology. Shorthand, its a mess - but some people might find it workable.Ĭlick to expand.1. The bad news is, that the X9S forgets that you've switched to this setting after reboot. If you are a user and want both correct colors in apps and in video, you have to switch to RGB444 (and set your TV accordingly (black level high, full, 0-255 - or however the setting in your TV is called)) - at which point system level and video level should align (will double check this as well). Ie - when you are saying, that you are outputing a 16-235 signal, don't output a 0-255 signal with the colors remapped to the 16-235 range. Second, if you are Zidoo, make sure that whatever signal you are puting out is actually standards compliant. If you feed the signal through a LUT Box or probably even an AV receiver, all bets are off, because Zidoo does "something" to the output signal, that makes it not standards compliant.įirst, if you are Zidoo - concentrate on YCbCr (as it is the defacto AV standard) and make sure, that both system level (app) colors, and video colors are displayed correctly. Meaning, that theres something seriously off in terms of the device handshake and being standards compliant.īroken down into simple words: All your apps colors are probably wrong on the X9S, but the video colors in Kodi/ZDMC are ok, when you have the device at auto/default settings (= YCbCr modes). ![]() When going through my LUT Box, the color errors double in amount and in the same direction (chroma), and now even Kodis/ZDMCs video output shows the error that the App/System level showed before. This probably means, that the SOC handles "video level" (as in GPU assisted?) and "system level" color differently, but does it in a way that introduces significant color errors on the System/App level. This affects other Android apps as well (tested with Voodoo pattern generator)įor some reason though - in Kodi/ZDMC, when feeding a video file pattern, the color output readings are correct, when feeding the signal directly to a TV (which most of the people out there probably are doing). Mobileforge for example specifically expects the Android device to take PC Level colors (0-255), like any other Android App, then downconvert them if neccessary according to the output settings. When set to YCbCr the X9S outputs wrong color levels on the System Color level. Color Measurements taken in Voodoo Screen Test Patterns 3.4 (a different Android Pattern generator):Ĭolor error roughly "doubles in amount and direction" to the Voodoo Screen Test Patterns measurements in test scenario 1 (when connected directly to the TV). Color Measurements taken in Voodoo Screen Test Patterns 3.4 (a different Android Pattern generator)Ĭolor errors explode, same error profile as above (in regards to chroma).Īll measurements taken at the following settings: X9S set to YCbCr 444 output at 1080p60, TV set up accordingly (limited color space), X9S going through a 3D LUT box into the TV (not 3D LUT enabled).Ĭolor error suddenly appears, same rough "amount and direction" as in the color error cases above.Ĭolor error roughly "doubles in amount and direction" to the Mobileforge measurements in test scenario 1 (when connected directly to the TV).ģ. Color Measurements taken in Mobileforge (Android Pattern Generator):ģ. Color measurements taken in Kodi/ZDMC:Ĭolor errors are low, and pretty much "where expected".Ģ. I did the last outstanding measurements - and now the picture is pretty much clear.Īll measurements taken at the following settings: X9S set to YCbCr 444 output at 1080p60, TV set up accordingly (limited color space), X9S going directly into the TV.ġ. (I'm sorry for suggesting it.) But your idea of attributing the error to measuring a screen and not the signal, just so you'd have an explanation for your results was wrong and going by the data that already was posted, even a little unfair. I've already acknowledged, that your findings with Kodi/ZDMC and ONLY with Kodi/ZDMC were correct and not a PR plant. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |