Posts: 12
Joined: Dec 2014
Reputation:
0
Hi, I recently installed dual boot Chrome OS/OpenELEC on Asus Chromebox with OpenELEC as default OS.
On my Sharp LCD TV LC-32M400M-BK (native resolution 1366x768) it is able to display the OpenELEC on boot up. Connection is direct HDMI.
On my Panasonic plasma TV TH42PV70H (native resolution 1024x768) it is showing up as if no signal. Tried both direct HDMI connection and HDMI connection through chromebox -> AVR -> TV.
Pls help on how I can fix the no display on Panasonic TV. Thanks.
Posts: 315
Joined: Mar 2013
Reputation:
7
Okay, I upgraded to RC2 and now the troublesome video plays back just fine in 4k - wasn't aware there would be such a performance difference! Trying to select any of the HQ scalers still results in a horrible framerate, but setting the threshold to 10% as you suggested leaves Auto working fine.
Downscaling the same 4k video to 1080p loses about 1 frame every 2 seconds with any of the HQ scalers, and with or without VAAPI (well, maybe a tiny bit better with VAAPI), but is rock solid on Auto/Bilinear.
Incidentally, any idea why in RC2 I now have the text "There are no settings available for this visualization" behind my Video Settings screen (which is otherwise normal?) Also, how the left-side labels for the "Open Elec" settings menu are all pushed all the way left, with only like a half character visible...
Posts: 23,277
Joined: Aug 2011
Reputation:
1,077
fritsch
Team-Kodi Developer
Posts: 23,277
Cool.
Remember to install a build that has the GPU hang fixed. I think Matt has documented that in the first post.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 315
Joined: Mar 2013
Reputation:
7
2014-12-21, 13:54
(This post was last modified: 2014-12-21, 14:05 by Sunflux.)
Sorry, UI error was the result of me having customized Confluence (and thus requiring me to update the copy and re-apply my changes).
Don't see any reference to a fixed build in the first post or Wiki, but I can probably wait until RC3. The issue is still only when "prefer VAAPI" is enabled, correct?
However, the PAR error I referenced is really messing up video. With the 10% HQ scaler setting, my default preference of Lanczos3 now changes to Nearest Neighbor for 1080p played at 1080p. But due to the PAR issue, it's still rescaling the video at all times (it thinks 1920 wide should be played at 1919, then the 1% aspect error allowance gets it back to 1920).
But even still, and SPECIFICALLY on videos that are not the full 1920x1080, but rather cropped vertically (for example, 1920x800), Nearest Neighbor is causing a noticeable doubling of vertical lines about every 100 pixels or so, despite the fact that it's ultimately playing the file back at its native resolution. Switching to Bilinear results in noticeable softening of the video compared to Nearest Neighbor. Removing the 10% HQ scaler setting lets me use Lanczos3 which looks better, but clearly it's still messing around with the video and isn't giving me 1:1 reproduction.
Posts: 315
Joined: Mar 2013
Reputation:
7
I have done that... but for some reason on any file that's less than 1080 pixels high, I'm getting visible resampling artifacts that I can watch come and go as I change resampling algorithms. Note that I do not see the same effect on any video that is the full 1920x1080 frame, just those that are letterboxed.