Hey Eric,<div><br></div><div>Thanks for the informative e-mails detailing what you've done so far. I have a couple of questions for you:</div><div><br></div><div>- Did you have to apply any patches to ffmpeg checked out from Git? Which branch/tag of ffmpeg did you use?</div> <div>- Were you able to get the decoding/encoding acceleration working from ffmpeg command line?</div><div>- 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?</div> <div><br></div><div>Cheers,</div><div>Karthik<br><br><div class="gmail_quote">On Thu, Oct 6, 2011 at 10:26 AM, Erik Slagter <span dir="ltr"><<a href="mailto:erik@slagter.name" target="_blank">erik@slagter.name</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">*** UPDATE ***<br> <br> It seems to work now!<br> <br> The -va option was really there, that whas just my stupidity.<br> <br> I added "--enable-xrender" to the config flags.<br> <br> 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...)<br> <br> CPU usage is 55% without vaapi and 6-9% using vaapi.<br> <br> Stubborn as I am, I will still try again to make the patched mplayer to be in sync with the svn version...<div><div></div><div><br> ______________________________<u></u>_________________<br> Libva mailing list<br> <a href="mailto:Libva@lists.freedesktop.org" target="_blank">Libva@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/libva" target="_blank">http://lists.freedesktop.org/<u></u>mailman/listinfo/libva</a><br> </div></div></blockquote></div><br></div>