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

Anuj Mittal am.devel at gmail.com
Thu Nov 22 17:18:41 CET 2012


On Thu, Nov 22, 2012 at 9:29 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Thu, Nov 22, 2012 at 04:45:31PM +0530, anuj mittal wrote:
>> 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
>
> this uses a old ffmpeg, and doesnt compile with latest ffmpeg so
> testing it is not easy.

True. It indeed would be difficult using this.

>
> btw, why are these patches not in main mplayer ?
>
>

Don't know :(


More information about the ffmpeg-devel mailing list