From: Shashwat Verma via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org, ffmpeg-user@ffmpeg.org,
michael@niedermayer.cc, cus@passwd.hu
Cc: Kanishq Verma <kanishq.verma01@gmail.com>,
Vraj Parikh <vrjparikh@gmail.com>,
Shashwat Verma <shash@aaai.solutions>
Subject: [FFmpeg-devel] Appreciation + Sharing a Project Built on FFmpeg
Date: Tue, 18 Nov 2025 06:08:53 +0000
Message-ID: <CAKT98BDOP5MNq0cnTL-d7OKTa9a2T4FVZB_aWC0+atcmLORvbw@mail.gmail.com> (raw)
Hi FFmpeg team,
My name is Shashwat, and I wanted to reach out to express my appreciation
for the work you’ve built over the years. I’m currently building an
AI-driven video editing system where a large part of the architecture
relies on FFmpeg for composing timelines, applying transformations, and
generating final outputs. A core component of our system involves
converting user requests into dynamically generated FFmpeg commands and
filter graphs.
I’m reaching out mainly to share what I’m working on and to acknowledge
that none of it would be possible without the depth and reliability of
FFmpeg. If any of you have thoughts, guidance, or suggestions—especially
regarding best practices for building higher-level automation layers on top
of FFmpeg—I’d be grateful to hear them. I’m also happy to share more about
the architecture if that’s of interest.
Even if there’s no response, I just wanted to say thank you for the project
and the impact it has on the entire ecosystem.
Best regards,
Shashwat Verma
AAAI Solutions
shash@aaai.solutions
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next reply other threads:[~2025-11-19 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 6:08 Shashwat Verma via ffmpeg-devel [this message]
2025-11-27 1:49 ` [FFmpeg-devel] " 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=CAKT98BDOP5MNq0cnTL-d7OKTa9a2T4FVZB_aWC0+atcmLORvbw@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cus@passwd.hu \
--cc=ffmpeg-user@ffmpeg.org \
--cc=kanishq.verma01@gmail.com \
--cc=michael@niedermayer.cc \
--cc=shash@aaai.solutions \
--cc=vrjparikh@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