Posts: 38
Joined: Jun 2015
Reputation:
0
So then it is pretty weird that datranquil was able to notice differences in the black rows image between 0, 1, 2, 3, I assume those are lower or equal to 16 black? since I can see them on my PC, I did try changing hdmi mode on projector but same result.
Posts: 23,437
Joined: Aug 2011
Reputation:
1,096
fritsch
Team-Kodi Developer
Posts: 23,437
Yeah - the problem is:
If Android clamps, we can workaround it, stop surface rendering, but render the surface with EGL and use a custom matrix to achieve limited range
If Android scales, we need to stop surface rendering, upscale to full range (with dithering) so that the damn driver could downscale again.
All solutions suck ... as they are quite slow (no direct zero copy rendering) and overhead :-(.
Also what I absolutely don't understand. When Android clamps - there should be no issue at all with MediaCodec surface rendering, besides they get their BT709 / BT601 wrong ... then they need to go whining in the corner and fix their mediacodec implementation.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,437
Joined: Aug 2011
Reputation:
1,096
fritsch
Team-Kodi Developer
Posts: 23,437
Really curious! Thanks much in advance.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 31,445
Joined: Jan 2011
2016-01-12, 22:51
(This post was last modified: 2016-01-12, 22:53 by Ned Scott.)
This is the firmware bug that has been hitting all of the Android TV boxes (exact results depend on TV hardware used, I think). Apparently Google broke something when fixing something else and didn't want to rush a second fix (which might break something else, and the cycle continues). So it took a while, at least a few weeks if not a month or more, to get a fix. The Nexus Player has already been updated with the fix, and I would expect the Shield TV and Razor Forge to follow with their own specific updates.
Posts: 23,437
Joined: Aug 2011
Reputation:
1,096
fritsch
Team-Kodi Developer
Posts: 23,437
@wesk05: Thanks very much for those tests. I sadly don't have those disks. Btw. kodi's picture viewer should not scale, but also clamp.
What do you propose?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 38
Joined: Jun 2015
Reputation:
0
Hmm so I am right in assuming the correct behavior of video player is to clamp? since all media content is made in limited range anyways? and since the SATV itself outputs at that range.
What I am wondering is why I can't see the 1 2 and 3 blacks (17, 17, 19 after scale) on that image,as they are clearly shown on wesk video, if it didn't scale I should be seeing a black screen only right?
Also since no one has the video of the image test, isn't it possible to use a picture from wesk second test and save it in the proper format to see if it looks different when opening via picture instead of video?