From: Vittorio Palmisano <vpalmisano-at-gmail.com@ffmpeg.org>
To: Zhao Zhili <quinkblack@foxmail.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Whisper audio filter
Date: Thu, 10 Jul 2025 10:43:05 +0200
Message-ID: <CADv15W8dyK36E=PP_=jRx5Bwjhv-6dAa+b4Mbrg63wV7bvKomA@mail.gmail.com> (raw)
In-Reply-To: <tencent_63CFC055282753B8EC9632CD3EA0194DA607@qq.com>
> While the filter provides great value, the accelerating pace of AI innovation raises concerns
> about its longevity. Given how rapidly newer models emerge, is there a risk of this filter
> becoming deprecated in the near term?
I think that the design of the whisper.cpp library allows us to use
updated models without changing the ffmpeg plugin code.
> If I understand correctly, whisper should be an audio to subtitle filter. However, libavfilter
> missing subtitle support currently.
Why? There are different ways to use subtitles in ffmpeg:
https://trac.ffmpeg.org/wiki/HowToBurnSubtitlesIntoVideo
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-10 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 7:23 Vittorio Palmisano
2025-07-09 13:36 ` Marvin Scholz
2025-07-09 15:24 ` Zhao Zhili
2025-07-10 8:43 ` Vittorio Palmisano [this message]
2025-07-10 9:47 ` Zhao Zhili
2025-07-10 12:41 ` Michael Niedermayer
2025-07-09 23:37 ` Michael Niedermayer
2025-07-10 8:34 ` Vittorio Palmisano
2025-07-10 10:05 ` Marvin Scholz
2025-07-10 10:20 ` Vittorio Palmisano
2025-07-10 10:25 ` Vittorio Palmisano
2025-07-10 12:20 ` Michael Niedermayer
2025-07-10 11:31 ` Michael Niedermayer
2025-07-10 12:07 ` Nicolas George
2025-07-10 12:10 ` Nicolas George
2025-07-09 23:41 ` Michael Niedermayer
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='CADv15W8dyK36E=PP_=jRx5Bwjhv-6dAa+b4Mbrg63wV7bvKomA@mail.gmail.com' \
--to=vpalmisano-at-gmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=quinkblack@foxmail.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