Hi Nicolas
On Thu, Oct 30, 2025 at 08:42:20PM +0100, Nicolas George via ffmpeg-devel wrote:
> Hi.
>
> Michael Niedermayer via ffmpeg-devel (HE12025-10-16):
> > I like that this would result in a steady income stream.
> > I think its a good idea, and iam happy to p
Hi Niklas
On Sat, Nov 01, 2025 at 11:38:46PM +, Niklas Haas via ffmpeg-devel wrote:
> Hi all,
>
> at VDD'25 multiple people discussed interest in the ability to improve the
> filter negotiation around hardware filters; specifically about avoiding
> the need to cons
On Fri, 31 Oct 2025, 17:06 michaelni via ffmpeg-devel, <
[email protected]> wrote:
> PR #20805 opened by michaelni
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20805
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20805.patch
>
> Fixes: out of array
rules more objective and less personal.
-- Romain
Le lun. 27 oct. 2025 à 18:13, Jean-Baptiste Kempf via ffmpeg-devel <
[email protected]> a écrit :
> Hello Everyone,
>
> Folks, you really should all calm down.
> All this drama does not help the project, nor does it give a g
PR #20820 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20820
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20820.patch
>From f5eb11a71d64660543809cbe2aa6c4d6f4aff96c Mon Sep 17 00:00:00 2001
From: James Almer
Date: Sun, 2 Nov 2025 18:14:17 -0300
Subje
PR #20824 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20824
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20824.patch
>From f0b423a688cb75fa83c064485103007425892f96 Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Sun, 2 Nov 2025 23:31:04 +0
PR #20826 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20826
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20826.patch
>From 4bdc932ec9ab9b8ece10492a96dec8b679413498 Mon Sep 17 00:00:00 2001
From: James Almer
Date: Mon, 3 Nov 2025 00:15:34 -0300
Subje
PR #20825 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20825
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20825.patch
In early code, the BUNDLE always has two stream
id "a=group:BUNDLE 0 1" even though there's only
one stream.
This patch aims to dynamica
Hi all
On Thu, Oct 16, 2025 at 06:25:00PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi everyone
>
> As we all certainly know, this ML since a few months rewrites
> all "From:" headers to "X Y via ffmpeg-devel "
> We changed this because neither m
Hi Lynne
On Tue, Oct 21, 2025 at 04:28:26AM +0200, Lynne via ffmpeg-devel wrote:
[...]
> with issues. I hardly read trac since it has no notifications at all about
> new issues.
There are multiple ways to do this
1.
theres a mailing list that contains all changes to trac including new
PR #20732 opened by Chris Hodges (platon42)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20732
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20732.patch
Fix the AV1 RTP depacketizer for instances where the OBU elements
did not have their OBU size fields removed according to the
recomm
On Tue, Oct 21, 2025 at 01:03:26PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi Lynne
>
> On Tue, Oct 21, 2025 at 04:28:26AM +0200, Lynne via ffmpeg-devel wrote:
> [...]
> > with issues. I hardly read trac since it has no notifications at all about
> > ne
PR #20734 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20734
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20734.patch
This makes the final file truly hybrid: Externally the file
is a regular, non-fragmented file, but internally, the fragmented
form
The mismatch between neon and C functions can be reproduced
using the following bitstream and command line on aarch64 devices.
wget https://streams.videolan.org/ffmpeg/incoming/replay_intra_pred_16x16.h264
./ffmpeg -cpuflags 0 -threads 1 -i replay_intra_pred_16x16.h264 -f framemd5
-y md5_ref
Jamaika1 via ffmpeg-devel (HE12025-10-18):
> PR #20716 opened by Jamaika1
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20716
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20716.patch
>
>
> >From f1276fe5217d07fda6d7dba77d0740a32d4fdc15 Mon Sep 17 00:00:00
PR #20722 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20722
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20722.patch
>From bb65f51fce43d970e94eeef12dd20d3beabb559e Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Fri, 15 Aug 2025 20:39:49 +0800
Subject:
ayosec via ffmpeg-devel (HE12025-09-07):
> PR #20458 opened by ayosec
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20458
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20458.patch
>
> This pull-request adds _drawvg_, a new filter to draw vector graphics on to
On Wed, 22 Oct 2025, Rémi Denis-Courmont via ffmpeg-devel wrote:
If you want to compile AArch64 FFmpeg for use in emulated x86 processes,
then you need a FFmpeg that exposes the same ABI as the x86 FFmpeg.
That's going to require a lot of changes throughout the code base (and I
doubt p
On Fri, 24 Oct 2025, 14:52 michaelni via ffmpeg-devel, <
[email protected]> wrote:
> PR #20746 opened by michaelni
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20746
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20746.patch
>
> Fixes: memcpy with
PR #20735 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20735
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20735.patch
profile_name is always NULL with --enable-small, which leading to
a warning message "Unknown profile bitstream".
>From 17ea0e2c5ade290e
tis 2025-10-21 klockan 04:24 +0200 skrev Lynne via ffmpeg-devel:
> On 20/10/2025 19:50, Tomas Härdin via ffmpeg-devel wrote:
> > Hi
> >
> > I'm writing this email to get a feel for how everyone feels about
> > making more use of C++ in the codebase.
tis 2025-10-21 klockan 22:15 -0500 skrev Romain Beauxis via ffmpeg-
devel:
> I understand the benefit of using higher order APIs borrowed from C++
> but,
> to fully make your case I think it'd be important to know: is it
> possible
> to use STL and avoid linking with libstc+
tis 2025-10-21 klockan 04:24 +0200 skrev Lynne via ffmpeg-devel:
> On 20/10/2025 19:50, Tomas Härdin via ffmpeg-devel wrote:
> > Hi
> >
> > I'm writing this email to get a feel for how everyone feels about
> > making more use of C++ in the codebase.
Hi
On Wed, Oct 22, 2025 at 02:09:32PM +0200, Gregor Riepl via ffmpeg-devel wrote:
> > My main motivation is to be able to use STL, which would simplify
> > string handling and memory management, and give us access to its data
> > structures. Manual memory management has its pl
On 10/20/25 13:50, Tomas Härdin via ffmpeg-devel wrote:
Hi
I'm writing this email to get a feel for how everyone feels about
making more use of C++ in the codebase. I am only proposing using C++
*internally*, and only where it makes sense. I am not suggesting a
"move" to C+
On Mon, Oct 20, 2025 at 1:51 PM Tomas Härdin via ffmpeg-devel
wrote:
>
> Hi
>
> I'm writing this email to get a feel for how everyone feels about
> making more use of C++ in the codebase. I am only proposing using C++
> *internally*, and only where it makes sense. I am n
PR #20751 opened by Shreesh Adiga (tantei3)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20751
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20751.patch
Implemented the algorithm described in the paper titled
"Fast CRC Computation for Generic Polynomials Using PCLMULQDQ Instruction"
b
PR #20851 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20851
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20851.patch
The current code only ever printed the pixel format; even when the negotiation
error was in a completely different format.
>From c171
PR #20849 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20849
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20849.patch
The MSB YUV formats were added, but the gray formats were not. Seems to have
been an oversight.
Fixes: a5be0ecbfdab24632a10c8a671484453
Michael Niedermayer via ffmpeg-devel (HE12025-10-29):
> 1. merge libavdevice and libavformat
Of course we should do that. The split into multiple libraries serves no
purpose, it only makes our work more complicated; the benefits people
think they get from it either are nonexistent or could
Hi all
i was talking with a company, who wants to sponsor FFmpeg
they asked if they would be listed in the GitHub readme.
I think we should instead add a sponsors.md and link to forgejo of it (forgejo
can render .md)
or
instead put a sponsors.html on our webpage
similar to https://www.python.org
>
>
> > And again, the more important aspect here is that Kieran was *asking*,
> not
> > publishing, what *business*, not person, sits at a given already
> published
>
> The litteral text from kieran was
>
> "Who does this address belong to?"
> and "who" normally implies a person.
>
> All above sai
Hi all
libavdevice uses teh same ABI as libavformat so extending that ABI
without major bump leads to problems
input devices and input formats use the same struct
FFInputFormat
now you cant add a new field to that because the old libavdevice
would not have it and the newer libavformat would so t
Hi
On Tue, Oct 28, 2025 at 09:48:24AM +0200, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Hello all,
>
> It has come to the attention of the FFmpeg Community Council that the owner
> of the YouTube channel @t3dotgg is being "doxxed". In consideration of the
> timel
Hi Remi
On Wed, Oct 29, 2025 at 11:31:26PM +0200, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Le keskiviikkona 29. lokakuuta 2025, 22.38.17 Itä-Euroopan normaaliaika
> Michael Niedermayer via ffmpeg-devel a écrit :
> > > When did that happen?
> >
> > Wed, 31 Jan 20
worldofmaps--- via ffmpeg-devel (HE12025-10-29):
> Since the current FFMPEG twitter account has a lot of engagement and
> has been found funny by a lot, the project should probably have two
> ffmpeg account. One corporate and one with a title like FFPMEG
> Official Satire account or
Hi Remi
On Wed, Oct 29, 2025 at 07:55:09PM +0200, Rémi Denis-Courmont via ffmpeg-devel
wrote:
>
>
> Le 29 octobre 2025 19:09:15 GMT+02:00, Michael Niedermayer via ffmpeg-devel
> a écrit :
> >Does this also apply to the case where kieran doxxed thilo ?
>
> When did t
cenzhanquan1 via ffmpeg-devel (HE12025-10-21):
> PR #20731 opened by cenzhanquan1
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20731
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20731.patch
>
> The existing avfilter_process_command and avfilter_gra
This was broken by dc7bd7c5a5 because it was depending on the behaviour
of all frames setting key_frame by default, although that was also wrong
because it didn't unset the flag for duplicate/repeated frames.
Signed-off-by: Jeremy James
---
libavcodec/qtrle.c | 4
1 file changed, 4 insertio
PR #20795 opened by Manuel Lauss (mlauss2)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20795
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20795.patch
This is another post-processing codec: it sums the r/g/b componentes
of the 4 surrounding pixels, and uses the 15bit-rgb value as an
> On Oct 31, 2025, at 03:12, Nicolas George via ffmpeg-devel
> wrote:
>
> cenzhanquan1 via ffmpeg-devel (HE12025-10-21):
>> PR #20731 opened by cenzhanquan1
>> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20731
>> Patch URL: https://code.ffmpeg.org/F
On 2025-10-31 07:01 am, Michael Niedermayer via ffmpeg-devel wrote:
Hi all
I think ive finally found a way to fix the ffmpeg-devel-owners from
being unsubscribed/disabled due to spam bounces
Lots of spam incoming to ffmpeg-devel.
Regards,
Gyan
Zhao Zhili via ffmpeg-devel (HE12025-10-31):
> Current implementation isn’t a new API, but new flags. It extends the ways to
> traverse a graph.
A new flag is a new API.
> The existing API has the capability to send commands to a specific filter, a
> certain
> type of filter,
Hi Steven
On Thu, Oct 30, 2025 at 03:28:40PM +0800, Steven Liu via ffmpeg-devel wrote:
> Michael Niedermayer via ffmpeg-devel
> 于2025年10月30日周四 09:48写道：
> >
> > Hi all
> >
> > i was talking with a company, who wants to sponsor FFmpeg
> > they asked if they
Hi all
I think ive finally found a way to fix the ffmpeg-devel-owners from
being unsubscribed/disabled due to spam bounces
Let me first explain what the problem is, then how we solved it.
The problem:
1. spam hits ffmpeg-devel-owners
2. our spam filters remove alot but not all spam
3. spam to ff
PR #20774 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20774
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20774.patch
For mv-hevc, the second layer of IDR frame can be a P slice.
long_term_rps wasn't been reset before the patch, which leading to
ff_hevc_f
Hi.
Michael Niedermayer via ffmpeg-devel (HE12025-10-16):
> I like that this would result in a steady income stream.
> I think its a good idea, and iam happy to provide companies with
> extended security support on old releases.
I think it is naïve for nerds like us to expect bein
On Sat, 8 Nov 2025, Martin Storsjö wrote:
This is used for embedding directives in COFF objects for the
linker (e.g. for dllexport).
---
Will push within a day or two, this is quite uncontroversial.
---
gas-preprocessor.pl | 1 +
1 file changed, 1 insertion(+)
Pushed this one now.
// Martin
__
PR #20885 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20885
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20885.patch
This reverts commit 7b18eafabd7cfd9e179dc28ae93911437faa.
That commit added tests that don't work on Windows, and which
also
PR #20884 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20884
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20884.patch
This whole logic is beginning to get rather annoying and I'm starting to feel
like a whole redesign is needed.
>From 2cc48b34340738f3
Hi Team!
Apologies for maybe breaking submit rules but as of now I don't know better :-)
I figured out on arm "hwdownload" is quite slow.
I turns out this is caused by imgutils.c image_copy_plane which does a memcpy
loop
for (;height > 0; height--) {
memcpy(dst, src, bytewidth);
The initial out of order check was introduced with commit
ad29f9e47cb avcodec/tiff: Restrict tag order based on specification
This changes the check to only check against tags the we process
since tags that we don't process shouldn't cause any bugs.
Example of CinemaDNG files with incorrect order
PR #20886 opened by Dmitrii Okunev (xaionaro)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20886
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20886.patch
On Android15+ MediaCodec HAL backend was switched from HIDL to AIDL.
As a result, MediaCodec operations started to hang, see:
Hey all,
after the recent social media discussion around P0 reported bugs etc. I'd
like to
contribute a few patches for a few open crash bugs in the bugtracker (and
hopefully
for the remaining BIGSLEEP bug reports, too).
I am using a coding assistant combined with a stack of ASAN + rr, and while
ffmpeg-git--- via ffmpeg-cvslog (HE12025-11-09):
> The branch, master has been updated
>via 7b18eafabd7cfd9e179dc28ae93911437faa (commit)
> from dd05022def835129028b8fc53602cea4a860496a (commit)
>
>
> - Log -
> co
PR #20882 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20882
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20882.patch
>From 9fddad48ada500acaf0c1320cee74cebb4432dae Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Mon, 10 Nov 2025 16:44:49 +0800
Subject:
Hi Kieran
On Sat, Nov 01, 2025 at 02:37:45AM +, Kieran Kunhya via ffmpeg-devel wrote:
> On Fri, 31 Oct 2025, 17:06 michaelni via ffmpeg-devel, <
> [email protected]> wrote:
>
> > PR #20805 opened by michaelni
> > URL: https://code.ffmpeg.org/FFmpeg/FFmpe
PR #20888 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20888
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20888.patch
This is an extension to WAVEFORMATEX used for some AAC streams, defined in the
Windows SDK.
Fixes issue #20887.
>From 05a6c683e9a3
hould also be done by human hand?
Cheers,
Thomas
On Mon, Nov 10, 2025, 5:04 PM Rémi Denis-Courmont via ffmpeg-devel <
[email protected]> wrote:
> Le lauantaina 8. marraskuuta 2025, 10.34.24 Itä-Euroopan normaaliaika
> Thomas
> Dullien via ffmpeg-devel a écrit :
> > Wha
On Sat, Nov 8, 2025 at 2:31 AM Michael Niedermayer via ffmpeg-devel
wrote:
>
> On Mon, Nov 03, 2025 at 12:07:24PM +0100, Niklas Haas via ffmpeg-devel wrote:
> > Hi all,
> >
> > I travelled to VDD'25 where I held two talks, one of which was directly
> > relate
On Monday, November 10th, 2025 at 10:55 PM, Stefano Sabatini via ffmpeg-devel
wrote:
>
> On Sat, Nov 8, 2025 at 2:31 AM Michael Niedermayer via ffmpeg-devel
> [email protected] wrote:
>
> > On Mon, Nov 03, 2025 at 12:07:24PM +0100, Niklas Haas via ffmpeg-devel
> &
> 在 2025年10月21日，上午1:50，Tomas Härdin via ffmpeg-devel
> 写道：
>
> Hi
>
> I'm writing this email to get a feel for how everyone feels about
> making more use of C++ in the codebase. I am only proposing using C++
> *internally*, and only where it makes sense. I am n
Zhao Zhili via ffmpeg-devel (HE12025-10-21):
> I noticed that the FFmpeg Twitter account posted about this
> discussion. I believe the discussion should remain within the mailing
> list.
Why?
> Please keep in mind that C AND C++ developers make up the largest
> portion of our user
> On Oct 21, 2025, at 22:58, Nicolas George via ffmpeg-devel
> wrote:
>
> Zhao Zhili via ffmpeg-devel (HE12025-10-21):
>> I noticed that the FFmpeg Twitter account posted about this
>> discussion. I believe the discussion should remain within the mailing
>> list
Hi all
On Mon, Oct 20, 2025 at 06:14:47PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
[...]
> after this Vote, i intend to start one about "migrating tickets."
>
> All GA members can vote, by replying to this mail on ffmpeg-devel,
> duration is 7 days
> I will t
PR #20739 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20739
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20739.patch
From ec5f76d9e28a3e79bbd8e369470749597317490c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20Storsj=C3=B6?=
Date: Thu, 23 Oct
ons 2025-10-22 klockan 14:09 +0200 skrev Gregor Riepl via ffmpeg-devel:
> > My main motivation is to be able to use STL, which would simplify
> > string handling and memory management, and give us access to its
> > data
> > structures. Manual memory management has its place
ons 2025-10-22 klockan 15:05 +0200 skrev Michael Niedermayer via
ffmpeg-devel:
> One difference that favors lower level languages is that with
> high level languages one looses sight of the cost of operations
>
> Teh closer you are to the implementation of a data structure, like
>
Hi Remi
On Thu, Oct 23, 2025 at 08:41:32PM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Le torstaina 23. lokakuuta 2025, 13.49.54 Itä-Euroopan kesäaika Michael
> Niedermayer via ffmpeg-devel a écrit :
> > I ve missed a crucial detail, which only became obvious to me now.
>
Hi Tomas
On Thu, Oct 23, 2025 at 11:49:31PM +0200, Tomas Härdin via ffmpeg-devel wrote:
> ons 2025-10-22 klockan 15:05 +0200 skrev Michael Niedermayer via
> ffmpeg-devel:
> > One difference that favors lower level languages is that with
> > high level languages one looses si
Zhao Zhili via ffmpeg-devel (HE12025-10-21):
> >> I noticed that the FFmpeg Twitter account posted about this
> >> discussion. I believe the discussion should remain within the mailing
> >> list.
> > Why?
> Using an official account to make fun of a technical
On Thu, 23 Oct 2025, Rémi Denis-Courmont via ffmpeg-devel wrote:
Le 23 octobre 2025 00:01:55 GMT+03:00, "Martin Storsjö" a
écrit :
On Wed, 22 Oct 2025, Rémi Denis-Courmont via ffmpeg-devel wrote:
If you want to compile AArch64 FFmpeg for use in emulated x86 processes, then
On Mon, Oct 20, 2025, 12:51 Tomas Härdin via ffmpeg-devel <
[email protected]> wrote:
> Hi
>
> I'm writing this email to get a feel for how everyone feels about
> making more use of C++ in the codebase. I am only proposing using C++
> *internally*, and only wher
Hi Zhao Zhili
On Tue, Oct 21, 2025 at 11:31:02PM +0800, Zhao Zhili via ffmpeg-devel wrote:
>
>
> > On Oct 21, 2025, at 22:58, Nicolas George via ffmpeg-devel
> > wrote:
> >
> > Zhao Zhili via ffmpeg-devel (HE12025-10-21):
> >> I noticed that the F
On Mon, Nov 03, 2025 at 12:07:24PM +0100, Niklas Haas via ffmpeg-devel wrote:
> Hi all,
>
> I travelled to VDD'25 where I held two talks, one of which was directly
> related to FFmpeg. I am hereby requesting reimbursement for my travel
>
On Mon, Jul 14, 2025 at 08:58:52PM +0200, Michael Niedermayer wrote:
> On Sun, Jul 13, 2025 at 07:37:06PM +0200, Andreas Rheinhardt wrote:
> > Michael Niedermayer:
> > > Fixes: signed integer overflow: 2147483565 + 128 cannot be represented in
> > > type 'int'
> > > Fixes:
> > > 428055715/cluster
PR #20856 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20856
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20856.patch
>From cfe9a10589f05b41766036871fd1c1532067e066 Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Fri, 7 Nov 2025 14:35:01 +0800
Subject:
Hi,
On Fri, 7 Nov 2025, Harish Raja Selvan wrote:
Just wanted to check if you have an estimate for when the ARM64EC related
patches for gas-preprocessor
The patch for gas-preprocessor was merged already many weeks ago. (We
agreed to go with my version of that patch.)
and the makedef scrip
0001-avformat-mpjpegdec-add-support-for-X-Timestamp-and-X-Framerate.patch
Description: Binary data
___
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
>From a9c2970ea4c06f2503ce0089291c8d0bc1b3da4f Mon Sep 17 00:00:00 2001
From: 350d <[email protected]>
Date: Sun, 9 Nov 2025 02:06:23 +0200
Subject: [PATCH] avformat/mpjpegdec: add support for X-Timestamp and
X-Framerate headers
Add support for parsing X-Timestamp and X-Framerate headers from
HTTP
>From a9c2970ea4c06f2503ce0089291c8d0bc1b3da4f Mon Sep 17 00:00:00 2001
From: 350d
Date: Sun, 9 Nov 2025 02:06:23 +0200
Subject: [PATCH] avformat/mpjpegdec: add support for X-Timestamp and
X-Framerate headers
Add support for parsing X-Timestamp and X-Framerate headers from
HTTP multipart MJPEG st
>From 31d73c6774c1ea6d621db57f26439e297cc23c3d Mon Sep 17 00:00:00 2001
From: Vladimir Sobolev
Date: Sun, 9 Nov 2025 02:28:13 +0200
Subject: [PATCH] avformat/mpjpegdec: add support for X-Timestamp and
X-Framerate headers
Add support for parsing X-Timestamp and X-Framerate headers from
HTTP multi
Hi Reaxx
On Fri, Nov 07, 2025 at 06:20:38PM +0100, Reaxx via ffmpeg-devel wrote:
> This patch fixes an out-of-bounds read in the RV60 decoder where qp can
> reach 65, exceeding the rv60_qp_to_idx[64] array bounds. The previous fix
> (61cbcaf93f) only covered intra frames. This adds vali
Hi
On Fri, Nov 07, 2025 at 10:19:27PM +0100, Reaxx via ffmpeg-devel wrote:
> Thanks for reviewing and applying the patch. Apologies for the incorrect
> commit message , I appreciate you correcting it. Thanks again
actually, can you check if my commit message is correct before i ap
Hi Reaxx
On Fri, Nov 07, 2025 at 10:49:05PM +0100, Reaxx via ffmpeg-devel wrote:
> Hi Michael,
>
> Yes, the commit message LGTM , Thank you for the detailed explanation and
> for taking the time to review this thoroughly. I appreciate your patience.
patch applied
thx
[...]
This is used for embedding directives in COFF objects for the
linker (e.g. for dllexport).
---
Will push within a day or two, this is quite uncontroversial.
---
gas-preprocessor.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/gas-preprocessor.pl b/gas-preprocessor.pl
index 1ba0563..85ccf24
PR #20865 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20865
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20865.patch
>From 22c76f902917bf18c82a8295bda883dde7ce7071 Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Sat, 8 Nov 2025 22:35:38 +0800
Subject:
Hi Vladimir
On Sun, Nov 09, 2025 at 02:38:56AM +0200, Vladimir Sobolev via ffmpeg-devel
wrote:
> >From 31d73c6774c1ea6d621db57f26439e297cc23c3d Mon Sep 17 00:00:00 2001
> From: Vladimir Sobolev
> Date: Sun, 9 Nov 2025 02:28:13 +0200
> Subject: [PATCH] avformat/mpjpegdec: ad
On Monday, November 10th, 2025 at 3:09 PM, Thilo Schunck via ffmpeg-devel
wrote:
>
>
> Hi Team!
>
> Apologies for maybe breaking submit rules but as of now I don't know better
> :-)
>
> I figured out on arm "hwdownload" is quite slow.
>
Hi
adding niklas to the CC so its not missed
but i agree the patch LGTM
On Tue, Nov 04, 2025 at 08:52:36PM +0100, Nicolas George via ffmpeg-devel wrote:
> Carl Hetherington via ffmpeg-devel (HE12025-11-03):
> > Since 3b26b782eeded9b9ab7fac013cd1a83a30d68206 it would only look at the
Hi Remi
On Mon, Nov 10, 2025 at 06:03:38PM +0200, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Le lauantaina 8. marraskuuta 2025, 10.34.24 Itä-Euroopan normaaliaika Thomas
> Dullien via ffmpeg-devel a écrit :
> > What's the best way to submit these patches? There is the bug t
On 2025-11-11 12:19 pm, Rémi Denis-Courmont via ffmpeg-devel wrote:
Le 11 novembre 2025 04:59:42 GMT+02:00, Michael Niedermayer via
ffmpeg-devel a écrit :
Hi Remi
On Mon, Nov 10, 2025 at 06:03:38PM +0200, Rémi Denis-Courmont via ffmpeg-devel
wrote:
Le lauantaina 8. marraskuuta 2025
Hi Mathias
On Wed, Nov 05, 2025 at 12:29:53PM +0100, Mathias Koehler via ffmpeg-devel
wrote:
> The initial out of order check was introduced with commit
> ad29f9e47cb avcodec/tiff: Restrict tag order based on specification
>
> This changes the check to only check against tags th
On 06/11/2025 09:40, Nicolas George via ffmpeg-devel wrote:
Rémi Denis-Courmont (HE12025-11-04):
From a technical standpoint, that seems very agreeable indeed. But at
the same time, it sounds unreasonable to expect that of a bounty
claimant.
Can you elaborate why you think that? We set the
Hello there
I want to unsubscribe from the devel@ffmpeg Mailing list
Thanks
___
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Pavel Roslyy via ffmpeg-devel (HE12025-11-04):
> The headers that are signed for DKIM can be configured. It is not
> recommended, but if needed you can remove Subject from the list of
> signed headers.
“Eh, Google, can I edit your DKIM settings to exclude the Subject
header, so that w
Timo Rothenpieler via ffmpeg-devel (HE12025-11-06):
> Couldn't we simply have any design-discussions and decisions before the
> bounty is started, so the design becomes part of what the bounty is posted
> for?
Not really, I would say. To paragraph the famous saying “no battle pla
Niklas Haas via ffmpeg-devel (HE12025-11-06):
> PR #20851 opened by Niklas Haas (haasn)
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20851
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20851.patch
>
> The current code only ever printed the pixel format
Hi James
On Tue, Nov 11, 2025 at 08:19:25PM -0300, James Almer via ffmpeg-devel wrote:
> On 11/11/2025 8:15 PM, Michael Niedermayer via ffmpeg-devel wrote:
> > Hello everyone
> >
> > We have been contacted by Microsoft.
> >
> > Whats your oppinion about putting
On Fri, Nov 7, 2025 at 6:04 AM Nicolas George via ffmpeg-devel
wrote:
>
> Pavel Roslyy via ffmpeg-devel (HE12025-11-04):
> > The headers that are signed for DKIM can be configured. It is not
> > recommended, but if needed you can remove Subject from the list of
> >
3001 - 3100 of 3432 matches
Mail list logo
