From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Carotti, Elias" <eliascrt@amazon.it>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/libx264: enable x4->params.analyse.b_fast_pskip if mb_info is set
Date: Wed, 6 Sep 2023 01:07:48 +0200
Message-ID: <ZPe0xLwqexPuZSJM@mariano> (raw)
In-Reply-To: <1875a1e78c2a49618256568ca30e2ac1@amazon.it>
On date Tuesday 2023-09-05 12:43:35 +0000, ffmpeg-devel Mailing List wrote:
[...]
> On date Saturday 2023-09-02 09:20:08 +0000, Carotti, Elias wrote:
> > On Thu, 2023-08-31 at 19:09 +0200, Stefano Sabatini wrote:
> > >
> > <snip>
> > >
> > > > In particular why are you turning on fast_pskip silently based on
> > > > a completely different setting?
> > >
> > > The patch is fixing the regression introduced by the unconditional
> > > setting of b_fast_pskip.
> > >
> > > Now the question is if it makes sense to set mb_info without
> > > b_fast_pskip (in both case this should be probably documented).
> > >
> > > @Elias can you comment about the mb_info/b_fast_pskip use case?
> >
> > Sorry again for the delay in responding.
> > We can safely remove it altogether. It's true we don't need to set it
> > along with mb_info.
> > However, it doesn't do any harm, since fast_pskip is by default set to
> > true by libx264 and only turned off either explicitly by the user, or
> > when using the placebo preset, or when doing lossless encoding
> > (constant QP == 0.) So, I agree, let's remove these three lines.
> >
> > Thanks, updated.
>
> Ok for me
Applied, thanks.
_______________________________________________
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-09-05 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 10:01 Stefano Sabatini
2023-08-31 14:12 ` Carotti, Elias via ffmpeg-devel
2023-08-31 14:30 ` Kieran Kunhya
2023-08-31 14:38 ` Kieran Kunhya
2023-08-31 17:09 ` Stefano Sabatini
2023-09-02 9:20 ` Carotti, Elias via ffmpeg-devel
2023-09-02 15:45 ` Stefano Sabatini
2023-09-05 12:43 ` Carotti, Elias via ffmpeg-devel
2023-09-05 23:07 ` Stefano Sabatini [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=ZPe0xLwqexPuZSJM@mariano \
--to=stefasab@gmail.com \
--cc=eliascrt@amazon.it \
--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