Changes between Version 8 and Version 9 of HWAccelIntro


Ignore:
Timestamp:
Oct 12, 2015, 12:06:22 PM (4 years ago)
Author:
gjdfgh
Comment:

Recommend a better place for looking at how a vdpau hwaccel API user looks like

Legend:

Unmodified
Added
Removed
Modified
  • HWAccelIntro

    v8 v9  
    1414http://http.download.nvidia.com/XFree86/vdpau/doxygen/html/index.html
    1515
    16 Note that VDPAU cannot be used to decode frames in memory, the compressed frames are sent by libavcodec to the GPU device supported by VDPAU and then the decoded image can be accessed using the VDPAU API. This is not done automatically by FFmpeg, but must be done at the application level (check for example the vo_vdpau.c module from MPlayer). Also note that with this API it is not possible to move the decoded frame back to RAM, for example in case you need to encode again the decoded frame (e.g. when doing transcoding on a server).
     16Note that VDPAU cannot be used to decode frames in memory, the compressed frames are sent by libavcodec to the GPU device supported by VDPAU and then the decoded image can be accessed using the VDPAU API. This is not done automatically by FFmpeg, but must be done at the application level (check for example the ffmpeg_vdpau.c file used by ffmpeg.c). Also note that with this API it is not possible to move the decoded frame back to RAM, for example in case you need to encode again the decoded frame (e.g. when doing transcoding on a server).
    1717
    1818Several decoders are currently supported through VDPAU in libavcodec, in particular MPEG Video, VC-1, H.264, MPEG4.