PR #20609 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20609
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20609.patch
From 092f17162a356b5f51b4410d3428324c57fe2ce7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kacper=20Michaj=C5=82ow?=
Date: Thu, 25
PR #20608 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20608
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20608.patch
From 08b798dd52b743221bc3023fbff3db4fc8925156 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kacper=20Michaj=C5=82ow?=
Date: Thu, 25
On Thu, Sep 18, 2025 at 11:23:47PM -, michaelni via ffmpeg-devel wrote:
> PR #20550 opened by michaelni
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20550
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20550.patch
>
>
> >From 38d62a1a51a84e220b6dbeaefd9
Hi Gyan
On Wed, Sep 24, 2025 at 04:26:53PM +0530, Gyan Doshi via ffmpeg-devel wrote:
>
>
> On 2025-09-24 03:20 am, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi Gyan
> >
> > On Tue, Sep 16, 2025 at 10:09:14AM +0530, Gyan Doshi via ffmpeg-devel wrote:
> >
PR #20604 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20604
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20604.patch
When we parse a MakerNote, we first try to parse it as an IFD and if
that fails, we try to re-parse it as a binary blob. This is becau
PR #20622 opened by Gyan Doshi (GyanD)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20622
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20622.patch
Remove ref to libSPVRemapper as glslang removed spirv-remapper in 3a7f787
>From 57e850b523eaf3fea04ac8f1d5543e8ddac743b8 Mon Sep 17 00:
>
> - The FFmpeg community will be the decission maker about these funds.
> - The FFmpeg community will, at any time be able to change the process of
> how these decission are made by public consensus.
> - In absence of privacy concerns, decissions will be made by public
> consensus amongth the
Hi Everyone
On Tue, Sep 09, 2025 at 10:19:26AM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi Everyone
>
> The subject of funding and sponsors came up a few times recently.
>
> I think FFmpeg needs a clear guideline on this matter. To avoid
> confusion, to avoid di
On 14.10.2025 04:40, Michael Niedermayer via ffmpeg-devel wrote:
Hi Everyone
As we are now looking for sponsors, we also should look for tasks to fund.
I suggest, we first do some brainstorming and make a list, and then figure out
which
tasks we want to sponsor (or maybe someone wants to do
Hi Nicolas
On Tue, Oct 14, 2025 at 12:32:00PM +0200, Nicolas George via ffmpeg-devel wrote:
[...]
> Hi. I procrastinated replying about soliciting sponsorships, but if it
> looks like that I cannot anymore. Also, it must not be discussed in the
> dark of an obscure pull request, it ne
PR #20630 opened by Gyan Doshi (GyanD)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20630
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20630.patch
As per configure script.
>From 61a2422eeacc6a82eaae0cef5b6d4c6c21157f72 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Tue, 30 Sep 20
PR #20724 opened by Gyan Doshi (GyanD)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20724
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20724.patch
The calculation of decode error rate neglected to cast
its operands to float, thus always leading to a value of 0.
>From 85d266c0ec970b
PR #20725 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20725
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20725.patch
This option is parsed after it is used.
>From 2ddf9d2ad57e7a9a5e028e381406693225a4ab8e Mon Sep 17 00:00:00 2001
From: Niklas Haas
Dat
PR #20727 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20727
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20727.patch
>From a7d280cec74796ebd6581ad263202e4526b32e3c Mon Sep 17 00:00:00 2001
From: James Almer
Date: Sat, 18 Oct 2025 20:07:15 -0300
Subj
Hi everyone
We currently have 2 issue trackers (trac and forgejo),
Previous discussion:
"[RFC] Issue tracker" and "trac ticket statistics"
https://lists.ffmpeg.org/archives/list/[email protected]/thread/HS46O6K62MHRHJDJC45XLRMR64RE5IB7/#LMXCTJDF5SIUSX43X7YZ4347U5YHWW33
I think there are 2
On 20.10.2025 18:14, Michael Niedermayer via ffmpeg-devel wrote:
Hi everyone
We currently have 2 issue trackers (trac and forgejo),
Previous discussion:
"[RFC] Issue tracker" and "trac ticket statistics"
https://lists.ffmpeg.org/archives/list/ffmpeg-dev
PR #20729 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20729
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20729.patch
>From 30098f359a23a5016c99706e7d1f075188325841 Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Tue, 21 Oct 2025 01:24:27 +0800
Subject:
On Mon, 20 Oct 2025 19:50:33 +0200 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
Hi,
On Thursday, July 3rd, 2025 at 11:28 AM, Michael Niedermayer
wrote:
> On Thu, Jul 03, 2025 at 04:43:42PM +0200, Michael Niedermayer wrote:
>
> > Hi
> >
> > For fuzzer issues, to whom can i forward libtheora issues ?
> > (there are 2 in ossfuzz)
> >
> > David is listed in Maintainers but
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++, merely using features already present in the compilers
we target: gcc, clang
Hi Timo
On Mon, Oct 20, 2025 at 06:41:17PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 20.10.2025 18:14, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi everyone
> >
> > We currently have 2 issue trackers (trac and forgejo),
> >
> > Previous dis
On Tue, 19 Aug 2025 at 23:13, Michael Niedermayer via ffmpeg-devel
wrote:
>
> Hi all
>
> On Fri, Aug 01, 2025 at 06:16:18PM -0500, Romain Beauxis wrote:
> > Le mer. 23 juil. 2025 à 06:43, Michael Niedermayer
> > a écrit :
> > >
> > > Hi everyone
>
On Thu, 21 Aug 2025, 01:32 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> Hi
>
> Should we use a Merge or Cherry picks for integrating Pauls work ?
>
> Following are 2 plans, as we execute either we may run into issues
> and of course adapt
On Fri, Aug 8, 2025 at 2:23 PM Alan Kelly wrote:
>
>
> On Fri, Aug 8, 2025 at 2:21 PM Alan Kelly wrote:
>
>> Intel provided a microcode update to mitigate this security
>> vulnerability which has a huge negative performance impact on gather
>> instructions. This means that hscale 8to15 avx2, whi
PR #20304 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20304
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20304.patch
It makes sense to treat the presence of a frame duration and the presence
of frame rate metadata identically - because both convey effec
PR #20303 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20303
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20303.patch
See-Also: https://code.videolan.org/videolan/libplacebo/-/merge_requests/737
>From 20d6f1fdbdd95df75e4f3025e6cdc1cd92c2dda1 Mon Sep 17
Hi
Should we use a Merge or Cherry picks for integrating Pauls work ?
Following are 2 plans, as we execute either we may run into issues
and of course adapt them as needed. (or even switch)
Option M:
This would be a merge of pauls last revission before files where
switched to GPL and the
PR #20307 opened by Manuel Lauss (mlauss2)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20307
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20307.patch
>From 81464c509dfece2e6a17f5608c1b904705c8b7fd Mon Sep 17 00:00:00 2001
From: Manuel Lauss
Date: Thu, 21 Aug 2025 22:00:32 +0200
Su
Hi
On Thu, Aug 21, 2025 at 06:03:12PM +0200, Kacper Michajlow via ffmpeg-devel
wrote:
[...]
> Also on the topic of CI, I suspect we might add more jobs as needed.
> Probably depends on priorities, to not overload existing runners
> capacity.
>
> I was wondering about integratin
Hi
On Thu, Aug 21, 2025 at 12:31:46AM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 8/20/2025 9:25 PM, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi
> >
> > On Wed, Aug 20, 2025 at 05:56:27PM +0200, Timo Rothenpieler via
> > ffmpeg-devel wrote:
> >
On Thu, 21 Aug 2025, 07:53 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> Hi Kieran
>
> On Thu, Aug 21, 2025 at 06:56:14AM -1000, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
> > For the record, Paul had a note saying changes are under G
Hi Kieran
On Thu, Aug 21, 2025 at 06:56:14AM -1000, Kieran Kunhya via ffmpeg-devel wrote:
[...]
> For the record, Paul had a note saying changes are under GPL. As I
> understand you are ignoring legal advice saying this is a valid statement.
>
> Can you confirm the legal advice yo
PR #20308 opened by Daniil Cherednik (dcherednik)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20308
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20308.patch
'decode_spectrum' reads 5 bits from bitstream to get
number of encoded subbands – so 31 means all 32
subbands are encoded. Thi
On Tue, Aug 19, 2025 at 02:17:05PM +, Drew Dunne via ffmpeg-devel wrote:
[...]
> @@ -1000,6 +1005,11 @@ static const AVOption colorspace_options[] = {
> ENUM("vonkries", WP_ADAPT_VON_KRIES, "wpadapt"),
> ENUM("identity", WP_ADAPT_IDENT
PR #20312 opened by Marvin Scholz (ePirat)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20312
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20312.patch
Improves grouping and brief descriptions for AVCodecParameters.
>From 0e610267507db4b657669e6da442ed58798a8680 Mon Sep 17 00:00:00
Hi! :D
Sorry for "cross-posting"?, but I thought I'd take this up one level and
bring it before "the real devs".
Original thread = 2 msg monologue:
https://ffmpeg.org/pipermail/ffmpeg-user/2025-August/059734.html
@cehoyos:
Are you still reading me?
I'd like to talk. I am seriously believing i
PR #20311 opened by Marvin Scholz (ePirat)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20311
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20311.patch
This makes it more clear that it will be removed in a future release.
>From a6c578ef6555fdb0af0789f8fc673f9188f4b0ec Mon Sep 17 00:
Add options to insert HDR metadata into HEVC streams.
The following options are added:
- master_display: For Mastering Display Colour Volume SEI.
- max_cll: For Content Light Level Information SEI.
The filter is idempotent and will replace any existing SEI messages
of the same type. It fails when
On 21/08/2025 06:47, Lynne via ffmpeg-devel wrote:
> ---
> src/index | 42 ++
> 1 file changed, 42 insertions(+)
>
> diff --git a/src/index b/src/index
> index 52829e1..a07f4b8 100644
> --- a/src/index
> +++ b/src/index
> @@
PR #20310 opened by Marvin Scholz (ePirat)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20310
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20310.patch
The use of this protocol was already discouraged and warned about
for years with the recommendation to use the HLS demuxer instead.
On Thu, 21 Aug 2025 at 00:32, Timo Rothenpieler via ffmpeg-devel
wrote:
>
> On 8/20/2025 9:25 PM, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi
> >
> > On Wed, Aug 20, 2025 at 05:56:27PM +0200, Timo Rothenpieler via
> > ffmpeg-devel wrote:
> >> On 8/2
PR #20301 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20301
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20301.patch
>From 618dfcbc25bed20cabd394dcd00a635bac8efb39 Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Thu, 21 Aug 2025 16:40:09 +0800
Subject:
PR #20299 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20299
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20299.patch
Follow the general practice to assign the C implementation to DSP,
then the SIMD-optimized version.
>From 2796ce20d9a91193dbdca9aa980ac
PR #20300 opened by Manuel Lauss (mlauss2)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20300
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20300.patch
It's like cmd 2. Fixes the Rebel Assault 1 Intro Video "C1BLOCK.ANM"
crossfade from planet view to space view and subsequent wrong co
On Wed, 20 Aug 2025 23:43:18 +0200 Niklas Haas wrote:
> This argument works both ways.
>
> filter authors to remember to enable support
> for premultiplied alpha, even if they don't even touch the alpha plane?
I accidentally deleted a line too many here, the text was supposed to read:
Do you exp
Hi Pierre
On Wed, Aug 20, 2025 at 09:28:26AM -0700, Pierre-Anthony Lemieux via
ffmpeg-devel wrote:
> On Wed, Aug 20, 2025 at 9:24 AM Niklas Haas via ffmpeg-devel
> wrote:
> >
> > On Tue, 12 Aug 2025 08:32:39 -0700 Pierre-Anthony Lemieux
> > wrote:
> > > Qui
Hi Ayose
On Mon, Aug 18, 2025 at 07:22:56AM +0100, Ayose via ffmpeg-devel wrote:
> This is a proposal to add a new filter to FFmpeg: drawvg, to draw
> vector graphics on top of a video, using libcairo.
>
> This is my first contribution to FFmpeg, so I don't know if this is
>
PR #20295 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20295
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20295.patch
Otherwise, this may break vulkan encoding or subsequent hwupload/hwdownload
if the upstream filter did not specifically advertise this.
Hi
On Wed, Aug 20, 2025 at 10:18:20AM +0900, Lynne via ffmpeg-devel wrote:
> On 20/08/2025 06:13, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi all
> >
> > On Fri, Aug 01, 2025 at 06:16:18PM -0500, Romain Beauxis wrote:
> > > Le mer. 23 juil. 2025 à 06:43, Mich
On August 20, 2025 10:47:03 PM PDT, Lynne via ffmpeg-devel
wrote:
> +Hardware accelerated decoding: Vulkan VP9, VAAPI VVC, OpenHarmony
> H264/5
> +Hardware accelerated encoding: Vulkan AV1, OpenHarmony H264/5
> +Filters: colordetect, pad_cuda, scale_d3d11, Whisper, and o
PR #20302 opened by Peter Ross (pross)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20302
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20302.patch
>From 628d38aca7987a08586101c4f79c1a075b06353d Mon Sep 17 00:00:00 2001
From: Peter Ross
Date: Thu, 21 Aug 2025 19:58:03 +1000
Subject:
On Fri, 22 Aug 2025, Niklas Haas via ffmpeg-devel wrote:
On Thu, 21 Aug 2025 14:47:03 +0900 Lynne via ffmpeg-devel
wrote:
---
src/index | 42 ++
1 file changed, 42 insertions(+)
diff --git a/src/index b/src/index
index 52829e1..a07f4b8 100644
Hi
On Fri, Aug 22, 2025 at 05:22:54PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 22/08/2025 16:54, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi Timo
> >
> > On Fri, Aug 22, 2025 at 02:13:14PM +0200, Timo Rothenpieler via
> > ffmpeg-devel wrote:
>
On Fri, 22 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:
For arm I'm not sure if we really need qemu? All it might take is a
32bit arm chroot on aarch64? Not sure if it works like x86 though, where
a 64bit CPU can also run 32bit code.
It works pretty much like x86, yes - you don&#
On Fri, 22 Aug 2025, 03:05 Lynne via ffmpeg-devel,
wrote:
> On 22/08/2025 21:13, Niklas Haas via ffmpeg-devel wrote:
> > On Thu, 21 Aug 2025 14:47:03 +0900 Lynne via ffmpeg-devel <
> [email protected]> wrote:
> >>
PR #20318 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20318
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20318.patch
Signed-off-by: Jack Lau
>From 8f27dbfcaac61282dbe30553dbe957566dbc336d Mon Sep 17 00:00:00 2001
From: Jack Lau
Date: Sat, 23 Aug 2025
On Fri, 22 Aug 2025 17:22:54 +0200 Timo Rothenpieler via ffmpeg-devel
wrote:
> We could only run those tests on master, not on PRs.
> Nobody is impacted by them then, and we still notice breakage reasonably
> fast.
That seems reasona
On Sat, Aug 23, 2025 at 10:09:14AM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
[...]
> As a member of the CC and the GA, I agree with Niklaas that any license change
> needs a GA vote. And obviously that preempts any discussion of how to merge
> the code.
There is no license cha
PR #20324 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20324
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20324.patch
This makes the functions extensible, as future behavior change flags can be
introduced.
This is strictly speaking not an API break.
Hi Ayose
On Sat, Aug 23, 2025 at 09:22:47AM +0100, Ayose via ffmpeg-devel wrote:
> On 2025-08-20 22:58:26 +0200, Michael Niedermayer wrote:
> >
> > On Mon, Aug 18, 2025 at 07:22:56AM +0100, Ayose via ffmpeg-devel wrote:
> > > This is a proposal to add a new filter to
PR #20321 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20321
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20321.patch
Includes Exif packet side data, and starting with support in Heif.
>From 962fea2d2cb56450d5325969cb655543895d4885 Mon Sep 17 00:00:0
On Sat, 23 Aug 2025, 00:58 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> On Sat, Aug 23, 2025 at 10:09:14AM +0300, Rémi Denis-Courmont via
> ffmpeg-devel wrote:
> [...]
> > As a member of the CC and the GA, I agree with Niklaas that any license
&g
Hi
On Thu, Aug 21, 2025 at 01:32:02PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi
>
> Should we use a Merge or Cherry picks for integrating Pauls work ?
>
> Following are 2 plans, as we execute either we may run into issues
> and of course adapt them as needed. (o
On Sat, 23 Aug 2025, 21:33 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> Hi
>
> Here is the legal advice that i was given.
> The GA has the full text and that is much more detailed.
> Iam posting the relevant parts so the whole community can see
On Sun, 24 Aug 2025, 13:09 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> Hi Kieran
>
> On Sun, Aug 24, 2025 at 12:11:20PM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Sun, 24 Aug 2025, 11:56 Michael Niedermayer via ffmpeg-devel, <
PR #20326 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20326
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20326.patch
Fixes for two EXIF bugs, notably #20305 and #20291.
>From c9e86ffd2ae9b3f296b761f3d7c2f10d69a46840 Mon Sep 17 00:00:00 2001
From: Le
Hi Kieran
On Sun, Aug 24, 2025 at 07:53:45AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Sat, 23 Aug 2025, 21:33 Michael Niedermayer via ffmpeg-devel, <
> [email protected]> wrote:
>
> > Hi
> >
> > Here is the legal advice that i was given.
> &g
Hi Kieran
On Sat, Aug 23, 2025 at 11:39:37PM -0700, Kieran Kunhya via ffmpeg-devel wrote:
> >
> > The author for most of the changes of the new modules is Paul.
> > I certainly have alot of respect from Paul, he is a brilliant
> > developer and i feel a bit offended by w
Hi
On Thu, Aug 21, 2025 at 01:32:02PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi
>
> Should we use a Merge or Cherry picks for integrating Pauls work ?
>
> Following are 2 plans, as we execute either we may run into issues
> and of course adapt them as neede
On Sun, 24 Aug 2025, 11:48 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> Hi Kieran
>
> On Sat, Aug 23, 2025 at 11:39:37PM -0700, Kieran Kunhya via ffmpeg-devel
> wrote:
> > >
> > > The author for most of the changes of the new mod
On Sun, 24 Aug 2025, 11:56 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> Hi Kieran
>
> On Sun, Aug 24, 2025 at 07:53:45AM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> > On Sat, 23 Aug 2025, 21:33 Michael Niedermayer via ffmpeg-devel, <
>
> The author for most of the changes of the new modules is Paul.
> I certainly have alot of respect from Paul, he is a brilliant
> developer and i feel a bit offended by what nonsense Kieran said.
>
Paul left the project because of your attempt to ram in SDR without
community support.
This is d
Hi Kieran
On Sun, Aug 24, 2025 at 12:11:20PM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Sun, 24 Aug 2025, 11:56 Michael Niedermayer via ffmpeg-devel, <
> [email protected]> wrote:
>
> > Hi Kieran
> >
> > On Sun, Aug 24, 2025 at 07:53:45AM +010
On 8/24/2025 2:46 PM, Rémi Denis-Courmont via ffmpeg-devel wrote:
> Le sunnuntai 24. elokuuta 2025, 13.47.49 Itä-Euroopan kesäaika Michael
> Niedermayer via ffmpeg-devel a écrit :
>> Then thilo was attacked by derek claiming he stole money.
>
> Derek claimed that Thilo had so
Le mer. 20 août 2025 à 15:25, Yalda via ffmpeg-devel
a écrit :
> Thanks Romain. I am experimenting with this and trying the patches.
Awesome. Thanks so much for your time!
I have rebased the vorbis header PR against the latest `master` (would
love to call it main).
I have also pushed the n
On Tue, 8 Jul 2025 11:19:45 +
Diego de Souza via ffmpeg-devel wrote:
> Hi Andreas,
>
> Do you mean something like this?
>
> struct format_entry {
> enum AVPixelFormat format;
> char name[16];
> };
>
> static const struct
Hi Pierre
On Wed, Aug 20, 2025 at 06:38:06PM -0700, Pierre-Anthony Lemieux via
ffmpeg-devel wrote:
[...]
> I recommend that the proposed SOWs be more specific, i.e. list those forks.
>
> [ed.: I would definitely avoid forks from folks that have not shown
> interest in working with f
Hi
Here is the legal advice that i was given.
The GA has the full text and that is much more detailed.
Iam posting the relevant parts so the whole community can see it.
"a claim that there is GPLv2 code in a file of
FFmpeg origin that has the LGPLv2.1 license would be a breach of the FFmpeg's
L
PR #20322 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20322
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20322.patch
Currently, the aacencdsp checkasm tests fails for many seeds,
if the C code has been built with x87 math. This happens because
the
PR #20329 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20329
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20329.patch
Addresses issue #20328.
>From 5a95e5db18341c23584a8c13bdc134d5dcc9b05a Mon Sep 17 00:00:00 2001
From: James Almer
Date: Sun, 24 Aug
PR #20330 opened by Marton Balint (cus)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20330
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20330.patch
And a minor factorization.
>From f8e83bce6269c95fbad90f34434ceb641bf753d5 Mon Sep 17 00:00:00 2001
From: Marton Balint
Date: Sun, 24
On Mon, 7 Jul 2025 11:45:36 +0200
Diego Felix de Souza via ffmpeg-devel wrote:
> From: Diego de Souza
>
> The supported YUV pixel formats were separated between planar
> and semiplanar. This approach reduces the number of CUDA kernels
> for all pixel formats.
>
> This pat
PR #20331 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20331
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20331.patch
The project introduced API breaking changes to some of their public functions,
and given the library is relatively new, just bump the
PR #20332 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20332
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20332.patch
this patch will make whip be able to get the first
rtp seq easily and compute something sequence-based
(e.g. NACK and RTX handling)
Sign
PR #20253 opened by Manuel Lauss (mlauss2)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20253
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20253.patch
Some versions of LucasArts SANM Audio chunks have a special "IMA4" tag in their
VIMA chunks, to indicate that
a different coding sch
PR #20256 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20256
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20256.patch
See RFC 5245 Section 4.3
If an agent is a lite implementation, it MUST include an "a=ice-lite"
session-level attribute in its SDP. If an
Hi Lynne, ffmpeg-devel
the following (testcase public, not cattegorized as a security issue)
https://issues.oss-fuzz.com/issues/416134551
hits
if (!ics->num_swb || !ics->swb_offset) {
ret_fail = AVERROR_BUG;
goto fail;
}
Assertion ret != (-
PR #20262 opened by Kevin Wang (kevmo314)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20262
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20262.patch
When the flag AV_CODEC_FLAG_OUTPUT_CORRUPT or AV_CODEC_FLAG2_SHOW_ALL
is set, ignore any out of order POC's as they may still be valid
HI Kacper
On Wed, Aug 13, 2025 at 02:42:13AM +0200, Kacper Michajlow wrote:
> On Sat, 14 Jun 2025 at 22:47, Michael Niedermayer
> wrote:
> >
> > On Fri, Jun 13, 2025 at 04:06:31PM -0600, Pavel Koshevoy wrote:
> > > On Fri, Jun 13, 2025 at 2:46 PM Michael Niedermayer
> > >
> > > wrote:
> > >
> >
Hi Nicolas
On Tue, Aug 12, 2025 at 04:43:29PM +0200, Nicolas George wrote:
> Michael Niedermayer (HE12025-08-03):
> > well, you may have deep call stacks
> >
> > user_app->libavfilter->libavformat->libavcodec->decoder->jpeg_decoder->...
> >
> > and the user of the user_app needs to know what fil
Hi
The commit below affects:
~/tickets/5114/test_case.ivf
not sure its a "bug" as the file is not really having any content
but wanted to repost this as i saw this change
commit c0bf1382a757a4dd45b0c5f8ab70578e7126beca (HEAD)
Author: Lynne
AuthorDate: Thu Mar 27 04:54:54 2025 +
Commit:
PR #20266 opened by Isaac Marovitz (IsaacMarovitz)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20266
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20266.patch
packets need to be handled externally
useful for hardware decoder emulation
Co-authored-by: Joel Linn
Signed-off-by: Isaac
PR #20267 opened by Marton Balint (cus)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20267
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20267.patch
"glob_sequence" was deprecated since 2012. This also changes the default pattern
to "sequence", because "glob_sequence" was also the def
Niklas Haas via ffmpeg-devel (HE12025-08-16):
> PR #20257 opened by Niklas Haas (haasn)
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20257
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20257.patch
No objection from me to this, nor did I see anything shocking in it, but
On Tue, 19 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:
mailman2 has no good way to deal with that in a more reasonable way.
Mailman3 is already set up, and can be migrated to at a moments notice.
The only problem with it is that I really don't like the new archives.
It has wa
On 19/08/2025 08:55, Martin Storsjö via ffmpeg-devel wrote:
On Tue, 19 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:
mailman2 has no good way to deal with that in a more reasonable way.
Mailman3 is already set up, and can be migrated to at a moments notice.
The only problem with it is
PR #20284 opened by Manuel Lauss (mlauss2)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20284
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20284.patch
- Fix the old_codec1..31 implementations to check whether a pixel is inside the
visible/allocated buffer area. Should render commit
On 8/18/2025 7:08 PM, Timo Rothenpieler via ffmpeg-devel wrote:
Hi!
As you might have noticed, a bunch of big Mail-Hosters have introduced
new, even stricter, requirements. Primarily it's Microsoft, but others
seem to already have followed suit.
So we had to configure the list to sen
PR #20285 opened by Sean McGovern (sean_mcg)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20285
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20285.patch
This was disabled in da60b99a8857d5ca236f32c1799a066e0135a866 and then
accidentally re-enabled in 172b0e2e88832822632841e8e0d3794f9
Hi
On Wed, Aug 13, 2025 at 01:45:04PM +0200, Michael Niedermayer wrote:
> Hi all
>
> I intend to make 6.1.3 and 5.1.7 today or tomorrow
> we have had many security fixes so its high time to make releases of them
>
> the unfixed USAC bug should not affect it as USAC was added in 7.1
>
> So if yo
2501 - 2600 of 3425 matches
Mail list logo
