From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] libsvtav1: Add workaround for gop_size == 1
Date: Mon, 26 Jun 2023 20:53:44 -0300
Message-ID: <2b495a82-7732-f28f-0b45-af63c65e566e@gmail.com> (raw)
In-Reply-To: <CAOJaEPJmrdXgEHHHWkR_iuFLARTrxiZwrtFjt=3LP-FdYMWZow@mail.gmail.com>
On 6/26/2023 7:32 PM, Vignesh Venkat wrote:
> On Mon, Jun 26, 2023 at 3:17 PM Ronald S. Bultje <rsbultje@gmail.com> wrote:
>>
>> Hi,
>>
>> On Mon, Jun 26, 2023 at 1:47 PM Vignesh Venkatasubramanian <vigneshv-at-google.com@ffmpeg.org> wrote:
>>>
>>> In some versions of libsvtav1, setting intra_period_length to 0
>>> does not produce the intended result (i.e.) all frames produced
>>> are not keyframes.
>>>
>>> Instead handle the gop_size == 1 as a special case by setting
>>> the pic_type to EB_AV1_KEY_PICTURE when encoding each frame so
>>> that all the output frames are keyframes.
>>>
>>> SVT-AV1 Bug: https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/2076
>>>
>>> Example command: ffmpeg -f lavfi -i testsrc=duration=1:size=64x64:rate=30 -c:v libsvtav1 -g 1 -y test.webm
>>>
>>> Before: Only first frame is keyframe.
>>> After: All frames are keyframes.
>>>
>>> Signed-off-by: Vignesh Venkatasubramanian <vigneshv@google.com>
>>> ---
>>> libavcodec/libsvtav1.c | 16 +++++++++++++++-
>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>
>>
>> It feels a bit dirty to add workarounds in ffmpeg library wrappers for bugs in these libraries. Not 100% against it, but it's not particularly great.
>>
>
> Yeah I agree that it's not ideal. But minor changes like this that are
> commented/documented is okay i believe.
What are the buggy svt-av1 versions? Can this be wrapped in a
preprocessor check, so that if we bump the minimum required version in
the future and it's newer, this change can be removed/undone?
_______________________________________________
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-06-26 23:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 17:47 Vignesh Venkatasubramanian
2023-06-26 22:17 ` Ronald S. Bultje
2023-06-26 22:32 ` Vignesh Venkat
2023-06-26 23:53 ` James Almer [this message]
2023-06-27 17:55 ` Vignesh Venkat
2023-06-27 19:07 ` Ronald S. Bultje
2023-06-28 16:48 ` Vignesh Venkat
2023-06-28 23:25 ` Ronald S. Bultje
2023-06-28 23:27 ` James Almer
2023-07-13 21:13 ` Vignesh Venkat
2023-07-13 21:25 ` 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=2b495a82-7732-f28f-0b45-af63c65e566e@gmail.com \
--to=jamrial@gmail.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