From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] RFC: opinions on making fftools work like a library
Date: Sat, 04 Mar 2023 02:15:03 +0800
Message-ID: <tencent_ACCA9AE340FE9A359F0CAB314E00704B2D08@qq.com> (raw)
I'd like to know what do you think about making fftools work like a
library, like what ffmpeg-kit already did, but with built-in support.
https://github.com/arthenica/ffmpeg-kit
FFmpegKit is a collection of tools to use FFmpeg in Android, iOS,
Linux, macOS, tvOS, Flutter and React Native applications.
It includes scripts to build FFmpeg native libraries, a wrapper
library to run FFmpeg/FFprobe commands in applications and 8
prebuilt binary packages available at Github, Maven Central,
CocoaPods, pub and npm.
Pro:
1. It can be used for testing on mobile devices.
2. It can be used directly to do useful work.
3. It can combine some work from projects like ffmpeg-kit to extend the
funtion.
Cons:
1. It makes things complicated.
2. It's hard to support mobile devices.
Welcome to comments. I want to know is it:
a. Absolutely no! It's not fftools supported to do.
b. Doesn't matter/Don't care.
c. I like the idea, (but...)
_______________________________________________
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 reply other threads:[~2023-03-03 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 18:15 Zhao Zhili [this message]
2023-03-04 11:10 ` Lynne
2023-03-06 1:55 ` Steven Liu
2023-03-17 18:11 ` Anton Khirnov
2023-03-18 11:33 ` Neal Gompa
2023-03-19 9:01 ` Rémi Denis-Courmont
2023-03-19 18:38 ` Stefano Sabatini
2023-03-20 11:00 ` Anton Khirnov
2023-03-19 5:04 ` Zhao Zhili
2023-03-20 11:09 ` Anton Khirnov
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=tencent_ACCA9AE340FE9A359F0CAB314E00704B2D08@qq.com \
--to=quinkblack@foxmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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