--- src/download | 22 ++++++++++++++++++++ src/news | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+)
diff --git a/src/download b/src/download index 9f0b89e..1680607 100644 --- a/src/download +++ b/src/download @@ -198,6 +198,28 @@ selected changes from the development branch, which therefore receives much more and much faster bug fixes such as additional features and security patches. </p> +<a name="release_11"></a><h2>Libav 11 "One Louder"</h2> + +<p> +11 was released on 2014-09-08. It is the latest point release from the 11 +release series. 11 was published 2014-09-08, the 11 branch was cut +2014-08-20. Please give us feedback and use +our <a href="https://bugzilla.libav.org";>Bugzilla</a> for filing bugs. +</p> + +<p> +<a href="releases/libav-11.tar.xz">Download XZ tarball</a> +<a href="releases/libav-11.tar.xz.md5">MD5</a> +<a href="releases/libav-11.tar.xz.sha1">SHA1</a> +<a href="releases/libav-11.tar.xz.asc">PGP signature</a><br /> +<a href="releases/libav-11.tar.gz">Download gzip tarball</a> +<a href="releases/libav-11.tar.gz.md5">MD5</a> +<a href="releases/libav-11.tar.gz.sha1">SHA1</a> +<a href="releases/libav-11.tar.gz.asc">PGP signature</a><br /> +<a href="releases/libav-11.changelog">Changelog</a><br /> +<a href="releases/libav-11.release">Release Notes</a> +</p> + <a name="release_10"></a><h2>Libav 10 "Eks"</h2> <p> diff --git a/src/news b/src/news index b9473c1..3427bed 100644 --- a/src/news +++ b/src/news @@ -1,5 +1,71 @@ <h1>News</h1> +<a name="11final"></a><h3>September 8, 2014</h3> +<p> +After several months of development, we are pleased to announce +the release of Libav 11. +</p> + +<p> +With this release we are trying to answer the numerous calls from our users for +shorter development cycles. From now on we will aim for approximately two major +releases per year. +</p> + +<p> +Libav 11 is API-, but not ABI-compatible with the previous major release. This +means that the code using our libraries needs to be rebuilt, but no source +changes should be required. Note however, that a number of old APIs remain +deprecated and will be dropped in the near future. All users are strongly +encouraged to update their code as soon as possible. The doc/APIchanges file in +the Libav source tree and the migration guide on the wiki should help with +migration to the new APIs. If those are not sufficient, do not hesitate to +contact us on IRC or through the user mailing list. +</p> + +<p> +One specific API issue in libavformat deserves mentioning here. When using +libavcodec for decoding or encoding and libavformat for demuxing or muxing, +the standard practice was to use the stream codec context (AVStream.codec) for +actual decoding or encoding. There are multiple problems with this pattern +(the main one is that the decoder/demuxer or encoder/muxer are not necessarily +synchronized and may overwrite each other's state), so it is now strongly +discouraged and will likely be deprecated in the future. Users should instead +allocate a separate decoding or encoding context and populate it from the +demuxing codec context (or the reverse for encoding) with the +avcodec_copy_context() function. +</p> + +<p> +The main highlights of this release include native Opus, VP7, OpenEXR, and On2 +AVC decoders, HEVC encoding through libx265, new APIs for exporting ReplayGain +and display transformation metadata and countless bug fixes. A large effort was +also expended on internal cleanups which are not very visible to our users, +but should make the codebase cleaner, safer and easier to maintain and extend. +One point worth mentioning is refactoring the large monolithic framework for +architecture-specific codec optimizations into small blocks, which reduces the +size of configurations that selectively enable or disable certain codecs. +</p> + +<p> +The avserver streaming tool, which has not been maintained for many years and +was mostly broken, was removed from the tree. It was decided that it is a +significant maintenance burden and that we do our users no service by pretending +to support it, while we in fact do not. +</p> + +<p> +See the +<a href="http://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11";>Changelog file</a></li> +for a more extensive list of significant changes. +</p> + +<p> +You can download the new release, as usual, +from <a href="download.html#release_11">our download page</a>. +</p> + + <a name="bump_56"></a><h3>August 12, 2014</h3> <p> In preparation for the upcoming Libav 11 release, we have bumped the major -- 1.9.1 _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
