Message ID | 20240930074306.719956-1-dev@lynne.ee |
---|---|
State | New |
Headers | show |
Series | [FFmpeg-devel] web/index: add release notes for version 7.1 | expand |
Context | Check | Description |
---|---|---|
yinshiyou/configure_loongarch64 | warning | Failed to apply patch |
andriy/configure_x86 | warning | Failed to apply patch |
Quoting Lynne via ffmpeg-devel (2024-09-30 09:42:58) > --- > src/index | 37 +++++++++++++++++++++++++++++++++++++ > 1 file changed, 37 insertions(+) > > diff --git a/src/index b/src/index > index fdf7ebb..76c8b32 100644 > --- a/src/index > +++ b/src/index > @@ -35,6 +35,43 @@ > News > </h1> > > + <h3 id="pr7.1">October 1st, 2024, FFmpeg 7.1 <span title="Rózsa Péter">"Péter"</span></h3> > + <p> > + <a href="download.html#release_7.1">FFmpeg 7.1 "Péter"</a>, a new > + major release, is now available! This release is API and ABI backward compatible with 7.0 > A full list of changes can be found in the release > + <a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/refs/heads/release/7.1:/Changelog">changelog</a>. > + </p> > + <p> > + The more important highlights of the release are that the VVC decoder, merged as experimental in version 7.0, > + has had enough time to mature and be optimized enough to be declared as stable. The coded is starting to gain ^ c > + traction with broadcast standardization bodies.<br> > + Support has been added for a native AAC USAC (part of the xHE-AAC coding system) decoder, with the format starting "Support has been added for a ... decoder" sounds strange, should be either "Support has been added for ... decoding" or "Our decoder now supports ..." > + to be adopted by streaming websites, due to its extensive volume normalization metadata.<br> > + MV-HEVC is now able to be natively decoded. This is a stereoscopic coding tool that begun to be shipped and generated "able to be decoded" sounds weird to me as well, I'd say "MV-HEVC decoding is now supported". > + by recent phones and VR headsets.<br> > + LC-EVC decoding, an enhancement metadata layer to attempt to improve the quality of codecs, is now supported via an > + external library.<br> > + </p> > + <p> > + Support for Vulkan encoding, with H264 and HEVC was merged. ^ implementations? > This finally completes the loop with a consumer for Vulkan frames > being output by filters, decoders and users. This finally allows fully Vulkan-based decode-filter-encode pipelines. (it's not really a loop) > The encoders have feature-parity with their VAAPI > + implementation counterparts. Khronos has announced that support for AV1 encoding is also coming soon to Vulkan, > + and FFmpeg is aiming to have day-one support. > + </p> > + <p> > + As well as important features, this release has had a lot of work done internally. By far the standout highlight here ^^^^^^^^^^ In addition to the above?
On 30/09/2024 11:08, Anton Khirnov wrote: > Quoting Lynne via ffmpeg-devel (2024-09-30 09:42:58) >> --- >> src/index | 37 +++++++++++++++++++++++++++++++++++++ >> 1 file changed, 37 insertions(+) >> >> diff --git a/src/index b/src/index >> index fdf7ebb..76c8b32 100644 >> --- a/src/index >> +++ b/src/index >> @@ -35,6 +35,43 @@ >> News >> </h1> >> >> + <h3 id="pr7.1">October 1st, 2024, FFmpeg 7.1 <span title="Rózsa Péter">"Péter"</span></h3> >> + <p> >> + <a href="download.html#release_7.1">FFmpeg 7.1 "Péter"</a>, a new >> + major release, is now available! > > This release is API and ABI backward compatible with 7.0 Changed it to a minor release. >> A full list of changes can be found in the release >> + <a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/refs/heads/release/7.1:/Changelog">changelog</a>. >> + </p> >> + <p> >> + The more important highlights of the release are that the VVC decoder, merged as experimental in version 7.0, >> + has had enough time to mature and be optimized enough to be declared as stable. The coded is starting to gain > ^ > c > >> + traction with broadcast standardization bodies.<br> >> + Support has been added for a native AAC USAC (part of the xHE-AAC coding system) decoder, with the format starting > > "Support has been added for a ... decoder" sounds strange, should be either > "Support has been added for ... decoding" > or > "Our decoder now supports ..." > >> + to be adopted by streaming websites, due to its extensive volume normalization metadata.<br> >> + MV-HEVC is now able to be natively decoded. This is a stereoscopic coding tool that begun to be shipped and generated > > "able to be decoded" sounds weird to me as well, I'd say "MV-HEVC > decoding is now supported". Sure, went with your suggestion. > >> + by recent phones and VR headsets.<br> >> + LC-EVC decoding, an enhancement metadata layer to attempt to improve the quality of codecs, is now supported via an >> + external library.<br> >> + </p> >> + <p> >> + Support for Vulkan encoding, with H264 and HEVC was merged. > ^ > implementations? > >> This finally completes the loop with a consumer for Vulkan frames >> being output by filters, decoders and users. > > This finally allows fully Vulkan-based decode-filter-encode pipelines. > (it's not really a loop) Went with: "This finally allows fully Vulkan-based decode-filter-encode pipelines, by having a sink for Vulkan frames, other than downloading or displaying them." >> The encoders have feature-parity with their VAAPI >> + implementation counterparts. Khronos has announced that support for AV1 encoding is also coming soon to Vulkan, >> + and FFmpeg is aiming to have day-one support. >> + </p> >> + <p> >> + As well as important features, this release has had a lot of work done internally. By far the standout highlight here > ^^^^^^^^^^ > In addition to the above? > Went with "In addition to the above, this release has had a lot of important internal work done." Attached v2.
On 30/09/2024 11:34, Lynne via ffmpeg-devel wrote: > On 30/09/2024 11:08, Anton Khirnov wrote: >> Quoting Lynne via ffmpeg-devel (2024-09-30 09:42:58) >>> --- >>> src/index | 37 +++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 37 insertions(+) >>> >>> diff --git a/src/index b/src/index >>> index fdf7ebb..76c8b32 100644 >>> --- a/src/index >>> +++ b/src/index >>> @@ -35,6 +35,43 @@ >>> News >>> </h1> >>> + <h3 id="pr7.1">October 1st, 2024, FFmpeg 7.1 <span title="Rózsa >>> Péter">"Péter"</span></h3> >>> + <p> >>> + <a href="download.html#release_7.1">FFmpeg 7.1 "Péter"</a>, a new >>> + major release, is now available! >> >> This release is API and ABI backward compatible with 7.0 > > Changed it to a minor release. > >>> A full list of changes can be found in the release >>> + <a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/refs/ >>> heads/release/7.1:/Changelog">changelog</a>. >>> + </p> >>> + <p> >>> + The more important highlights of the release are that the VVC >>> decoder, merged as experimental in version 7.0, >>> + has had enough time to mature and be optimized enough to be >>> declared as stable. The coded is starting to gain >> ^ >> c >> >>> + traction with broadcast standardization bodies.<br> >>> + Support has been added for a native AAC USAC (part of the xHE- >>> AAC coding system) decoder, with the format starting >> >> "Support has been added for a ... decoder" sounds strange, should be >> either >> "Support has been added for ... decoding" >> or >> "Our decoder now supports ..." >> >>> + to be adopted by streaming websites, due to its extensive volume >>> normalization metadata.<br> >>> + MV-HEVC is now able to be natively decoded. This is a >>> stereoscopic coding tool that begun to be shipped and generated >> >> "able to be decoded" sounds weird to me as well, I'd say "MV-HEVC >> decoding is now supported". > > Sure, went with your suggestion. > >> >>> + by recent phones and VR headsets.<br> >>> + LC-EVC decoding, an enhancement metadata layer to attempt to >>> improve the quality of codecs, is now supported via an >>> + external library.<br> >>> + </p> >>> + <p> >>> + Support for Vulkan encoding, with H264 and HEVC was merged. >> ^ >> implementations? >> >>> This finally completes the loop with a consumer for Vulkan frames >>> being output by filters, decoders and users. >> >> This finally allows fully Vulkan-based decode-filter-encode pipelines. >> (it's not really a loop) > > Went with: > "This finally allows fully Vulkan-based decode-filter-encode pipelines, > by having a sink for Vulkan frames, other than downloading or displaying > them." > >>> The encoders have feature-parity with their VAAPI >>> + implementation counterparts. Khronos has announced that support >>> for AV1 encoding is also coming soon to Vulkan, >>> + and FFmpeg is aiming to have day-one support. >>> + </p> >>> + <p> >>> + As well as important features, this release has had a lot of >>> work done internally. By far the standout highlight here >> ^^^^^^^^^^ >> In addition to the above? >> > > Went with "In addition to the above, this release has had a lot of > important internal work done." > > Attached v2. > > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". Thanks for the review. I've pushed it with the changes. Announcements can be made now.
diff --git a/src/index b/src/index index fdf7ebb..76c8b32 100644 --- a/src/index +++ b/src/index @@ -35,6 +35,43 @@ News </h1> + <h3 id="pr7.1">October 1st, 2024, FFmpeg 7.1 <span title="Rózsa Péter">"Péter"</span></h3> + <p> + <a href="download.html#release_7.1">FFmpeg 7.1 "Péter"</a>, a new + major release, is now available! A full list of changes can be found in the release + <a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/refs/heads/release/7.1:/Changelog">changelog</a>. + </p> + <p> + The more important highlights of the release are that the VVC decoder, merged as experimental in version 7.0, + has had enough time to mature and be optimized enough to be declared as stable. The coded is starting to gain + traction with broadcast standardization bodies.<br> + Support has been added for a native AAC USAC (part of the xHE-AAC coding system) decoder, with the format starting + to be adopted by streaming websites, due to its extensive volume normalization metadata.<br> + MV-HEVC is now able to be natively decoded. This is a stereoscopic coding tool that begun to be shipped and generated + by recent phones and VR headsets.<br> + LC-EVC decoding, an enhancement metadata layer to attempt to improve the quality of codecs, is now supported via an + external library.<br> + </p> + <p> + Support for Vulkan encoding, with H264 and HEVC was merged. This finally completes the loop with a consumer for + Vulkan frames being output by filters, decoders and users. The encoders have feature-parity with their VAAPI + implementation counterparts. Khronos has announced that support for AV1 encoding is also coming soon to Vulkan, + and FFmpeg is aiming to have day-one support. + </p> + <p> + As well as important features, this release has had a lot of work done internally. By far the standout highlight here + are the improvements made for full-range images. Previously, color range data had two paths, no negotiation, + and was unreliably forwarded to filters, encoders, muxers. Work on cleaning the system up started more than 10 + years ago, however this stalled due to how fragile the system was, and that breaking behaviour would be unacceptable. + The new system fixes this, so now color range is forwarded correctly and consistently everywhere needed, and also + laid the path for more advanced forms of negotiation.<br> + Cropping metadata is now supported with Matroska and MP4 formats. This metadata is important not only for archival, + but also with AV1, as hardware encoders require its signalling due to the codec not natively supporting one. + </p> + <p> + As usual, we recommend that users, distributors, and system integrators to upgrade unless they use current git master. + </p> + <h3 id="coverity">September 11th, 2024, Coverity</h3> <p> The number of issues FFmpeg has in <a href="https://scan.coverity.com/projects/ffmpeg">Coverity (a static analyzer)</a> is now lower than it has been since 2016.