Posts: 315
Joined: Mar 2013
Reputation:
7
2015-09-22, 13:38
(This post was last modified: 2015-09-22, 13:44 by Sunflux.)
Yes, I was just checking that out. Currently to avoid banding, I'm doing the following:
* Not using the VAAPI copying method.
* In autostart.sh, I force full color space.
* In Kodi settings, I enable limited color space (to fix up the dark GUI - has no effect on video).
* In my television, I force limited color space.
This has the effect of leaving limited range videos as unchanged limited range while being sent over a full range color space. This would normally make blacks grey, which is why I force the TV back into limited range. Using the CPU copying method, this prevented any color space conversions and prevented banding from occurring.
You state: No adjustment of autostart.sh for full range is needed anymore - it is done automatically Check your "Use Limited Range setting" if you feel everything is too dark.
Now, assuming my TV stays fixed to "limited" color space (needed for my other CE devices on the same input, and I don't trust the reliability of its automatic detection), am I safe letting Kodi go back to automatic operation (remove the autostart.sh line?) Or, should I force it into Limited space via autostart, or does the Kodi menu option do more than just adjust the GUI now?
Posts: 315
Joined: Mar 2013
Reputation:
7
Okay, as usual you're right! Upgraded fine, VAAPI enabled, graduations look flawless just like I had before, but now with an even more power efficient method.
On one sample 1080p file, CPU copying uses around 8-14% CPU power, but just 2-8% with VAAPI.
Must say... Kodi/OpenElec appliances are basically my favorite tech devices out there! Between all the customizations, hacking my display EDID, modifying Confluence to include home menu options for my security cameras (and putting the year of a movie on the pop-up info bar - why isn't this done already??)... it performs better than any other media solution out there!
Posts: 315
Joined: Mar 2013
Reputation:
7
Assuming a few minutes watching is enough, no, not so far.
However has something changed with lipsync? Did you remove OE's internal 175ms delay?
Posts: 26
Joined: Sep 2015
Reputation:
0
Tried last Jarvis release maybe update first page and add PVR addons are incompatible. Back to older release.
Posts: 315
Joined: Mar 2013
Reputation:
7
2015-09-22, 14:38
(This post was last modified: 2015-09-22, 14:41 by Sunflux.)
Yup, seems like the 175ms is still needed for me. Put it back in, and everything's fine again.
(Not sure I need the default 50ms delay - is that a stock OpenElec item?)
I think some users have *never* needed a delay on 24hz material (even before now), although no one has adequately explained why. At least as far as my experience, I need it on this Marantz Receiver + Sony TV combo, and in another room I also need it on a Marantz Receiver (2 different models built 7 years apart) and Pioneer TV combo. I've also needed a similar delay on a Dune media player, so Kodi is not unique... but do not need it on a PS3 playing Blu-rays, or a Sony dedicated Blu-ray player. Strange, huh?