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 18:10:16 +0000
Message-ID: <a4755ec7-8081-4b4c-af06-2a899e603bae@frankplowman.com> (raw)
In-Reply-To: <CABM86px381tVGvGi-MSQrXdwuNDECzT-=P-dbVY+Su63vJ1AvQ@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1340 bytes --]
On 13/11/2025 17:56, Sidd via ffmpeg-devel wrote:
> Hi Frank,
>
> Thanks for the reply, it seems like there is a lot for me to cover.
>
> Regarding the assembly, since FFmpeg is known for handcrafting it, are
> there any references of help in their docs regarding this? I have gone
> through their ASM lessons and know the basics of them but am quite far
> from being good at writing it. And if I may ask, what exactly are the
> current drawbacks of the current C implementation?
>
> Thank you for taking your time to answer my questions.
>
The assembly lessons are the only "intro to SIMD" resource specifically
for FFmpeg that I know of, but I'm sure you can find more stuff by
googling. A more practical resource for x86 specifically is [1] on
x86inc.asm. I think the most important thing is to practice. Yes, the
learning curve is steep. I can't say I'm very good at writing SIMD.
I'm not quite sure what you mean by "drawbacks of the current C
implementation" -- as opposed to what? As I said, the C high-level
decoder logic is in a good state, but the decoder is quite slow and
needs more ASM to make it faster.
Nit: top-posting is discouraged on mailing lists such as ffmpeg-devel.
[1]
https://blogs.gnome.org/rbultje/2017/07/14/writing-x86-simd-using-x86inc-asm/
--
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 18:10 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 ` [FFmpeg-devel] " Frank Plowman via ffmpeg-devel
2025-11-13 17:56 ` Sidd via ffmpeg-devel
2025-11-13 18:10 ` Frank Plowman via ffmpeg-devel [this message]
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=a4755ec7-8081-4b4c-af06-2a899e603bae@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