From: Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Lynne <dev@lynne.ee>
Subject: Re: [FFmpeg-devel] [PATCH] Announce FFmpeg 8.0
Date: Fri, 22 Aug 2025 15:06:48 +0900
Message-ID: <c5881b89-8de2-4598-ade4-44ca87873ef2@lynne.ee> (raw)
In-Reply-To: <8701682e-5125-42ee-847b-ff497914925c@frankplowman.com>
On 22/08/2025 06:56, Frank Plowman via ffmpeg-devel wrote:
> 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?
I copied the changelog, but I guess its wrong.
Done.
_______________________________________________
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".
next prev parent reply other threads:[~2025-08-22 6:07 UTC|newest]
Thread overview: 9+ 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 [this message]
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
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=c5881b89-8de2-4598-ade4-44ca87873ef2@lynne.ee \
--to=ffmpeg-devel@ffmpeg.org \
--cc=dev@lynne.ee \
/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