Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>, Lynne <dev@lynne.ee>
Subject: Re: [FFmpeg-devel] [PATCH] Announce FFmpeg 8.0
Date: Fri, 22 Aug 2025 08:34:01 -1000
Message-ID: <CABGuwE=MSYV5u5dqvj-cHGmiDNDOG6PRn-AXDr9d0eJpYdguPw@mail.gmail.com> (raw)
In-Reply-To: <79021053-bb7b-4f81-9e8a-2e967f07d394@lynne.ee>

On Fri, 22 Aug 2025, 03:05 Lynne via ffmpeg-devel, <ffmpeg-devel@ffmpeg.org>
wrote:

> On 22/08/2025 21:13, 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.
>
> Its as long and detailed as it needs to be.
>

It clearly is way too detailed.

Kieran

>
_______________________________________________
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".

  reply	other threads:[~2025-08-22 18:34 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 [this message]
2025-08-22 18:09   ` Marton Balint via ffmpeg-devel

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='CABGuwE=MSYV5u5dqvj-cHGmiDNDOG6PRn-AXDr9d0eJpYdguPw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=dev@lynne.ee \
    --cc=kieran618@googlemail.com \
    /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