Quoting wm4 (2016-05-18 18:49:55)
> On Mon, 16 May 2016 15:53:31 +0200
> Anton Khirnov <[email protected]> wrote:
> 
> > ---
> >  doc/RELEASE_NOTES | 97 
> > +++++++++++++++++++++++++++----------------------------
> >  1 file changed, 48 insertions(+), 49 deletions(-)
> > 
> > diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES
> > index bda4789..f25c0e0 100644
> > --- a/doc/RELEASE_NOTES
> > +++ b/doc/RELEASE_NOTES
> > @@ -1,48 +1,31 @@
> >  Release Notes
> >  =============
> >  
> > -* 11 "One Louder"
> > +* 12 "Not Enough Trocadero"
> >  
> 
> Reservations about a new release at this point of time have been
> expressed on IRC. While AVStream.codec is deprecated and a new BSF API
> has been created, the parser API hasn't been updated yet. This is a big
> inconsistency, and we're going to have to live with it for how long?

I don't exactly see how the current situation is much worse than the
previous one, where the muxer/demuxers/parsers/bsfs/codecs had to step
very carefully around one AVCodecContext, which would explode horribly
if they did it wrong.
Yes, you still have to have a codec context to be used by parsers, but
I think not many people even use the parsers explicitly. And allocating
and filling a separate codec context, while ugly, is just a few lines.

-- 
Anton Khirnov
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to