[lmyllari]

lmyllari, did u see my posting where i tried ur configurations, any word about it?

Problem is for ME i see NO difference when disabling VA-API and set it to software decoding,
i now have 3.2.3 running with autostart set to Full-RGB and i get as opposed the crushed blacks,
but switching VA-API on/off makes no change for me...i even tried rebooting after disabling it...still no change...

And where in the XBMC Display Settings can i choose 16...235, i can not see that option...should be in the same menu as VA-API i guess...?

Hi gamble,

I saw your post but couldn't yet figure out what was going on. Can you clarify how changing the RGB range with xrandr works for you? Are you getting grey blacks with "Limited 16:235" and crushed blacks with "Full"?

The color problem doesn't seem to be with VA-API decoding itself, any path which uses bt.601 will show the same issue. Maybe take a look at xbmc log and see what the player says?

The 16..235 option is only in Gotham, but 16..235 didn't work reliably for me using VA-API. The way VA-API works I'm not optimistic that it can be implemented nicely.


edit: I think the VA-API post processing code in Intel driver has the same problem, and the API doesn't seem to support limited range output. For high quality output, the best bet might be multithreaded software decoding in Gotham. I wonder if the VA-API devs would be open to adding support for user specified coefficients..