On 21/08/2025 06:47, Lynne via ffmpeg-devel wrote:
> ---
>  src/index | 42 ++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
> 
> diff --git a/src/index b/src/index
> index 52829e1..a07f4b8 100644
> --- a/src/index
> +++ b/src/index
> @@ -35,6 +35,48 @@
>      News
>    </h1>
>  
> +  <h3 id="pr8.0">August 23nd, 2025, FFmpeg 8.0 <span title="David A. Huffman">"Huffman"</span></h3>
> +  <p>
> +  A new major release, <a href="download.html#release_8.0">FFmpeg 8.0 <span title="David A. Huffman">"Huffman"</span></a>,
> +  is now available for download.
> +  Thanks to several delays, and modernization of our entire infrastructure, this release ended up
> +  being one of our largest releases to date. In short, its new features are:
> +  <ul>
> +    <li>Native decoders: <span title="Advanced Professional Video">APV</span>, ProRes RAW, RealVideo 6.0, Sanyo LD-ADPCM, and others</li>
> +    <li>VVC decoder improvements: <span title="Inter Block Copy">IBC</span>,

Should be "Intra Block Copy"

> +                                  <span title="Screen Content Coding">SSC</span>,

SCC isn't really a new tool/feature but rather a use case.  The new
SCC-specific tools are IBC and Palette (and arguably the ACT is most
relevant for SCC but I digress), so it seems strange to list SCC
separately.  Perhaps it can be removed?

> +                                  <span title="Adaptive Color Transform">ACT</span>,
> +                                  Palette Mode</li>
> +    <li>Vulkan compute-based codecs: FFv1 (encode and decode), ProRes RAW (decode only)</li>
> +    <li>Hardware accelerated decoding: Vulkan VP9, VAAPI VVC, OpenHarmony H264/5</li>
> +    <li>Hardware accelerated encoding: Vulkan AV1, OpenHarmony H264/5</li>
> +    <li>Filters: colordetect, pad_cuda, scale_d3d11, Whisper, and others</li>
> +  </ul>
> +  </p>
> +  <p>
> +  A new class of decoders and encoders based on pure Vulkan compute implementation have been added.
> +  Rather than using a custom hardware accelerator present, they are based on compute shaders, and work
> +  on any implementation of Vulkan 1.3. Decoders use the same hwaccel API and commands, so users do not
> +  need to do anything special to enable them, as enabling Vulkan decoding is sufficient to use them.
> +  Encoders, like our hardware accelerated encoders, require specifying a new encoder (ffv1_vulkan).
> +  Currently, the only codecs supported are: FFv1 (encoding and decoding) and ProRes RAW (decode only).
> +  ProRes (encode+decode) and VC-2 (encode+decode) implementations are complete and currently in review,
> +  to be merged soon and available with the next minor release.<br>
> +  Only codecs specifically designed for parallelized decoding can be implemented in such a way, with
> +  more mainstream codecs not being planned for support.<br>
> +  Depending on the hardware, these new codecs can provide very significant speedups, and open up
> +  possibilities to work with them for situations like non-linear video editors and
> +  lossless screen recording/streaming, so we are excited to learn what our downstream users can make with them.
> +  </p>
> +  <p>
> +  The project has recently started to modernize its infrastructure. Our mailing list servers have been
> +  fully upgraded, and we have recently started to accept contributions via a new forge, available on
> +  <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>, running a Forgejo instance.
> +  </p>
> +  <p>
> +    As usual, we recommend that users, distributors, and system integrators to upgrade unless they use current git master.
> +  </p>
> +
>    <h3 id="pr7.1">September 30th, 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

Thanks

-- 
Frank