From: Vignesh Venkat via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: "Ronald S. Bultje" <rsbultje@gmail.com> Cc: Vignesh Venkat <vigneshv@google.com>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/svt-av1: Set pic_type only when gop_size == 1 Date: Tue, 3 Oct 2023 15:51:29 -0700 Message-ID: <CAOJaEPLXu4hHMpVoVt1PD69QA=8=U2RmPHGqcD4M6cZ_KBhotQ@mail.gmail.com> (raw) In-Reply-To: <CAEEMt2=6fCC_UARWn5-O8Xxc7aGVp947tS1_RYSjK7epxwx8Fw@mail.gmail.com> On Thu, Sep 28, 2023 at 2:05 AM Ronald S. Bultje <rsbultje@gmail.com> wrote: > > Hi Vignesh, > > On Thu, Sep 28, 2023 at 12:14 AM Vignesh Venkatasubramanian via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote: >> >> SVT-AV1 does not support requesting keyframes at arbitrary points >> by setting pic_type to EB_AV1_KEY_PICTURE. >> >> This patch changes the following: >> * Set pic_type to EB_AV1_KEY_PICTURE only when gop_size == 1. This >> only has an effect in this case (combined with force_key_frames). >> In all other cases, setting this has no effect. >> * Set force_key_frames to 1 only when gop_size == 1, this is >> needed for pic_type request above to work. >> >> Please see the comments in >> https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/2076 for a bit more >> details. > > > Right. So, if I put my archeologist hat on, is it fair to say that what probably happened is that force_key_frames used to not exist, and pic_type worked as per above code. Then force_key_frames was required (because of quality implications), breaking the above code. And now we're removing the broken code because otherwise there's a quality penalty. Is that fair? > Hi Ronald, Yes, i believe your assessment is correct. > I agree it's probably unfair to ask you to fix the broken use case that was previously possible (I suppose this comes down to exposing an option to set force_key_frames by having the user indicate s/he'll be using pic_type). However, maybe we should not remove the dead code, because it's functionally OK. Maybe we even need a FIXME above the line where we set force_key_frames only if gop_size==1, explaining this is a bug. WDYT? > > (It feels a bit weird to remove it because it's broken, is what I'm trying to say, especially because we know how to fix it.) > Makes sense, i have kept the old code in the pic_type setting part and have updated this patch to only set force_key_frames when gop_size == 1. PTAL. > Ronald -- Vignesh _______________________________________________ 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:[~2023-10-03 22:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-27 22:13 Vignesh Venkatasubramanian via ffmpeg-devel 2023-09-28 9:04 ` Ronald S. Bultje 2023-10-03 22:51 ` Vignesh Venkat via ffmpeg-devel [this message] 2023-10-03 22:53 ` [FFmpeg-devel] [PATCH] avcodec/svt-av1: Set force_key_frames " Vignesh Venkatasubramanian via ffmpeg-devel 2023-10-04 17:23 ` Ronald S. Bultje 2023-10-04 21:05 ` Vignesh Venkat via ffmpeg-devel 2023-10-05 20:06 ` Ronald S. Bultje
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='CAOJaEPLXu4hHMpVoVt1PD69QA=8=U2RmPHGqcD4M6cZ_KBhotQ@mail.gmail.com' \ --to=ffmpeg-devel@ffmpeg.org \ --cc=rsbultje@gmail.com \ --cc=vigneshv@google.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