[FFmpeg-devel] Appreciation + Sharing a Project Built on FFmpeg

[FFmpeg-devel] Appreciation + Sharing a Project Built on FFmpeg

[Shashwat Verma via ffmpeg-devel]

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

[FFmpeg-devel] Re: Appreciation + Sharing a Project Built on FFmpeg

[Michael Niedermayer via ffmpeg-devel]

[-- 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