VDPAU does not work with Libav 10 and XBMC 13

[Reinhard Tartler]

Control: tag -1 +help +upstream

On Sat, Mar 29, 2014 at 5:25 PM, Bálint Réczey <balint at balintreczey.hu> wrote:
> Hi,
>
> Could someone familiar with Libav debugging please check this bug?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742896
> XBMC seems to work with latest FFMpeg but not with latest Libav. :-(

Disclaimer: I've never used xbmc, nor do I have a radeon card where I
would use vdpau as described in the bug. However, in Message#15, the
debug output contains:

19:14:05 T:140477827372800   ERROR:  (VDPAU) Error: An invalid pointer was
provided. Typically, this means that a NULL pointer was provided for an
'output' parameter.(4) at VDPAU.cpp:1081

To me this looks like XBMC is providing either bad data, or isn't
using libavcodec the intended way. On a personal note, VDPAU in
libavcodec does not seem to me very well engineered and designed and
clearly underdocumented. This comment is not restricted to libav, it
equally applies to ffmpeg as well. Just compare the doxys:

https://libav.org/doxygen/master/group__lavc__codec__hwaccel__vdpau.html
http://www.ffmpeg.org/doxygen/trunk/group__lavc__codec__hwaccel__vdpau.html

Sorry that I couldn't me more helpful here. I'm tagging this bug
accordingly for now, maybe either libav or xbmc upstream developers
can help out here.

-- 
regards,
    Reinhard