Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Niklas Haas via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Cc: Marton Balint <cus@passwd.hu>
Subject: Re: [FFmpeg-devel] [PATCH] Announce FFmpeg 8.0
Date: Fri, 22 Aug 2025 20:09:24 +0200 (CEST)
Message-ID: <9210a366-4351-074b-a05d-096bf670b30c@passwd.hu> (raw)
In-Reply-To: <20250822141334.GB11447@haasn.xyz>



On Fri, 22 Aug 2025, Niklas Haas via ffmpeg-devel wrote:

> On Thu, 21 Aug 2025 14:47:03 +0900 Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> 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>,
>> +                                  <span title="Screen Content Coding">SSC</span>,
>> +                                  <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.
>
> Respectfully, I think this section is rather too long and technical and not
> really interesting to most users. Either describe all of the changes (of which
> you allude to, there are a lot) in detail, or none of them, but as it stands
> this feels like shining a spotlight on your contributions in particular.

I don't think this is too technical, ffmpeg release announcement is 
targeted for people with a strong tech/video interest, not general 
audience.

Also I find it quite OK if you elaborate a bit in one highlighted area of 
the release in the news entry. A news entry is not an extensive list of 
features implemented, only highlights.

So we should apply this as soon as we can.

Thanks,
Marton
_______________________________________________
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".

      parent reply	other threads:[~2025-08-22 18:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  5:47 Lynne via ffmpeg-devel
2025-08-21  6:44 ` Jacob Lifshay via ffmpeg-devel
2025-08-21 18:54   ` Lynne via ffmpeg-devel
2025-08-21 21:56 ` Frank Plowman via ffmpeg-devel
2025-08-22  6:06   ` Lynne via ffmpeg-devel
2025-08-22  6:11 ` Kieran Kunhya via ffmpeg-devel
2025-08-22 11:16 ` Gyan Doshi via ffmpeg-devel
2025-08-22 12:13 ` Niklas Haas via ffmpeg-devel
2025-08-22 13:04   ` Lynne via ffmpeg-devel
2025-08-22 18:34     ` Kieran Kunhya via ffmpeg-devel
2025-08-22 18:09   ` Marton Balint via ffmpeg-devel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9210a366-4351-074b-a05d-096bf670b30c@passwd.hu \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cus@passwd.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git