On Sun, 15 Dec 2013 21:41:07 +0100, Diego Biurrun <[email protected]> wrote: > From: Anton Khirnov <[email protected]> > > --- > > Anton's draft plus minor changes, host/target libc among them. If people > don't think it is release-note-worthy, it could be removed again .. > > doc/RELEASE_NOTES | 130 > +++++++++++++++++++++++------------------------------- > 1 file changed, 55 insertions(+), 75 deletions(-) > > diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES > index 62207c6..9f654d6 100644 > --- a/doc/RELEASE_NOTES > +++ b/doc/RELEASE_NOTES > @@ -1,61 +1,40 @@ > Release Notes > ============= > > -* 9 "Plain Nine" > +* 10 "Eks" > > General notes > ------------- > > -From this release onwards, we have decided to drop the leading zero from our > -release numbers. There were no plans of ever changing it, so it carried no > -information. Thus this release is just a plain 9, the next will be 10 etc. > - > -A new library arrived in Libav during this development cycle -- its name is > -libavresample and it handles audio conversion and mixing. All users are > -encouraged to use it instead of the old, now deprecated, audio conversion > -API in libavcodec. > - > -The libpostproc library now resides in a separate tree. It was fully > independent > -of the other Libav libraries, not used by any of the tools and saw very > little > -development. For these reasons we decided that it has no place in Libav. A > -standalone Git tree is available at > http://git.videolan.org/?p=libpostproc.git > -for people wishing to use libpostproc. > - > -The major versions of the libavcodec, libavformat and libavfilter libraries > have > -been bumped, so they are not API or ABI compatible with the 0.8 release. The > -ffmpeg transcoding tool, kept for compatibility in 0.8, has also been > dropped. > - > -This release brings a number of significant changes in the libavfilter > library. > -Firstly, all the API dealing with filter internals is no longer public. The > -result is that creating user-side filters will not be supported until > -libavfilter is more mature. > -Secondly, full audio filtering support is now available along with a set of > -basic audio filters. We hope that their number will soon grow significantly. > -The avconv transcoding tool has of course been extended to handle audio > -filtering as well. > -There were a number of other API changes, most importantly the addition of > -the buffer sink public API. > - > -In the libavcodec library, one of the most notable changes is added support > for > -planar audio (i.e. not interleaved). Many decoders and encoders, that > previously > -did inefficient (de)interleaving internally, now only work with planar audio > -formats. Libavresample can be used for optimized conversion between > interleaved > -and planar formats. > - > -Of big interest to our Windows users, Libav now supports building with the > MSVC > -compiler. Since MSVC does not support C99 features used extensively by Libav, > -this has been accomplished using a converter that turns C99 code to C89. See > the > -platform-specific documentation for more detailed documentation on building > -Libav with MSVC. > - > -As usual, this release also contains support for some new formats, many > smaller > -new features and countless bug fixes. We can highlight Opus decoding / > encoding > -through libopus, encoders for Apple ProRes and Ut Video, WMA Lossless and > -RealAudio Lossless decoders, fragmented MOV/MP4 and ISMV (Smooth Streaming) > -muxers, 24-bit FLAC encoding, a large number of RTMP improvements and support > -for cover art in ID3v2, WMA, MP4 and FLAC. > - > -See the Changelog file for a list of significant changes. > +One of the main features of this release is the addition of reference-counted > +data buffers to Libav and their use in various structures. Specifically, the > +data buffers used by AVPacket and AVFrame can now be reference counted, which > +should allow to significantly simplify many use cases. In addition, > +reference-counted AVFrames can now be used in libavfilter, avoiding the need > +for a separate libavfilter-specific frame structure. Frames can now be passed > +straight from the decoders into filters or from filters to encoders. > + > +These additions made it necessary to bump the major versions of libavcodec, > +libavformat, and libavdevice, which was accompanied by dropping some old > +deprecated APIs. These three libraries are thus not ABI- or API-compatible > with > +the previous release. All the other libraries (libavfilter, libavresample, > +libavutil, and libswscale) should be both ABI- and API-compatible.
lavu and lavfi will be most likely bumped, so this won't be true -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
