xbmc
xbmc copied to clipboard
VAAPI: Use VPP deinterlacing by default
v2: correctly fallback
This tries to use VPP_BOB by default while falling back to Render BOB if init fails
Follow up of: https://github.com/fritsch/xbmc/commit/b1abbbe8bdef8732bfd424bf4ae53bbcfd502f9a
Yes - how to detect if current method sucks?
Following comes to my mind: a) Render / FFmpeg is used -> performance sucks, we drop, skip and run with high cpu load b) VAAPI-MCDI / VAAPI-MADI is used on a baytrail -> frames skip and drop cause we are too slow c) VAAPI-BOB drops and skips on the only to my knowledge single core Atom
What would be a good indicator? This method btw. should then be extended to the scalers (e.g. lanczos3 too much) ...
Start collecting performance indicators in a common object: level of render queue, skips, drops, etc. Those need a history for getting trends. That's a starting point. We need to look at that data and learn how to interpret it and react to it.
Where should that object live? We need render / player / Decoder / Audio Engine data in it.
start simple and leave audio. to start with I would have it owned by player.
there is also a lot of things you already know from tests like Bytrail won't make MCDI. this info can be added too.