Kodi Community Forum

Then pick my PR from above and rebuild OpenELEC and see if that makes it better. Alternatively, Fake your EDID to announce correct values :-)

Heh, since I have *no* idea how to rebuild, I'll just hope your fix is included in RC3!

(Stupid Sony - even if 1.000512 is for some reason the exact mathematically correct aspect ratio, who cares! 1.000000 is much easier to enter!)

No, it won't be there. Basically it's a workaround for broken hardware and risk is too large to break standard conform TV sets that announce a pixelRatio of 1.0 as it should be.

And post a Debug Log btw. so that I can see what your TV announces. Enable debuglogging, restart, play such a video and post the result.

Edit: And as you have 4K output! Every 1080p video needs to be upscaled. You can drive your output at 1080p and let the TV scale if you like that better.

(2014-12-21, 13:20)fritsch Wrote: [ -> ]Cool.

Remember to install a build that has the GPU hang fixed. I think Matt has documented that in the first post.

hey, where i can find the link for this build? its not in the wiki and im not sure when is oe rc3 is coming

thanks.

OE RC3 will be released today. Final preparations and testing is just going on. Then you can pick that.

great news, what about regular kodi for ubuntu? will it be updated in the unstable repo as well? if so, i prefer just to update that instead of switching to OE

I just purchased the Asus Celeron Chromebox as a gift for someone for Christmas. I have Ubuntu and ChromeOS setup as dual boot.

I have a Logitech keyboard and mouse that I am having major issues with. I have no problem with the keyboard as far as selecting Ctrl D or Ctrl L but once I am booted into ChromeOS or Ubuntu the mouse and keyboard become completely unresponsive. The keyboard will work sometimes in Ubuntu but the mouse is unusable. This same mouse and keyboard work fine on my Home Theater Computer in the same room in both Windows and Ubuntu.

Is it worth me buying another Mouse and Keyboard and trying it or could it be an issue with the Chromebox. I do not own a wired mouse or keyboard to try (Can you even buy them anymore?).

Any troubleshooting tips?

(2014-12-21, 14:26)fritsch Wrote: [ -> ]And post a Debug Log btw. so that I can see what your TV announces. Enable debuglogging, restart, play such a video and post the result.

Edit: And as you have 4K output! Every 1080p video needs to be upscaled. You can drive your output at 1080p and let the TV scale if you like that better.

I posted a log in the other thread where we were discussing this issue.

http://xbmclogs.com/show.php?id=366718 (however the log site seems down right now?? can't upload a new one!)

Here's the relevant part:


Since Kodi's 1080 -> 2160 upscaling is not particularly good (at least not as far as the Chromebox supports, and the TV's is really quite excellent) I'm normally in 1080p and only go to 2160p for 4k videos.

Anybody has problem with displaying OpenELEC or Chrome OS on specific TV after successfully installing standalone or dual boot?

I had display problem in developer mode on Panasonic TV. But then I was able to successfully install and display dual boot on a Sharp LCD TV, but after moving the installed chromebox back to Panasonic TV, it still fails to display OpenELEC (default OS) or Chrome OS if I try Ctrl D.

Hmm, interesting. Taking a screenshot of a 1920x800 file being played, it's actually occupying 1920x808? Thus why the doubled lines every 100 pixels in Nearest Neighbor? Properties in debug log show:

07:37:26 T:140159228024576 INFO: ffmpeg[7F795CFF9700]: Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)

07:37:32 T:140158590506752 NOTICE: fps: 23.976024, pwidth: 1920, pheight: 800, dwidth: 1920, dheight: 800
07:37:32 T:140158590506752 DEBUG: OutputPicture - change configuration. 1920x800. framerate: 23.98. format: VAAPI_NV12
07:37:32 T:140158590506752 NOTICE: Display resolution ADJUST : HDMI1: 1920x1080 @ 23.98Hz (22) (weight: 0.000)

And yet a screen capture clearly shows the viewable window as 808 pixels high:

http://i59.tinypic.com/20i6hl5.png


That seems way too much to account for the PAR error.

(2014-12-21, 14:36)sh33p Wrote: [ -> ]great news, what about regular kodi for ubuntu? will it be updated in the unstable repo as well? if so, i prefer just to update that instead of switching to OE

