[FFmpeg-devel] [PATCH] fix speex sample

[Jai Menon]

On 4/9/09, Reimar D?ffinger <Reimar.Doeffinger at gmx.de> wrote:
> On Thu, Apr 09, 2009 at 09:39:24AM +0200, Diego Biurrun wrote:
>  > On Thu, Apr 09, 2009 at 04:46:34AM +0200, Michael Niedermayer wrote:
>  > > On Wed, Apr 08, 2009 at 06:30:56PM -0700, Baptiste Coudurier wrote:
>  > > > Michael Niedermayer wrote:
>  > > > > On Wed, Apr 08, 2009 at 05:26:11PM -0700, Baptiste Coudurier wrote:
>  > > > >> On 4/8/2009 5:02 PM, Michael Niedermayer wrote:
>  > > > >>> On Wed, Apr 08, 2009 at 04:21:32PM -0700, Baptiste Coudurier wrote:
>  > > > >>>>
>  > > > >>>> Mpeg2 decoder has an important bug IMHO since some time. I
>  > > > >>>> reported it, and libmpeg2 does not have this bug and decodes
>  > > > >>>> correctly the first 2 frames. I lack some knowledge of the
>  > > > >>>> surrounding code, but I tried to work on it at least. It should
>  > > > >>>> not take you much time to figure out the problem I guess.
>  > > > >>> thats a feature request not a bug, its something very well known
>  > > > >>> since the code was written.
>  > > > >> What was your argument about other implementation supporting it ?
>  > > > >> Oh yes, users will stop using yours to use the one supporting it.
>  > > > >>
>  > > > >> FYI, many of my samples use this mechanism, I just didn't really
>  > > > >> realize it, I thought it was just broken link but finally, I
>  > > > >> discovered that libavcodec deliberately _skip_ 2 frames, even
>  > > > >> without telling you !
>  > > > >>
>  > > > >> Solution is simple, until fixed I will use libmpeg2.
>  > > > >
>  > > > > poor libmpeg2
>  > > >
>  > > > I'd say poor libavcodec, loosing one heavy user because of lousy
>  > > > maintainership.
>  > >
>  > > not implementing all feature requests != lousy maintainership
>  > > if you want this feature, you can implement it.
>  >
>  > So I will rephrase the question: What will it take for you to implement
>  > this so that FFmpeg can be a complete libmpeg2 replacement?
>
>
> Uh, I read most of it and I only vaguely remember what this is about.
>  Is there a roundup bug number for this?

issue 824

-- 
Regards,

Jai