From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 4/4] avcodec/ffv1enc: avoid slices larger than 360x288 if no value is specified
Date: Mon, 7 Apr 2025 01:44:12 +0200
Message-ID: <20250406234412.GL4991@pb2> (raw)
In-Reply-To: <cfa3f9f9-ef74-450b-96d1-bd40dabc8bbe@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2493 bytes --]
On Sun, Apr 06, 2025 at 08:29:42PM -0300, James Almer wrote:
> On 4/3/2025 7:50 AM, Michael Niedermayer wrote:
> > This improves speed by providing more independent things for more CPUs
> >
> > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> > ---
> > libavcodec/ffv1enc.c | 6 +++++-
> > .../ref/fate/matroska-mastering-display-metadata | 16 ++++++++--------
> > 2 files changed, 13 insertions(+), 9 deletions(-)
> >
> > diff --git a/libavcodec/ffv1enc.c b/libavcodec/ffv1enc.c
> > index ce3f8e023e5..221344794e2 100644
> > --- a/libavcodec/ffv1enc.c
> > +++ b/libavcodec/ffv1enc.c
> > @@ -581,7 +581,11 @@ int ff_ffv1_encode_determine_slices(AVCodecContext *avctx)
> > if ( ff_need_new_slices(avctx->width , s->num_h_slices, s->chroma_h_shift)
> > ||ff_need_new_slices(avctx->height, s->num_v_slices, s->chroma_v_shift))
> > continue;
> > - if (avctx->slices == s->num_h_slices * s->num_v_slices && avctx->slices <= MAX_SLICES || !avctx->slices)
> > + if (avctx->slices == s->num_h_slices * s->num_v_slices && avctx->slices <= MAX_SLICES)
> > + return 0;
> > + if (maxw*maxh > 360*288)
> > + continue;
> > + if (!avctx->slices)
> > return 0;
> > }
> > }
> > diff --git a/tests/ref/fate/matroska-mastering-display-metadata b/tests/ref/fate/matroska-mastering-display-metadata
> > index 91ce6a05584..6a2ff15b1b2 100644
> > --- a/tests/ref/fate/matroska-mastering-display-metadata
> > +++ b/tests/ref/fate/matroska-mastering-display-metadata
> > @@ -1,7 +1,7 @@
> > -ad5e3c4e338599c81ef7d0f9ae25f871 *tests/data/fate/matroska-mastering-display-metadata.matroska
> > -1669589 tests/data/fate/matroska-mastering-display-metadata.matroska
> > +c1e5e2ecf433cf05af8556debc7d4d0b *tests/data/fate/matroska-mastering-display-metadata.matroska
> > +1669773 tests/data/fate/matroska-mastering-display-metadata.matroska
> > #extradata 0: 4, 0x040901a3
> > -#extradata 3: 200, 0x506463a8
> > +#extradata 3: 202, 0xfce96279
>
> Why did extradata change? Slice dimension value changes?
yes, any reason you belive theres an issue ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The educated differ from the uneducated as much as the living from the
dead. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2025-04-06 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 10:50 [FFmpeg-devel] [PATCH 1/4] avcodec/ffv1dec: Limit size of fltmap* to pixel number Michael Niedermayer
2025-04-03 10:50 ` [FFmpeg-devel] [PATCH 2/4] avcodec/ffv1enc: Remove 65536 pixel per slice limit for remap Michael Niedermayer
2025-04-03 10:50 ` [FFmpeg-devel] [PATCH 3/4] avcodec/ffv1enc: Consider 2s x s slice configurations Michael Niedermayer
2025-04-03 10:50 ` [FFmpeg-devel] [PATCH 4/4] avcodec/ffv1enc: avoid slices larger than 360x288 if no value is specified Michael Niedermayer
2025-04-06 23:29 ` James Almer
2025-04-06 23:44 ` Michael Niedermayer [this message]
2025-04-07 1:13 ` James Almer
2025-04-07 12:35 ` Michael Niedermayer
2025-04-06 18:43 ` [FFmpeg-devel] [PATCH 1/4] avcodec/ffv1dec: Limit size of fltmap* to pixel number Michael Niedermayer
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=20250406234412.GL4991@pb2 \
--to=michael@niedermayer.cc \
--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