On Tue, Mar 12, 2013 at 12:54 PM, Anton Khirnov <[email protected]> wrote:

>
> On Tue, 12 Mar 2013 12:48:36 +0100, Anton Khirnov <[email protected]>
> wrote:
> > Based on a patch by Vittorio Giovara <[email protected]>
> >
> > Fixes Bug 378.
> > ---
> >  doc/APIchanges             |    3 ++
> >  libavcodec/avcodec.h       |    5 ++++
> >  libavcodec/h264.c          |   70
> +++++++++++++++++++++++++++++++-------------
> >  libavcodec/h264_ps.c       |   14 ++++-----
> >  libavcodec/options_table.h |    1 +
> >  5 files changed, 64 insertions(+), 29 deletions(-)
> >
> > diff --git a/doc/APIchanges b/doc/APIchanges
> > index 0d317fc..ff5884a 100644
> > --- a/doc/APIchanges
> > +++ b/doc/APIchanges
> > @@ -13,6 +13,9 @@ libavutil:     2012-10-22
> >
> >  API changes, most recent first:
> >
> > +2013-03-xx - xxxxxxx - lavc 55.0.0 - avcodec.h
> > +  Add CODEC_FLAG_UNALIGNED to allow decoders to produce unaligned
> output.
> > +
> >  2013-03-xx - Reference counted buffers - lavu 52.8.0, lavc 55.0.0, lavf
> 55.0.0,
> >  lavd 54.0.0, lavfi 3.5.0
> >    xxxxxxx, xxxxxxx - add a new API for reference counted buffers and
> buffer
> > diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
> > index e48b114..ced7fed 100644
> > --- a/libavcodec/avcodec.h
> > +++ b/libavcodec/avcodec.h
> > @@ -609,6 +609,11 @@ typedef struct RcOverride{
> >     Note: Not everything is supported yet.
> >  */
> >
> > +/**
> > + * Allow decoders to produce frames with data planes that are not
> aligned
> > + * to CPU requirements (e.g. due to cropping).
> > + */
> > +#define CODEC_FLAG_UNALIGNED 0x0001
>
> Note that I'm not quite convinced that adding a flags like this is the best
> solution.
>
> Better suggestions are welcome.
>
>
I tested this patchset and I would OK it. The additional flag solution is
not that bad: with it the fate test attached on the bug report (on
cvfc1_sony) passes fine.
Vittorio
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to