From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kanishq Verma <kanishq.verma01@gmail.com>,
Vraj Parikh <vrjparikh@gmail.com>,
Shashwat Verma <shash@aaai.solutions>,
Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: Appreciation + Sharing a Project Built on FFmpeg
Date: Thu, 27 Nov 2025 02:49:04 +0100
Message-ID: <aSeuEJ8cWgL7ZbiG@neo> (raw)
In-Reply-To: <CAKT98BDOP5MNq0cnTL-d7OKTa9a2T4FVZB_aWC0+atcmLORvbw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1932 bytes --]
Hi Shashwat,
thanks a lot for your mail and sorry for the very late reply.
messages like yours are really appreciated, even if they sometimes end up buried in busy inboxes for a while.
Best regards,
Michael
On Tue, Nov 18, 2025 at 06:08:53AM +0000, Shashwat Verma via ffmpeg-devel wrote:
> 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
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
[-- 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
prev parent reply other threads:[~2025-11-27 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 6:08 [FFmpeg-devel] " Shashwat Verma via ffmpeg-devel
2025-11-27 1:49 ` Michael Niedermayer via ffmpeg-devel [this message]
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=aSeuEJ8cWgL7ZbiG@neo \
--to=ffmpeg-devel@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