Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Sidd via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Sidd <sid9.karanam@gmail.com>
Subject: [FFmpeg-devel] Re: [Question] Learning about VVC and wasm
Date: Thu, 13 Nov 2025 23:46:55 +0530
Message-ID: <CABM86pznCgZj_dKQ_2JZCMEVPE5nWQY0OdJiMh8JsMQ4qszYCQ@mail.gmail.com> (raw)
In-Reply-To: <a4755ec7-8081-4b4c-af06-2a899e603bae@frankplowman.com>

Ok I misunderstood about the decoder part.

Sorry I am new to mailing lists am not sure what top-posting means, if
I have not abided by any rules I do apologize and will refrain from
doing so

On Thu, Nov 13, 2025 at 11:40 PM Frank Plowman via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> 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_______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-11-13 18:18 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
2025-11-13 18:16       ` Sidd via ffmpeg-devel [this message]
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=CABM86pznCgZj_dKQ_2JZCMEVPE5nWQY0OdJiMh8JsMQ4qszYCQ@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=sid9.karanam@gmail.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