[FFmpeg-devel] [PATCH] start code detection for hardware decode in mpeg4/divx streams

[anuj mittal]

On Thu, Nov 22, 2012 at 8:19 AM, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Fri, Nov 09, 2012 at 03:58:01PM +0530, anuj mittal wrote:
>> On Mon, Oct 22, 2012 at 8:16 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
>> > On Mon, Oct 22, 2012 at 02:30:56PM +0530, anuj mittal wrote:

>> >
>> > I think the patches are ok
>> >
>> > As this patchset is about VAAPI basically, gwenole can you take a
>> > look too?
>>
>> ping
>
> hmm, as theres no reply from gwenole :(
>
> can you explain how the bug and fix can be reproduced, so i can
> test it before applying ?
> which player, command line and hardware do i need to test this ?

Thanks Michael. I've uploaded a sample file -
upload.ffmpeg.org/incoming/divx_frame_drop_vaapi.avi

I use mplayer with VAAPI patches maintained by Gwenole
(https://gitorious.org/vaapi/mplayer/commits/hwaccel-vaapi) or xbmc
(https://github.com/xbmc/xbmc.git) with VA support configured in
(--enable-vaapi).

To use mplayer with VA video out -

mplayer -vo vaapi -va vaapi <file name>

I'm using a notebook with Intel Atom and PowerVR video core. But you
can also use Intel core i3/i5 (Sandy/Ivy bridge based) with Integrated
graphics and configure and install libva
(http://en.wikipedia.org/wiki/Video_Acceleration_API#Supported_hardware_and_drivers).

You should be able to see the frame drops (about 30% of them) using
this sample file.

Thanks.

Anuj