From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [FFmpeg-cvslog] [ffmpeg] branch master updated. 92f2f9ea5c avcodec/d3d12va_encode: D3D12 AV1 encoding support
Date: Thu, 4 Dec 2025 00:13:42 +0100
Message-ID: <aTDEJgi9-BqUyhh5@neo> (raw)
In-Reply-To: <aS7WbB71E5zPpIpp@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 1783 bytes --]
Hi Nicolas
On Tue, Dec 02, 2025 at 01:07:08PM +0100, Nicolas George via ffmpeg-devel wrote:
> Michael Niedermayer via ffmpeg-devel (HE12025-12-02):
> > > + assert((total_size + tile_group_extra_size) * 8 == bit_len);
> > this possibly should be av_assert*
>
> Without a doubt.
>
> Michael Niedermayer via ffmpeg-devel (HE12025-12-02):
> > this patch breaks decoding a video with a single image:
> >
> > this works and creates our single image video
> > ./ffmpeg -i lena.pnm /tmp/file.m2v
> >
> > this fails after the patch:
> > ./ffmpeg -i /tmp/file.m2v /tmp/file.jpg -y
>
> This is bad.
>
> Can we acknowledge that we observe a worsening in the scrutiny that
> patches receive before being pushed?
This would require some statistics work, to be sure
In this specific case i simply didnt test it quick enough, i have a script
that warns me of new assert() so i should notice eventually.
>
> Also, right now: make a pull request with a trivial patch, a
> controversial one and another trivial patch, wait a few days, push:
> nobody will notice because the PR will be named after the first,
> trivial, patch, and the push notification will be named after the last,
> trivial patch.
These are several seperate issues.
First, forgejo simply doesnt send the right details to ffmpeg-devel.
Second, our current "cvslog" reporting code is pure shit, i suggested previously to
switch this. nothing happened, ok, ill switch it, will try it with ffmpeg-web first
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Into a blind darkness they enter who follow after the Ignorance,
they as if into a greater darkness enter who devote themselves
to the Knowledge alone. -- Isha Upanishad
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-12-03 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251126095910.2B49E68EB72@ffbox0-bg.ffmpeg.org>
2025-12-02 2:28 ` Michael Niedermayer via ffmpeg-devel
2025-12-02 12:07 ` Nicolas George via ffmpeg-devel
2025-12-03 23:13 ` Michael Niedermayer via ffmpeg-devel [this message]
[not found] <20251128005559.1126A690194@ffbox0-bg.ffmpeg.org>
2025-12-02 3:36 ` [FFmpeg-devel] Re: [FFmpeg-cvslog] [ffmpeg] branch master updated. 3d96d83a0a avformat/rawdec: set framerate in codec parameters Michael Niedermayer via ffmpeg-devel
2025-12-03 23:32 ` James Almer via ffmpeg-devel
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=aTDEJgi9-BqUyhh5@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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