From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/mediacodec add vp9 encoder using mediacodec
Date: Sun, 02 Apr 2023 15:37:46 +0800
Message-ID: <tencent_3F9466DDE7CFEAB053235C740B81E6179006@qq.com> (raw)
In-Reply-To: <tencent_209A6F9FA2ABDC4E7870152D509A5D40D508@qq.com>
On Tue, 2023-03-28 at 16:43 +0800, zhilizhao(赵志立) wrote:
>
> > On Mar 27, 2023, at 23:21, Samuel Raposo Vieira Mira <samuel.mira@qt.io> wrote:
> >
> > The only encoders avaliable using mediacodec were h264 and hevc. This
> > patch adds the vp9 encoder.
> >
> > Signed-off-by: Samuel Mira <samuel.mira@qt.io<mailto:samuel.mira@qt.io>>
> > ---
> > configure | 3 ++
> > libavcodec/Makefile | 1 +
> > libavcodec/allcodecs.c | 1 +
> > libavcodec/mediacodec_wrapper.c | 24 +++++++++++++
> > libavcodec/mediacodecenc.c | 61 +++++++++++++++++++++++++++++++++
> > 5 files changed, 90 insertions(+)
>
> This patch set LGTM. There is a warning on the patch subject:
>
> > The first line of the commit message must start with a context terminated by a colon and a space, for example "lavu/opt: " or "doc: “.
>
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8627
>
> I can fix it before push. Will do more test and apply in this week.
Pushed with version bump.
_______________________________________________
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".
prev parent reply other threads:[~2023-04-02 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 15:21 Samuel Raposo Vieira Mira
2023-03-28 8:43 ` "zhilizhao(赵志立)"
2023-04-02 7:37 ` Zhao Zhili [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=tencent_3F9466DDE7CFEAB053235C740B81E6179006@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