[Libva] Libva Digest, Vol 27, Issue 19

Xiang, Haihao haihao.xiang at intel.com
Thu Oct 27 18:43:53 PDT 2011


Fetch mplayer from git://gitorious.org/vaapi/mplayer.git
and switch to hwaccel-vaapi branch


> I was trying to compile mplayer with vaapi support.  I downloaded the
> latest svn release:
> 
> $ ./configure --enable-vaapi
> Current branch master is up to date.
> Unknown parameter: --enable-vaapi
> 
> 
> I have libva and libva-devel rpms installed - but that doesn't seem to
> make a difference.  Is vaapi not part of mplayer's build options?
> 
> Thanks
> 
> 
> On Thu, Oct 27, 2011 at 2:00 PM, <libva-request at lists.freedesktop.org>
> wrote:
>         Send Libva mailing list submissions to
>                libva at lists.freedesktop.org
>         
>         To subscribe or unsubscribe via the World Wide Web, visit
>                http://lists.freedesktop.org/mailman/listinfo/libva
>         or, via email, send a message with subject or body 'help' to
>                libva-request at lists.freedesktop.org
>         
>         You can reach the person managing the list at
>                libva-owner at lists.freedesktop.org
>         
>         When replying, please edit your Subject line so it is more
>         specific
>         than "Re: Contents of Libva digest..."
>         
>         
>         Today's Topics:
>         
>           1. Re: Status of libva and mplayer/ffmpeg? (Karthik Kailash)
>           2. Re: deinterlacing on GM45 (Xiang, Haihao)
>           3. Re: Status of libva and mplayer/ffmpeg? (Gwenole
>         Beauchesne)
>         
>         
>         ----------------------------------------------------------------------
>         
>         Message: 1
>         Date: Wed, 26 Oct 2011 17:00:29 -0700
>         From: Karthik Kailash <karthik at freestreammedia.com>
>         Subject: Re: [Libva] Status of libva and mplayer/ffmpeg?
>         To: Erik Slagter <erik at slagter.name>
>         Cc: libva at lists.freedesktop.org
>         Message-ID:
>                <CAF3A2PSuDUkGf-kB
>         +HUhz=kMEHhbUg6kFaR7fXnEVny2xiag4Q at mail.gmail.com>
>         Content-Type: text/plain; charset="iso-8859-1"
>         
>         Hey Eric,
>         
>         Thanks for the informative e-mails detailing what you've done
>         so far.  I
>         have a couple of questions for you:
>         
>         - Did you have to apply any patches to ffmpeg checked out from
>         Git?  Which
>         branch/tag of ffmpeg did you use?
>         - Were you able to get the decoding/encoding acceleration
>         working from
>         ffmpeg command line?
>         - Which codec does ffmpeg use?  When I run "ffmpeg -codecs", I
>         only see h264
>         and h264_vdpau.  Do you see a codec that corresponds to h264
>         with vaapi?
>         
>         Cheers,
>         Karthik
>         
>         On Thu, Oct 6, 2011 at 10:26 AM, Erik Slagter
>         <erik at slagter.name> wrote:
>         
>         > *** UPDATE ***
>         >
>         > It seems to work now!
>         >
>         > The -va option was really there, that whas just my
>         stupidity.
>         >
>         > I added "--enable-xrender" to the config flags.
>         >
>         > Also I added "-vf-clr" to the options, which avoided the
>         filters
>         > deinterlace and screenshot from being used, apparantly using
>         filters breaks
>         > using vaapi (I could understand that...)
>         >
>         > CPU usage is 55% without vaapi and 6-9% using vaapi.
>         >
>         > Stubborn as I am, I will still try again to make the patched
>         mplayer to be
>         > in sync with the svn version...
>         >
>         > ______________________________**_________________
>         > Libva mailing list
>         > Libva at lists.freedesktop.org
>         >
>         http://lists.freedesktop.org/**mailman/listinfo/libva<http://lists.freedesktop.org/mailman/listinfo/libva>
>         >
>         -------------- next part --------------
>         An HTML attachment was scrubbed...
>         URL:
>         <http://lists.freedesktop.org/archives/libva/attachments/20111026/ee3ed0c5/attachment-0001.htm>
>         
>         ------------------------------
>         
>         Message: 2
>         Date: Thu, 27 Oct 2011 13:14:16 +0800
>         From: "Xiang, Haihao" <haihao.xiang at intel.com>
>         Subject: Re: [Libva] deinterlacing on GM45
>         To: Holger Kaelberer <hk at getslash.de>
>         Cc: "libva at lists.freedesktop.org"
>         <libva at lists.freedesktop.org>
>         Message-ID: <1319692456.2498.64.camel at xhh-ctg32>
>         Content-Type: text/plain; charset="UTF-8"
>         
>         GM45 doesn't support deinterlacing
>         
>         Regards
>         Haihao
>         
>         > Hi all,
>         >
>         > playing around with libva we found  that deinterlacing a TV
>         stream seems not to work on a Intel GM45
>         > chip.
>         >
>         > We are using the latest intel drivers from the g45-h264
>         branch on
>         > git.freedesktop.org/git/vaapi/intel-driver.git. Testing both
>         on a Nvidia chip and an Intel GM45 with
>         > mplayer + vaapi-patches and modified gstreamer-vaapi plugins
>         (see attached quick'n'dirty fix) we found:
>         >
>         > mplayer-withVaapi -vo vaapi:deint=2 -va vaapi ...
>         >      ... OK on nvidia (deinterlaced images)
>         >      ... NOT OK on Intel
>         >
>         > modified gstreamer-vaapi
>         >      ... OK on nvidia
>         >      ... NOT OK on Intel
>         >
>         > Did we miss something in our setup? Or maybe a known
>         restriction for intel drivers?
>         >
>         > Regarding the gstreamer-vaapi modification: It is based on
>         what was said in the following thread
>         >
>         http://lists.freedesktop.org/archives/libva/2010-July/000338.html
>         > Might be a feature to be integrated in the vaapi-plugins.
>         Could define another property in vaapisink
>         > (like deint={true, false}) allowing to enforce putSurface
>         flags set to VA_FRAME_PICTURE vs.
>         > VA_TOP_FIELD+VA_BOTTOM_FIELD. What do you think, Gwenole?
>         >
>         > Thanks,
>         >     Holger
>         
>         
>         
>         
>         ------------------------------
>         
>         Message: 3
>         Date: Thu, 27 Oct 2011 07:22:56 +0200
>         From: Gwenole Beauchesne <gb.devel at gmail.com>
>         Subject: Re: [Libva] Status of libva and mplayer/ffmpeg?
>         To: Karthik Kailash <karthik at freestreammedia.com>
>         Cc: libva at lists.freedesktop.org
>         Message-ID:
>         
>          <CAEDM96jeGcAXt_ovzZ0_mb7M7N=Gwo=uiRbHzNQYfnxXceTcAA at mail.gmail.com>
>         Content-Type: text/plain; charset=ISO-8859-1
>         
>         Hi,
>         
>         2011/10/27 Karthik Kailash <karthik at freestreammedia.com>:
>         
>         > - Did you have to apply any patches to ffmpeg checked out
>         from Git? ?Which
>         > branch/tag of ffmpeg did you use?
>         
>         Unless you want to sync both mplayer & ffmpeg git trees, I
>         recommend
>         you fetch out the ffmpeg subdirectory from the ffmpeg.git
>         around the
>         same date as the latest commit in mplayer. For ffmpeg.git use
>         something >= 2011/10/06. For libav.git, use something >=
>         2011/10/11 or
>         so.
>         
>         > - Were you able to get the decoding/encoding acceleration
>         working from
>         > ffmpeg command line?
>         
>         This does not exist yet. More generally, there is no HW
>         decoding/encoding acceleration in ffmpeg command line tool
>         aside from
>         Crystal HD (for decoding only).
>         
>         > - Which codec does ffmpeg use? ?When I run "ffmpeg -codecs",
>         I only see h264
>         > and h264_vdpau. ?Do you see a codec that corresponds to h264
>         with vaapi?
>         
>         "ffmpeg -codecs" should not even list h264_vdpau since it
>         won't work
>         in the tool either. However, the fact that you don't even see
>         h264_vaapi indicates that you probably have not built FFmpeg
>         with
>         VA-API support (--enable-vaapi + making sure libva headers are
>         available and usable). i.e. please check config.log &
>         config.mak.
>         
>         Regards,
>         Gwenole.
>         
>         > On Thu, Oct 6, 2011 at 10:26 AM, Erik Slagter
>         <erik at slagter.name> wrote:
>         >>
>         >> *** UPDATE ***
>         >>
>         >> It seems to work now!
>         >>
>         >> The -va option was really there, that whas just my
>         stupidity.
>         >>
>         >> I added "--enable-xrender" to the config flags.
>         >>
>         >> Also I added "-vf-clr" to the options, which avoided the
>         filters
>         >> deinterlace and screenshot from being used, apparantly
>         using filters breaks
>         >> using vaapi (I could understand that...)
>         >>
>         >> CPU usage is 55% without vaapi and 6-9% using vaapi.
>         >>
>         >> Stubborn as I am, I will still try again to make the
>         patched mplayer to be
>         >> in sync with the svn version...
>         >> _______________________________________________
>         >> Libva mailing list
>         >> Libva at lists.freedesktop.org
>         >> http://lists.freedesktop.org/mailman/listinfo/libva
>         >
>         >
>         > _______________________________________________
>         > Libva mailing list
>         > Libva at lists.freedesktop.org
>         > http://lists.freedesktop.org/mailman/listinfo/libva
>         >
>         >
>         
>         
>         ------------------------------
>         
>         _______________________________________________
>         Libva mailing list
>         Libva at lists.freedesktop.org
>         http://lists.freedesktop.org/mailman/listinfo/libva
>         
>         
>         End of Libva Digest, Vol 27, Issue 19
>         ************************************* 
> 




More information about the Libva mailing list