[gst-devel] How to build gstreamer pipeline with VAAPI hardware acceleration?
tingustar at gmail.com
Thu Apr 8 12:38:08 CEST 2010
>From what file hardware-accelerated is explicitely disable? Is it
There are 3 pixel formats are added in ffmpeg: PIX_FMT_VAAPI_MOCO,
PIX_FMT_VAAPI_IDCT and PIX_FMT_VAAPI_VLD. It seems all decoding part
is done in ffmpeg so I think gstreamer (gst-ffmpg) only needs to
detect if gfx driver supports VAAPI and in the end, pass the VAAPI
surface id instead of buffer to xv sink.
Does gstreamer have a plan to add some gst-specific plugins to enable hwaccel?
2010/4/8 Edward Hervey <bilboed at gmail.com>
> On Thu, 2010-04-08 at 18:01 +0800, Mr. Tingustar wrote:
> > I rebuilt ffmpeg package with
> > --enable-hwaccel=h263_vaapi \\\
> > --enable-hwaccel=h264_vaapi \\\
> > --enable-hwaccel=mpeg2_vaapi \\\
> > --enable-hwaccel=mpeg4_vaapi \\\
> > --enable-hwaccel=vc1_vaapi \\\
> > --enable-hwaccel=wmv3_vaapi
> > Gst-plugins-bad, gst-plugins-ugly and gstreamer-ffmeg work fine. But I
> > don't know how to build the gstreamer pipeline that can enable ffmpeg
> > hwaccel decoding (VAAPI based). Can anyone share some guide, or
> > gstreamer is not ready for VAAPI hwaccel?
> We explicitely disable support of hardware-accelerated codecs from
> ffmpeg in gst-ffmpeg. There isn't a unified way to forward the
> va-api/vdpau/hw specific information between ffmpeg and gstreamer.
> In order to have proper VAAPI acceleration support in GSTreamer, we
> would need some gst-specific plugins.
More information about the gstreamer-devel