Hi everyone
I intend to make 7.1.2 soon (days)
if you want something included or backported, do it soon
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Freedom in capitalist society always remains about the same as it was in
ancient Greek republics: Freedom for
Hi Martin
On Tue, Sep 16, 2025 at 10:54:19PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote:
>
> > On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel
> > wrote:
> > > On Tue, 16 Se
On Mon, Sep 15, 2025 at 02:57:53PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi
>
> On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via ffmpeg-devel
> wrote:
> > On 15/09/2025 13:09, Michael Niedermayer via ffmpeg-devel wrote:
> [...]
> > > I
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 disagreements and to ensure community members
can point potential sponsors in an aggreed direction without hesitation.
My suggestion w
Hi Alexander
On Tue, Sep 16, 2025 at 03:59:38PM +0200, Alexander Strasser via ffmpeg-devel
wrote:
> On 2025-09-16 10:49 +0200, Michael Niedermayer via ffmpeg-devel wrote:
> >
> [...]
> >
> > * If we keep forgejo we will likely transition our issue tracker ticket
Hi Martin
On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> On Tue, 16 Sep 2025, Michael Niedermayer wrote:
>
> > Hi all
> >
> > 2 months ago we voted on testing Forgejo vs Gitlab, we picked and tested
> > Forgejo. And as said in t
Hi
On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 15/09/2025 13:09, Michael Niedermayer via ffmpeg-devel wrote:
[...]
> > Ideas, Comments ?
>
> I do think trac is a dead end software, and we want to eventually retire it.
btw, anyone kno
Hi all
2 months ago we voted on testing Forgejo vs Gitlab, we picked and tested
Forgejo. And as said in that vote, (and surprisingly, i have not forgotten it)
heres the "after testing" discussion and vote
do we want to keep Forgejo or switch back to the ML workflow
(or something else)
F. keep Fo
Hi Timo
On Mon, Sep 15, 2025 at 10:20:30PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> These are the hosting costs for code.ffmpeg.org so far:
>
> Each months bill is for the previous month. So the February one is for what
> was used in January, and so on.
> The left side is server cost,
On Mon, Sep 15, 2025 at 08:35:21PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 9/15/2025 8:26 PM, Michael Niedermayer via ffmpeg-devel wrote:
[...]
>
> >
> > >
> > > Plus the multi-account issue you mentioned.
> >
> > redmine can accept OAu
Hi Gyan
On Tue, Sep 16, 2025 at 12:39:37AM +0530, Gyan Doshi via ffmpeg-devel wrote:
> It's best to have a single issue tracker.
+1
> It's best for the issue tracker to be integrated with the code workflow.
+1
>
> What can happen is that if an existing open trac issue is taken up for
> act
Hi Timo
On Mon, Sep 15, 2025 at 07:19:17PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 9/15/2025 2:57 PM, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi
> >
> > On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via
> > ffmpeg-devel wrote
Hi
On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
[...]
>
> I thought Forgejo had votes as well, but I can't find them anymore, so I
> might be misremembering that.
One can add thumbs up and down to individual messages of an issue but they
are not shown in
On Mon, Sep 15, 2025 at 01:09:47PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi all
>
> ATM the bug reporting guidlines point to trac
> and https://trac.ffmpeg.org/newticket redirects to forgejo
>
> So if a user found a bug, now what does she do?
> 1. First she
, Comments ?
thx
On Sun, Sep 14, 2025 at 11:23:17PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi everyone
>
> trac supports, custom search queries, customly formated results
>
> People can vote on tickets, we can have custom ticket states and custom
> workflow on
Hi everyone
trac supports, custom search queries, customly formated results
People can vote on tickets, we can have custom ticket states and custom
workflow on tickets.
Are these things possible in forgejo ?
For example, what we use in trac:
Open Tickets ordered by number of votes colored base
On Tue, Sep 09, 2025 at 02:40:50PM +0200, Jerome Martinez via ffmpeg-devel
wrote:
> timecode.c | 104
> +
> timecode.h | 22
> 2 files changed, 126 insertions(+)
> 8969dd4cc3cc1d77acde18a6eae065e9413757b2
> 0004-32-bit
Hi Jerome
On Tue, Sep 09, 2025 at 02:41:39PM +0200, Jerome Martinez via ffmpeg-devel
wrote:
> matroska.h|1 +
> matroskadec.c | 34 ++
> 2 files changed, 35 insertions(+)
> 83b42253e7a0ca4f220f658b0671e4056e719592
> 0006-matroskadec-read-timecode-in-Bl
On Tue, Sep 09, 2025 at 02:38:53PM +0200, Jerome Martinez via ffmpeg-devel
wrote:
> libavformat/matroskaenc.c |8 +++
> tests/ref/lavf/mka|4 +--
> tests/ref/lavf/mkv|4 +--
> tests/ref/lavf/mkv_attachment |4 +--
> tests/ref/seek/lavf-mkv |
Hi Gyan
On Fri, Sep 12, 2025 at 12:11:56PM +0530, Gyan Doshi via ffmpeg-devel wrote:
> Let's put aside the extreme cases for now. What is the concrete definition
> of the community in normal cases?
In the normal case, we would reach a consensus or we would agree that the
general
assembly would m
Hi remi
On Tue, Sep 09, 2025 at 07:29:02PM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Le tiistaina 9. syyskuuta 2025, 15.10.37 Itä-Euroopan kesäaika Michael
> Niedermayer via ffmpeg-devel a écrit :
> > > 2) A legal entity with clear oversight rules that sponsor
Hi Gyan
On Thu, Sep 11, 2025 at 01:41:24PM +0530, Gyan Doshi via ffmpeg-devel wrote:
>
>
> On 2025-09-11 02:22 am, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi Kieran
> >
> > On Wed, Sep 10, 2025 at 06:21:56PM +0200, Kieran Kunhya via ffmpeg-devel
> >
Hi Kieran
On Wed, Sep 10, 2025 at 06:21:56PM +0200, Kieran Kunhya via ffmpeg-devel wrote:
> On Wed, 10 Sept 2025, 17:49 Michael Niedermayer via ffmpeg-devel, <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> > Hi remi
> >
> > On Tue, Sep 09, 2025 at 07:29:02PM +0300, R
Hi Remi
On Tue, Sep 09, 2025 at 02:49:39PM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Hi,
>
> Le 9 septembre 2025 11:19:26 GMT+03:00, Michael Niedermayer via ffmpeg-devel
> a écrit :
> >Hi Everyone
> >
> >The subject of funding and sponsors came up
Hi Kieran
On Tue, Sep 09, 2025 at 10:02:22AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Tue, 9 Sept 2025, 09:19 Michael Niedermayer via ffmpeg-devel, <
[...]
> My suggestion would be:
> > - The FFmpeg project should actively seek sponsors and funding.
> > - The mo
On Thu, Sep 04, 2025 at 07:43:36PM +0800, 岑湛权 via ffmpeg-devel wrote:
> From: zhanquan cen
>
> Fix two -Wenum-conversion warnings:
> - Implicit conversion from AVPacketSideDataType to AVFrameSideDataType
> - Implicit conversion from AVFrameSideDataType to AVPacketSideDataType
>
> The packet side
Hi Derek
On Wed, Sep 03, 2025 at 02:19:28PM +0100, Derek Buitenhuis via ffmpeg-devel
wrote:
> On 9/3/2025 2:06 PM, Michael Niedermayer via ffmpeg-devel wrote:
> > Applied after discussion in the General Assembly.
> > There where no objections.
[...]
> Moving it to a priva
Hi Derek
On Wed, Sep 03, 2025 at 02:19:28PM +0100, Derek Buitenhuis via ffmpeg-devel
wrote:
> On 9/3/2025 2:06 PM, Michael Niedermayer via ffmpeg-devel wrote:
> > Applied after discussion in the General Assembly.
> > There where no objections.
>
> There were multiple ob
Hi everyone
On Fri, Aug 29, 2025 at 05:21:00PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> See: https://fundingjson.org/
> See: https://floss.fund/
>
> Based on: https://www.python.org/funding.json and the example from
> fundingjson.org
>
> It is put in the web
On Fri, Aug 29, 2025 at 05:21:00PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
> See: https://fundingjson.org/
> See: https://floss.fund/
>
> Based on: https://www.python.org/funding.json and the example from
> fundingjson.org
>
> It is put in the web repository so
On Wed, Aug 27, 2025 at 01:06:42PM +0200, Maryla Ustarroz via ffmpeg-devel
wrote:
> On Mon, Aug 11, 2025 at 2:01 PM Maryla Ustarroz wrote:
> >
> > On Mon, Aug 11, 2025 at 1:57 PM Maryla Ustarroz-Calonge
> > wrote:
> > >
> > > Signed-off-by: Maryla Ustarroz-Calonge
> > > ---
> > > tests/Makefil
Hi Patrick
On Fri, Aug 29, 2025 at 02:58:16AM +0800, Patrick Wang via ffmpeg-devel wrote:
> d119ae2fd82a494d9430ff4d4fc262961a68c598 removed the loop-breaking condition
> received_sigterm.
> Thus, signals no longer gracefully shutdown ffmpeg.
>
> Fixes: #10834
>
> Signed-off-by: Patrick Wang
>
On Sat, Aug 30, 2025 at 04:27:25PM -0700, Spencer Alves via ffmpeg-devel wrote:
> The 'smpl' chunk is used for sampling music synthesizers, and includes
> things like the pitch of the sample and how to loop it. This exposes the
> loop points as "loop_start" and "loop_end" metadata, that the brstm,
On Tue, Sep 02, 2025 at 10:39:12AM -0300, James Almer via ffmpeg-devel wrote:
> On 9/2/2025 10:30 AM, Michael Niedermayer via ffmpeg-devel wrote:
> > On Wed, Aug 27, 2025 at 01:06:42PM +0200, Maryla Ustarroz via ffmpeg-devel
> > wrote:
> > > On Mon, Aug 11, 2025 at 2:01 P
On Fri, Aug 29, 2025 at 08:19:39PM +, Zsolt Vadász via ffmpeg-devel wrote:
>
> This patch series makes vf_minterpolate approximately 5% faster,
> according to my tests, which I performed on a Ryzen 7 PRO 4750U,
> compiling with GCC 15.2.1, using -O2.
>
> Zsolt Vadasz (2):
> libavfilter/vf_m
Hi Remi
On Sun, Aug 31, 2025 at 11:53:01AM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
[...]
> > And the General Assembly can change the person(s) who control the wallet
> > For example the GA could simply choose any people it wants
> > these people then could make a transaction. for exam
On Tue, Aug 12, 2025 at 12:35:15PM +0200, Nicolas Gaullier wrote:
> v4 (Michael): first patch splitted: now 3 patches, code is unchanged.
> v3 (James): complete overhaul of the commit message of the first
> patch, code is unchanged. Second patch is fully unchanged ("should be ok").
> v2 (Baptiste):
Hi Remi
On Fri, Aug 29, 2025 at 08:35:54PM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
[...]
> >+},{
> >+"guid": "ffmpeg-crypto",
> >+"type": "other",
> >+"address": "0x2f3900e7064eE63D30d749971265858612AA7139",
> >+"description": "US
See: https://fundingjson.org/
See: https://floss.fund/
Based on: https://www.python.org/funding.json and the example from
fundingjson.org
It is put in the web repository so its all on the plain ffmpeg.org domain
otherwise extra files are needed
---
htdocs/funding.json | 126 +++
mplying that a funding.json was pushed without consent is unacceptable
The patch was on the mailing list,
Do 19 Jun 2025 21:12:23 CEST Michael Niedermayer
[FFmpeg-devel] [PATCH] Add FUNDING.json
The General Assembly was informed about the potential donation from
the etherum foundation, th
See: https://fundingjson.org/
See: https://floss.fund/
Based on: https://www.python.org/funding.json and the example from
fundingjson.org
It is put in the web repository so its all on the plain ffmpeg.org domain
otherwise extra files are needed
---
htdocs/funding.json | 131 +++
Hi Remi
On Sun, Aug 24, 2025 at 04:46:09PM +0300, 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 :
[...]
> > And you simply posted thilos street address in public.
>
Hi Derek
On Sun, Aug 24, 2025 at 03:33:32PM +0100, Derek Buitenhuis via ffmpeg-devel
wrote:
> 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 :
Hi all
On Sun, Aug 24, 2025 at 12:59:29PM +0200, Michael Niedermayer via ffmpeg-devel
wrote:
[...]
> > Option M:
> > This would be a merge of pauls last revission before files where
> > switched to GPL and the command line tool to AGPL
[...]
> > Option C:
&g
Hi
We seem not to have basic x86-32 / 64 linux clients covering the releases
iam running clients for many obscure archs like sh4 and alpha
should i add x86-32 and 64 linux
See for example: https://fatebeta.ffmpeg.org/v5.1
theres my ming32 x86-32/64 but no linux
that said, the hidden reason for
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, <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> > Hi Kieran
> >
> > On Sun, Aug 24, 2025 at 07:53:45AM +010
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
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, <
> ffmpeg-devel@ffmpeg.org> 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 what nonsense Kieran said.
>
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 ffmpeg, or at
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
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
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, 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 change.
thx
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:
>
Hi Timo
On Fri, Aug 22, 2025 at 02:13:14PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
[...]
> But then again, GitHub/MS gives us 20 parallel runners for free, and we can
> freely pick if they're running on x86_64 or aarch64, Linux, Windows or even
> OSX.
> As long as they do that, we only n
On Fri, Aug 22, 2025 at 02:13:14PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 22/08/2025 07:00, Kieran Kunhya via ffmpeg-devel wrote:
> > On Thu, 21 Aug 2025, 11:33 Michael Niedermayer via ffmpeg-devel, <
> > ffmpeg-devel@ffmpeg.org> wrote:
> >
> >
Hi Niklas
On Fri, Aug 22, 2025 at 02:29:56PM +0200, Niklas Haas via ffmpeg-devel wrote:
> On Thu, 21 Aug 2025 13:32:02 +0200 Michael Niedermayer via ffmpeg-devel
> wrote:
> > Hi
> >
> > Should we use a Merge or Cherry picks for integrating Pauls work ?
> >
&g
Hi Niklas
On Fri, Aug 22, 2025 at 02:29:56PM +0200, Niklas Haas via ffmpeg-devel wrote:
> On Thu, 21 Aug 2025 13:32:02 +0200 Michael Niedermayer via ffmpeg-devel
> wrote:
> > Hi
> >
> > Should we use a Merge or Cherry picks for integrating Pauls work ?
> >
&g
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_IDENTITY, "wpadapt"),
>
> +{ "clamptrc",
Traili
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:
> >
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 integrating CIFuzz. Which ba
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 you were given and
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
my initial reservations, I decided to also apply with another
> > continuation of the libswscale project. Just letting you know as a heads up
> > that I will add my proposal to the wiki shortly.
> >
> > How much more is currently needed to meet the minimum threshold?
>
>
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
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
> the right channel to
Hi
On Wed, Aug 20, 2025 at 05:56:27PM +0200, Timo Rothenpieler via ffmpeg-devel
wrote:
> On 8/20/2025 1:26 AM, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi
> >
> > It seems the forgejo CI takes about
> > 13min to do fate on aarch64 and x86-64 and build on w
Hi
It seems the forgejo CI takes about
13min to do fate on aarch64 and x86-64 and build on win64
Locally i run
fate + install on x86-64
build on x86-32, mingw64, arm32, mips, ppc, x86-64 + shared libs
testprogs alltools examples build on x86-64, x86-32 and arm32
in 2min 44sec
can
Hi all
what name should we give 8.0 ?
I already asked but it seems only a single reply suggested a name.
Just want to make sure everyone heared the call
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Democracy is the form of government in which you can choose
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
> >
> > I intend to create the release/8.0 branch in the next 1-2 weeks
> > after that i intend to make
Hi
On Fri, Aug 01, 2025 at 03:17:48PM -0700, Jacob Lifshay wrote:
> On July 23, 2025 4:43:43 AM PDT, Michael Niedermayer
> wrote:
> > Hi everyone
> >
> > I intend to create the release/8.0 branch in the next 1-2 weeks
> > after that i intend to make teh 8.0 rele
Hi Andrew
On Fri, Jul 25, 2025 at 06:34:53PM +0300, Andrew Randrianasulu wrote:
> ср, 23 июл. 2025 г., 14:43 Michael Niedermayer :
>
> > Hi everyone
> >
>
> Hi.
>
> I still wish you put some time in making more accurate web changelog, with
> detailed (with g
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 != (-
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:
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->...
> >
> &
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 Nied
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
On Thu, Aug 14, 2025 at 04:18:03PM +0200, Nicolas George wrote:
> Kieran Kunhya via ffmpeg-devel (HE12025-08-14):
> > I don't think we should partake in this "security vulnerability farming"
> > exercise. This isn't a security issue and it spams the code with integer
> > overflow checks to fix a th
FFmpeg/pulls/20236.patch
> >
> > Fixes: integer overflow
> > Fixes: testcase that calls av_timecode_init_from_components() with hh set
> > explicitly to INT_MAX
> >
> > Found-by: Youngjae Choi, Mingyoung Ban, Seunghoon Woo
> > Signed-off-by: Michael Niedermayer
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 you want something backported do it quick or ping me on IRC
and tell me to wait
thx
--
On Wed, Aug 13, 2025 at 02:57:02AM +0200, Timo Rothenpieler wrote:
> On 8/13/2025 2:43 AM, Michael Niedermayer wrote:
> > Hi
> >
> > On Tue, Aug 12, 2025 at 11:22:44PM +0200, Jean-Baptiste Kempf wrote:
> > > On Tue, 12 Aug 2025, at 17:59, Kacper Michajlow wrote:
>
Hi
On Tue, Aug 12, 2025 at 11:22:44PM +0200, Jean-Baptiste Kempf wrote:
> On Tue, 12 Aug 2025, at 17:59, Kacper Michajlow wrote:
> > Because of course there is homer-bot... I think everyone seen
> > marge-bot too https://github.com/smarkets/marge-bot (also GitLab
> > specific)
>
> Be careful, tho
h
> >
> >
> > >From a489870a2b35bf0e5a6a9a12696bceb211e18a35 Mon Sep 17 00:00:00 2001
> > From: Michael Niedermayer
> > Date: Mon, 11 Aug 2025 20:06:25 +0200
> > Subject: [PATCH 1/2] tools/merge-all-source-plugins: Fix merge_internal()
> > return code
> >
>
Hi Lynne
On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote:
> Recently, the issue of plugins was raised.
>
> Michael pushed a patch to enable out of tree branches to be freely added to
please look at this before you freak out and insta revert things again:
https://code.ffmpeg.org/FFmpeg/FFmp
On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote:
> Recently, the issue of plugins was raised.
>
> Michael pushed a patch to enable out of tree branches to be freely added to
> FFmpeg. I did not very much like the option of having officially-endorsed
> source plugins, as to me, it moved all t
Hi Lynne
On Tue, Aug 12, 2025 at 03:38:31PM +0900, Lynne wrote:
> On 11/08/2025 22:10, Michael Niedermayer wrote:
> > Hi Lynne
> >
> > On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote:
> > [...]
> > > To me, at least, I can imagine five options:
> &g
Hi Lynne
On Tue, Aug 12, 2025 at 03:25:13PM +0900, Lynne wrote:
[...]
> We are all very busy volunteers. Asking us to periodically inspect all
> projects included as source plugins for LGPL/GPL violations after an
> unreviewed policy change by a single maintainer is overtly wrong.
Noone is asking
On Thu, Aug 07, 2025 at 02:20:11PM -0700, Dale Curtis wrote:
> On Wed, Aug 6, 2025 at 3:05 PM Michael Niedermayer
[...]
>
> >
> >
> > >
> > > Signed-off-by: Dale Curtis
> > > ---
> > > libavcodec/h264_refs.c | 7 +++
> > > 1 fi
Hi Peter
On Fri, Aug 08, 2025 at 09:27:35AM +0200, Peter Enderborg wrote:
> This fixes two old TODO's in ipv6 multicast handling.
> If the system as SIOCGIFINDEX ioctl a helper function to iterate over
> all interfaces added to join the multicast group on interface if approperite.
>
> The default
Hi Peter
On Fri, Aug 08, 2025 at 09:27:34AM +0200, Peter Enderborg wrote:
> Adds a generic ioctl tester and a specific test SIOCGIFINDEX
> that sets ioctl_gifindex. It is a network specific feature
> and the tests are run only in network context.
>
> Signed-off-by: Peter Enderborg
> ---
> conf
On Fri, Aug 08, 2025 at 02:08:42AM +, Jiasheng Jiang wrote:
> Add av_free() if qf_vid is NULL to avoid potential memory leak.
>
> Fixes: 5d48e4eafa ("Merge commit 'a6a750c7ef240b72ce01e9653343a0ddf247d196'")
> Signed-off-by: Jiasheng Jiang
> ---
> libavutil/tests/lzo.c | 6 ++
> 1 file c
On Sat, Aug 09, 2025 at 03:10:20AM +, Jiasheng Jiang wrote:
> Add av_frame_free() to release frame to avoid potential memory leaks.
>
> Fixes: 5fdb5ed613 ("FATE: add a test for sliced scaling")
> Signed-off-by: Jiasheng Jiang
> ---
> tools/scale_slice_test.c | 2 ++
> 1 file changed, 2 inser
On Fri, Aug 08, 2025 at 07:22:29PM +, Jiasheng Jiang wrote:
[...]
> @@ -69,44 +70,49 @@ static int video_decode_example(const char
> *input_filename)
> codec = avcodec_find_decoder(origin_par->codec_id);
> if (!codec) {
> av_log(NULL, AV_LOG_ERROR, "Can't find decoder\n");
>
Hi Remi
On Fri, Aug 08, 2025 at 10:14:52AM +0700, Rémi Denis-Courmont wrote:
>
>
> Le 7 août 2025 19:37:32 GMT+07:00, Nicolas George a écrit :
> >Rémi Denis-Courmont (HE12025-08-07):
> >> Sure. You can send a list of patch files... And make it even more
> >> difficult to review,
> >
> >What? A
On Mon, Aug 11, 2025 at 08:04:02PM +0800, Zhao Zhili wrote:
>
>
> > On Aug 11, 2025, at 18:51, Michael Niedermayer
> > wrote:
> >
> > On Mon, Aug 11, 2025 at 11:37:55AM +0300, quink wrote:
> >> PR #20212 opened by quink
> >> URL: https://code
Hi Lynne
On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote:
[...]
> To me, at least, I can imagine five options:
>
> Option 1 - we have an official binary plugin interface, free for
>everyone to use with no limitation.
That requires someone to create that "binary plugin interface
Hi Lynne
On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote:
> Recently, the issue of plugins was raised.
>
> Michael pushed a patch to enable out of tree branches to be freely added to
> FFmpeg. I did not very much like the option of having officially-endorsed
> source plugins, as to me, it m
On Mon, Aug 11, 2025 at 11:37:55AM +0300, quink wrote:
> PR #20212 opened by quink
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20212
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20212.patch
>
> A set of files begins with the following byte sequence.
>
> 4c 41 4d 45 33
Hi
On Fri, Aug 08, 2025 at 10:36:48AM -0300, James Almer wrote:
> On 8/8/2025 10:28 AM, Michael Niedermayer wrote:
> > Hi
> >
> > AAC USAC conatains a double free since 6 month
> > (https://issues.oss-fuzz.com/issues/393523547)
> >
> > A WIP fix
1 - 100 of 2747 matches
Mail list logo
