From: James Zern <jzern-at-google.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/libaomenc: Add unmet target level warning
Date: Fri, 27 May 2022 13:41:03 -0700
Message-ID: <CABWgkX+fzB4f8exXkgBGq5Pp2=cLcX32AL-uKJ3yQTKPAufKUg@mail.gmail.com> (raw)
In-Reply-To: <CABWgkXLGpz3RrsKc-TWHWFQcSeod2BCt1icOyXoOyV0hs0_8pg@mail.gmail.com>
On Tue, May 17, 2022 at 12:45 PM James Zern <jzern@google.com> wrote:
>
> On Tue, Apr 19, 2022 at 11:20 AM Bohan Li
> <bohanli-at-google.com@ffmpeg.org> wrote:
> >
> > When target levels are set, this patch checks whether they are
> > satisfied by libaom. If not, a warning is shown. Otherwise the output
> > levels are also logged.
> >
> > This patch applies basically the same approach used for libvpx.
> >
> > Signed-off-by: Bohan Li <bohanli@google.com>
> > ---
> > libavcodec/libaomenc.c | 64 ++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 64 insertions(+)
> >
>
> lgtm.
applied. thanks for the patch.
_______________________________________________
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:[~2022-05-27 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 19:59 [FFmpeg-devel] [PATCH] Add unmet target level warning to libaom encoding Bohan Li
2022-04-19 17:03 ` [FFmpeg-devel] [PATCH] avcodec/libaomenc: Add unmet target level warning Bohan Li
2022-04-19 18:18 ` [FFmpeg-devel] [PATCH v2] " Bohan Li
2022-04-29 21:46 ` Bohan Li
2022-05-16 20:48 ` Bohan Li
2022-05-17 19:45 ` James Zern
2022-05-25 0:43 ` James Zern
2022-05-25 16:23 ` Bohan Li
2022-05-27 20:41 ` James Zern [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='CABWgkX+fzB4f8exXkgBGq5Pp2=cLcX32AL-uKJ3yQTKPAufKUg@mail.gmail.com' \
--to=jzern-at-google.com@ffmpeg.org \
--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