It has absolutely nothing to do with this howto here. Be happy with what you have. On topic again, please.
I've noticed some artifacts when using HQ scalers on 720p content (h264, mostly). Artifacts look like random color lines of noise and are not very noticeable. It seems to happen only on one system which is a Chromebox, Ubuntu 13.10, but with the ChromeOS kernel (Linux chrubuntu 3.8.11 #1 SMP Wed Jan 8 23:33:37 PST 2014 x86_64 x86_64 x86_64 GNU/Linux).
The hardware is Stumpy (SANDYBRIDGE Core i5).
vainfo:
http://pastebin.com/rDjMDcy7
There is no easy way to use the default Ubuntu kernel on Chromebox as it uses coreboot and requires a signed kernel (plus some set of custom patches and firmwares).
If I disable HQ scalers (set to 0% instead of 20%), artifacts disappear.
Could it be because of the kernel or should I try some other drivers/drm/mesa/xorg/vaapi versions?
DCCP847DYE NUC running the same drivers except the 3.13.2 kernel doesn't have this problem.
Debug Log please. If you are really unlucky, the GPU in your specific i5 is slow as hell :-)
Finally got my NUC up and running with your latest, and what can I say... it's perfect! I'm a happy cat
Thanks a lot fritsch.
edit: I'm sorry, of course team: fernetmenta, wsnipex, fritsch... you're going all in my hall of fame
For there are three that care for xbmc on enduser hardware, the fernetmenta, the wsnipex, and the unholy fritsch: and these three are doing one ppa.
(2014-02-13, 19:20)fritsch Wrote: [ -> ]Debug Log please. If you are really unlucky, the GPU in your specific i5 is slow as hell :-)
It happens only when I enable Lanczos3 optimized scaling. XBMC-CPU is ~20%.
Here is the log:
http://pastebin.com/dynDYjeD .
A HD2000 is too slow to do Lanczos 3 upscaling. Keep it on bilinear.
Btw. the 20% means that Lanczos is used only when the amount of scaling is larger than 20% as the source. It's totally unneeded to upscale 1080 to 1080 - with such a method.
Btw. use the intel gpu tools and check the performance monitor - that will show when it is at its limits.
Concerning the 847 Celeron. It should be too slow in general to use the SWFilter in combination with the "Deinterlace" method. It should do BOB quite fine, though.
> It's totally unneeded to upscale 1080 to 1080 - with such a method.
Did you mean 720 to 1080?
> Btw. use the intel gpu tools and check the performance monitor - that will show when it is at its limits.
Thanks for the hint, I'll try it.
> Concerning the 847 Celeron. It should be too slow in general to use the SWFilter in combination with the "Deinterlace" method. It should do BOB quite fine, though.
Yes, I'm using BOB on 1080i IPTV channels on NUC, it can't handle yadiff.
Nope - I meant 1080 to 1080. As this 20% takes care that the HQ scalers are only used when you "actually scale" a bit.
Example: 720 to 1080 is done with lanczos 3 with that setting 576 to 1080 also.
1920x800 to 1920x1080 is only done by nearest neighbour, cause of that setting.
Not sure I'm following you. Why would it upscale 1080 to 1080 if there is nothing to upscale at all and the setting is 20%?
I understand that with 20% setting 720 to 1080 is done with lanczos 3 and I'll change it to bilinear per your suggestion.
Problem is, that it's not that smart :-) If only one px width or height is different it uses that monster to upscale. Therefore the setting is a bit "fuzzy", e.g. we have a per centage value there.
OK, so if I set it to 40%, it will not upscale 720 to 1080 using lanczos 3 and it should be fine?