From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Guo, Yejun" <yejun.guo@intel.com>,
Raja Rathour <imraja729@gmail.com>,
Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [GSoC][RFC] GSoC 2026 Proposal (350 Hours): High-Performance LibTorch Backend Modernization
Date: Mon, 26 Jan 2026 04:03:14 +0100
Message-ID: <aXbZcnxImmLE6K6L@neo> (raw)
In-Reply-To: <CAMo0W6P6v7o6+3BMWW0eX2_bxJ3bAbsDc8NRJuzRKsbT=5jr3w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2483 bytes --]
Hi Raja, Guo
On Sun, Jan 25, 2026 at 10:30:25PM +0530, Raja Rathour via ffmpeg-devel wrote:
> *GSoC 2026 Proposal: High-Performance LibTorch Backend Modernization*
>
> *Candidate:* Raja Rathour
> *Project Type:* Large (350 Hours)
> *Mentor:* Guo Yejun
if guo agrees then someone should add this to
https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2026
we need more projects listed on the above idea page ASAP because
google will look at this and say "wtf that page is nearly empty"
> *1. Problem Statement: Bridging the Integration Gap*
>
> While the LibTorch backend logic was present in the source tree, it was
> functionally inaccessible to end-users due to a registration mismatch in
> the AVOption system. Specifically, the dnn_backend unit in
> vf_dnn_processing.c lacked the necessary constants to map the user input
> string "torch" to the internal DNN_TH backend ID. This caused the following
> failure:
>
> *The Error:*
> [Parsed_dnn_processing_0 @ 0x...] Option 'dnn_backend' not found
>
> *The Fix:*
> I have already diagnosed and resolved this by correctly registering the
> torch constant in the dnn_processing_options array and updating DnnContext
> offsets.
> *2. Current Progress & Functional Verification*
>
> I have verified the end-to-end inference pipeline using a local build
> (--enable-libtorch). The following terminal output serves as proof of
> concept, showing successful 25-frame inference at 14.8x speed using the new
> LibTorch integration:
>
> *# Verified Command Line Proof*
>
> ./ffmpeg -f lavfi -i testsrc=duration=1 -vf
> "dnn_processing=model=model.pt:dnn_backend=torch" -f null -
> ...
> Stream mapping: Stream #0:0 -> #0:0 (wrapped_avframe -> wrapped_avframe)
> frame= 25 fps=0.0 time=00:00:01.00 speed=14.8x
>
> This confirms that the "plumbing" between FFmpeg's filtergraph and the
> LibTorch engine (using at::from_blob for memory wrapping) is fully
> operational.
> [image: image.png]
>
>
> *3. 350-Hour Technical Roadmap (12-Week Plan)*
I do like the idea of improving libtorch support
I have to admit i probably never used FFmpeg with libtorch
but i used libtorch directly in another project i wrote.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Take away the freedom of one citizen and you will be jailed, take away
the freedom of all citizens and you will be congratulated by your peers
in Parliament.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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:[~2026-01-26 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 17:00 [FFmpeg-devel] " Raja Rathour via ffmpeg-devel
2026-01-26 3:03 ` Michael Niedermayer via ffmpeg-devel [this message]
2026-01-26 10:46 ` [FFmpeg-devel] " Raja Rathour via ffmpeg-devel
2026-01-26 23:58 ` Michael Niedermayer 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=aXbZcnxImmLE6K6L@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=imraja729@gmail.com \
--cc=michael@niedermayer.cc \
--cc=yejun.guo@intel.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