?? RC3 is there for a very long time. But final is not far. And it fixes nothing you would want on your intel hardware, kodi wise. The most wanted fix is the gpu hang, that is fixed. But this is a kernel issue. See my VAAPI thread in the linux forum section, it has links to working kernels.

(2014-12-21, 15:34)Sunflux Wrote: [ -> ]Hmm, interesting. Taking a screenshot of a 1920x800 file being played, it's actually occupying 1920x808? Thus why the doubled lines every 100 pixels in Nearest Neighbor? Properties in debug log show:

07:37:26 T:140159228024576 INFO: ffmpeg[7F795CFF9700]: Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)

07:37:32 T:140158590506752 NOTICE: fps: 23.976024, pwidth: 1920, pheight: 800, dwidth: 1920, dheight: 800
07:37:32 T:140158590506752 DEBUG: OutputPicture - change configuration. 1920x800. framerate: 23.98. format: VAAPI_NV12
07:37:32 T:140158590506752 NOTICE: Display resolution ADJUST : HDMI1: 1920x1080 @ 23.98Hz (22) (weight: 0.000)

And yet a screen capture clearly shows the viewable window as 808 pixels high:

http://i59.tinypic.com/20i6hl5.png

That seems way too much to account for the PAR error.

07:37:10 T:140160032450432 INFO: ID:0x48 Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
07:37:10 T:140160032450432 INFO: Pixel Ratio: 1.000512

1920 / 1.000512 = 1919,017463059

Yeah, teach your TV to behave better. For the 808 that's not an issue. It is centered and the rest of the surface is black, but the 1919 introduces a ratio change, rescaling and so on. You need the patch I posted above.

(2014-12-21, 15:35)fritsch Wrote: [ -> ]

(2014-12-21, 14:36)sh33p Wrote: [ -> ]great news, what about regular kodi for ubuntu? will it be updated in the unstable repo as well? if so, i prefer just to update that instead of switching to OE

?? RC3 is there for a very long time. But final is not far. And it fixes nothing you would want on your intel hardware, kodi wise. The most wanted fix is the gpu hang, that is fixed. But this is a kernel issue. See my VAAPI thread in the linux forum section, it has links to working kernels.

yes that's exactly what i needed! thank you sir!

(2014-12-21, 15:38)fritsch Wrote: [ -> ]

(2014-12-21, 15:34)Sunflux Wrote: [ -> ]Hmm, interesting. Taking a screenshot of a 1920x800 file being played, it's actually occupying 1920x808? Thus why the doubled lines every 100 pixels in Nearest Neighbor? Properties in debug log show:

07:37:26 T:140159228024576 INFO: ffmpeg[7F795CFF9700]: Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)

07:37:32 T:140158590506752 NOTICE: fps: 23.976024, pwidth: 1920, pheight: 800, dwidth: 1920, dheight: 800
07:37:32 T:140158590506752 DEBUG: OutputPicture - change configuration. 1920x800. framerate: 23.98. format: VAAPI_NV12
07:37:32 T:140158590506752 NOTICE: Display resolution ADJUST : HDMI1: 1920x1080 @ 23.98Hz (22) (weight: 0.000)

And yet a screen capture clearly shows the viewable window as 808 pixels high:

http://i59.tinypic.com/20i6hl5.png

That seems way too much to account for the PAR error.

07:37:10 T:140160032450432 INFO: ID:0x48 Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
07:37:10 T:140160032450432 INFO: Pixel Ratio: 1.000512

1920 / 1.000512 = 1919,017463059

Yeah, teach your TV to behave better. For the 808 that's not an issue. It is centered and the rest of the surface is black, but the 1919 introduces a ratio change, rescaling and so on. You need the patch I posted above.

...And I just figured out what's causing the 808 pixel issue. Disabling the 1% allowable aspect ratio error fixes the vertical scaling and returns the video to 800 pixels high in a 1080 window (but of course returns the horizontal problem). So, it's a MANDATORY 1% error - enforced if it can be, no matter what..800 + 1% = 808.

So to fix a 1 pixel horizontal scaling issue, I'm expected to accept an 8 pixel vertical scaling issue? If the file's 1050 pixels high, that'll be an 11 pixel error! Gee. I do wish your "rounding error" fix would be made mainstream, because the alternate fix is worse than the problem!

Any way to simply override the screen's PAR without a complicated EDID replacement? Or ignore it?