From: Frank Plowman via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Frank Plowman <post@frankplowman.com>
Subject: [FFmpeg-devel] Re: [Question] Learning about VVC and wasm
Date: Thu, 13 Nov 2025 17:42:43 +0000
Message-ID: <91066f69-f95f-43c9-9b6e-33fcbd0ed944@frankplowman.com> (raw)
In-Reply-To: <CABM86pzNA3VhdtP4g47dwEpCLpkyP0iARuy0Hg5qM1zwjoMP7Q@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1806 bytes --]
On 13/11/2025 16:46, Sidd via ffmpeg-devel wrote:
> Hi, I was curious on learning more about VVC and wasm within the
> ffmpeg project and would like some guidance on where to find the docs
> and references to go through
>
> I am simply trying to get my hands dirty with a past GSoC project to
> get the feel of working on the source code (hopefully to understand it
> better)
>
> Any help on this would be much appreciated
If you have prior experience with AVC and HEVC, [1] is an overview of
what was introduced in VVC. If not, a good place to start would be with
Iain E. Richardson's "The H.264 Advanced Video Compression Standard".
He's also got a new book out, "Coding Video: A Practical Guide to HEVC
and Beyond", but I'm not sure if that’s a good introductory text or
whether it assumes some knowledge.
As far as FFmpeg’s implementation goes, probably the most notable thing
is the wavefront parallel processing (WPP) multithreading model, which
is documented to some extent at [2]. The code for the multithreading
aspect is pretty well-contained to libavcodec/vvc/thread.c so you can
get a sense of how the decoder works at a high level there. There
aren't many docs for the decoder though really: it's an implementation
of the standard. In terms of the progress on the decoder and what needs
work, its C code is in a good state but it needs more assembly written
for it, particularly on x86.
If you have any specific questions about VVC or the FFmpeg
implementation, feel free to ask me. I don't know anything about wasm.
[1] https://ieeexplore.ieee.org/document/9503377/
[2] https://archive.fosdem.org/2024/events/attachments/fosdem-2024-3538-
ffmpeg-vvc-decoder/slides/22900/VVC_decoder_in_FFmpeg_Handout-1_FP3o8rS.pdf
--
All the best,
Frank
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1091 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-13 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 16:46 [FFmpeg-devel] " Sidd via ffmpeg-devel
2025-11-13 17:42 ` Frank Plowman via ffmpeg-devel [this message]
2025-11-13 17:56 ` [FFmpeg-devel] " Sidd via ffmpeg-devel
2025-11-13 18:10 ` Frank Plowman via ffmpeg-devel
2025-11-13 18:16 ` Sidd via ffmpeg-devel
2025-11-13 18:19 ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-14 4:09 ` Zhao Zhili via ffmpeg-devel
2025-11-14 11:30 ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-14 11:59 ` Zhao Zhili 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=91066f69-f95f-43c9-9b6e-33fcbd0ed944@frankplowman.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=post@frankplowman.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