2013-07-08, 15:59
(2013-06-19, 18:25)Robotica Wrote:(2013-06-19, 15:39)fritsch Wrote: Still some things AMD has to work on:
a) mpeg2 and mpeg4 hw accel
b) Bitstream Audio
c) Better deinterlacing quality.
And regarding the deinterlacing. So this is still not supported by the drivers, thus GPU. But as I understood CPU could still be used. In the past this was only single core due to XBMC's old FFMPEG. But nowadays FFMPEG is updated to a newer version. Does this also mean deinterlacing is done on multiple CPU cores?
(2013-06-19, 18:30)fritsch Wrote: We had this some time before, when the internal xvba was more buggy. It can be done - but it costs a lot more performance. I don't think the AMD GPUs can handle decoding + separate deinterlacing in high quality. We had BOB implemented that way, which also runs via xvba now. Bob needs one field and doubles the line it does not have, you find it in the xvba-sdk dokumentation, XVBATransfer iirc - read the last sentence about the scaling.
Offtopic: The BOB deinterlacer on intel needs more GPU load than decode and even more than encode (!) ... which was quite surprising :-)
As I understand, the h264@high L5.1 issue (and driver support for MPG2 and MPEG4) has been resolved (in driver and SDK) by AMD. I still wonder if Kabini GPU will be strongh enough to also do the deinterlacing?