2014-12-15, 21:18
(2014-12-15, 14:53)fritsch Wrote: It's quite hard to answer. In fact, when we use the vaPutSurface path a Full RGB conversion is done, we can "hint" 701 or 601 color format, which we do. Kodi does not touch this data anymore, as we use the VAAPi Upload to display those.
The OS driver then does the conversion back to "limited range".
We know, that this sucks like hell - and as we both, Fernetmenta and me are running VAAPI at home (Fernet in full RGB) and me (with a clamping AVR) with OS set to limited, really want to solve that by moving towards EGL, but this is not that easy, cause we don't have a Reference Clock for now, though the newly developed DRM Reference Clock could work.
Yeah, there is nothing we can "talk correct" or something - it's just fucked up as is. And the EGL codepath for vaapi is not even yet in the stable vaapi drivers, bleeding edge - nobody cared (on vendor side) for a much too long time.
Thanks for all the information, Fritsch. Rest assured that you aren't the only guys who care about this sort of thing, and that all of your efforts are very much appreciated by us end users - whether we know all the hard work and hair-pulling that went into the end result, or not! :-)
I'm looking forward to trying out the fixed VAAPI on the next OE release. Should be soon, right?