Hi,
I posted a patch not long ago to remove the long-deprecated glob_sequence
pattern type.
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20267
As far as I know there is no strict rule against removing options or
changing defaults without a major version bump, generally we follow common
sense
Hi,
On Wed, Jul 23, 2025 at 10:51 AM Nil Fons Miret via ffmpeg-devel
wrote:
> Pinging this patch from a couple weeks ago. To be clear, I am not sure
> how people typically use ffmpeg's ID3v2 support, so please let me know
> if the patch is missing something and I'm happy to
PR #20296 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20296
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20296.patch
This commit fixes some memory and security issues due to improper
sanitizing and checks.
Fixes:
- CID 1665100..1665107
Signed-off-b
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
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/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
On Wed, 20 Aug 2025, 11:37 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> 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
&g
> On 20 Aug 2025, at 00:27, Jacob Lifshay via ffmpeg-devel
> wrote:
>
>
>
> On August 19, 2025 2:27:12 PM PDT, Michael Niedermayer via ffmpeg-devel
> wrote:
>> Hi all
>>
>> what name should we give 8.0 ?
>
> IDK if it's a very good su
Gyan Dochi wrote:
>>* Huffman
>
>+1
+1
Best regards, Reto
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
[email protected] with subject "
On Wed, 20 Aug 2025, 19: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
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 ?
>
> Following are 2 plans, as we execute either we may run into issues
> and of course adapt them as needed. (or even sw
On 2025-08-21 11:17 am, Lynne via ffmpeg-devel wrote:
---
src/index | 42 ++
1 file changed, 42 insertions(+)
This should be pushed now that the release is tagged (with the date
corrected)
Regards,
Gyan
diff --git a/src/index b/src/index
index
On 22/08/2025 07:00, Kieran Kunhya via ffmpeg-devel wrote:
On Thu, 21 Aug 2025, 11:33 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
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 Niedermay
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
> --- a/src/index
> +++ b/src
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 Thu, 21 Aug 2025, 11:33 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
> 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:
> >
On Fri, 22 Aug 2025 15:47:04 +0200 Nicolas George via ffmpeg-devel
wrote:
> The filters that do not even touch the alpha plane are the most likely
> to produce invalid garbage with premultiplied alpha. They should NOT
> enable support.
Quod non sequitur.
Filters which do not touch
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:
[...]
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 aa
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 Haas via ffmpeg-devel (HE12025-08-20):
> I accidentally deleted a line too many here, the text was supposed to read:
>
> Do you expect filter authors to remember to enable support for
> premultiplied alpha, even if they don't even touch the alpha plane?
Hi. It is a
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, <
> > [email protected]> 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
PR #20315 opened by Damiano Galassi (galad)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20315
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20315.patch
Fix a regression introduced in 4eca8df, writing chapters failed if chapters
where not available before mov_write_header() is called
PR #20357 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20357
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20357.patch
>From 7c533ae7404fb20a4513ef766e368300dfe3cc54 Mon Sep 17 00:00:00 2001
From: Jack Lau
Date: Thu, 28 Aug 2025 07:22:04 +0800
Subject: [
Hi Pavel,
> also, netint_libxcoder README docs url returns a 404 Not Found:
> https://docs.netint.com/quadra/documentation/libxcoder
Thanks for pointing that out. The URL moved to
https://docs.netint.com/vpu/quadra/documentation/libxcoder
I'll look into getting that fixed.
Regards,
Desmond Li
Hi Pavel,
> I've cloned the netint ffmpeg fork from
> https://github.com/netintsteven/NI_FF_upstream/tree/upstream
> - looks like it was last updated on June 30th, 2025 -- about 2 months
> behind ffmpeg master
> - libavcodec/nicodec.h includes ni_device_api.h, so
> https://github.com/NETINT-Tech
PR #20359 opened by Peter Ross (pross)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20359
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20359.patch
Sample: https://github.com/vgmstream/vgmstream/files/11607386/Jumbo_Josh_1.zip
This was a contribution I made to librempeg last year.
PR #20348 opened by Marton Balint (cus)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20348
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20348.patch
It is more user-friendly to print which option caused the parse error.
Signed-off-by: Marton Balint
>From 94431f8b33bc7ed84069ed02bc
PR #20349 opened by Marvin Scholz (ePirat)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20349
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20349.patch
This PR is a proposal for a new API in `libavformat`, which I call the command
API, it adds the ability to send commands to demuxers
On Tue, Jul 22, 2025 at 3:26 PM Desmond Liu wrote:
> > They did, thank you ... the price they mentioned is too high to satisfy
> my
> > curiosity.
>
> You can sign up for an Akamai cloud account for testing/development.
> They have an "Accelerated Linode" with our hardware. If you sign up
> with
PR #20355 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20355
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20355.patch
libjxl consumes no input if it returns an error, so this loops over
and over while it spits out the same error many times. If we got a
On Tue, Aug 26, 2025 at 3:47 PM Pavel Koshevoy wrote:
>
>
> On Tue, Jul 22, 2025 at 3:26 PM Desmond Liu wrote:
>
>> > They did, thank you ... the price they mentioned is too high to satisfy
>> my
>> > curiosity.
>>
>> You can sign up for an Akamai cloud account for testing/development.
>> They h
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.
>
On 8/27/2025 12:54 PM, Michael Niedermayer via ffmpeg-devel wrote:
> Here:
> https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2024-November/336263.html
>
> You wrote this:
> "I also do not believe STF and SPI are being used appropriately, and
> I believe Thilo is recie
On Wed, Aug 27, 2025 at 6:03 PM Michael Niedermayer via ffmpeg-devel
wrote:
>
> 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
> > Niedermay
PR #20351 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20351
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20351.patch
If this function returns an error after ff_sws_graph_add_pass() has been
called, and the pass->free callback is therefore already set up
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 :
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/Makefile | 1 +
> > tests/fate/av1.mak | 7 +
> > tests/ref/fate/lib
PR #20352 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20352
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20352.patch
Fix leaks. We forgot to free these.
>From a8d6b87a4442c690587db6f44cc7ed72a2de81fc Mon Sep 17 00:00:00 2001
From: Leo Izen
Date: We
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_minterpolate: Hoist hot loop in `set_frame_data`
libavfilter/vf_minterpolate: Use local var
Signed-off-by: Zsolt Vadasz
---
libavfilter/vf_minterpolate.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_minterpolate.c b/libavfilter/vf_minterpolate.c
index 2406259056..ba5c512e03 100644
--- a/libavfilter/vf_minterpolate.c
+++ b/libavfilter/vf_minter
Signed-off-by: Zsolt Vadasz
---
libavfilter/vf_minterpolate.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/libavfilter/vf_minterpolate.c b/libavfilter/vf_minterpolate.c
index d034783bc5..2406259056 100644
--- a/libavfilter/vf_minterpolate.c
+++ b/libavfilter
PR #20370 opened by Dmitrii Ovchinnikov (OvchinnikovDmitrii)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20370
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20370.patch
.forgejo/CODEOWNERS: add myself for relevant files(AMF)
MAINTAINERS: Update the entries for AMF
>From 05d9d97bc6d
On 8/29/2025 2:08 AM, Kieran Kunhya via ffmpeg-devel wrote:
>> +"guid": "ffmpeg-crypto",
>> +"type": "other",
>> +"address": "0x2f3900e7064eE63D30d749971265858612AA7139",
>> +
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 value is IN6ADDR_ANY (::) and it then joins all interfaces
that are up and have mult
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
---
configure | 16
1 file changed, 16 insertions(+)
diff --git a/configure b/c
A new commandline option to set for joining multiple
interfaces. The default is one, and it is also a
special case falling back to output routing table
for selecting interface on group join. On group
join it search over all interfaces.
Change-Id: Idbf88c3ecd7d27cba0a236a8fa2451a85143d068
Signed-of
Add a commandline option for selecting interface by name.
This is useful when your multicast routing table for
sending multicast does not match the interface reciving
is wanted.
Signed-off-by: Peter Enderborg
---
libavformat/rtpproto.c | 4
libavformat/rtsp.c | 3 +++
libavformat/rtsp
Two new options added for receive IPv6 multicast streams.
1 multicast_max_joins
2 multicast_interface
Change-Id: Ief0389815cff3edf26f7db5cbff033ce8bb24639
Signed-off-by: Peter Enderborg
---
doc/protocols.texi | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/d
History:
v2 Added configure script to disable interface selection for systems that
do not support ioctl SIOCGIFINDEX for mapping name to index-id.
v2.1 rebase
v3 Added patches for command-line options to select interface and
maximum number of interfaces.
Spited iterate function to use a helper fu
Hello Martin,
I just found a time to have a look at your comments, mostly I fixed it,
additionally I optimised code a bit deeper because on Mac platform it
showed me reduction in performance (turned on auto-vectorisation by
default) + excluded unused code.
You mentioned submition of patch as a PR,
On Sat, 30 Aug 2025, George Zaguri wrote:
You mentioned submition of patch as a PR, you mean open merge request I
guess, how it works with mailing list? Do I need to update the patch in
mailing list as well? Should I reflect opened PR somewhere?
Not sure what I mentioned earlier (that was prob
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):
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,
mca, and scd demuxers already support.
Tested with file output from "Polyphone" s
PR #20369 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20369
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20369.patch
Now that the major EXIF overhaul has been merged, I should be suggested
to review patches that modify it.
Signed-off-by: Leo Izen
Hi Derek
On Fri, Aug 29, 2025 at 01:48:07PM +0100, Derek Buitenhuis via ffmpeg-devel
wrote:
> On 8/29/2025 2:08 AM, Kieran Kunhya via ffmpeg-devel wrote:
> We'll see if this is pushed without consent like funding.json
> was to the main git repo, which has yet to be removed.
I
On 8/29/2025 4:15 PM, Michael Niedermayer via ffmpeg-devel wrote:
> Implying that a funding.json was pushed without consent is unacceptable
It was and I said so at the time. Nobody approved it. Please forward to the
CC if you think it is unacceptable. Their silence is typical.
I'll CC
On Fri, Aug 29, 2025 at 5:23 PM Michael Niedermayer via ffmpeg-devel <
[email protected]> 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 th
On Fri, 29 Aug 2025, Peter Enderborg via ffmpeg-devel wrote:
Two new options added for receive IPv6 multicast streams.
1 multicast_max_joins
2 multicast_interface
Change-Id: Ief0389815cff3edf26f7db5cbff033ce8bb24639
Signed-off-by: Peter Enderborg
---
doc/protocols.texi | 17
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":
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 +++
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:
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
PR #20527 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20527
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20527.patch
AVFormatContext.event_flags is checked against AVSTREAM_EVENT_FLAG,
which belongs to AVStream.event_flags. There is no real issue since
t
PR #20528 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20528
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20528.patch
Plus checkasm tests for both
>From a406d6e309380e0413aa1b0c6ea98cfbe5912538 Mon Sep 17 00:00:00 2001
From: Niklas Haas
Date: Mon, 15
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
Hi Nicolas,
Thanks for the clarification about Omneon.
I agree that it makes sense to simply fix the UL as in this patch.
Best regards,
Helmuth
Em seg., 15 de set. de 2025 às 11:40, Nicolas Gaullier via ffmpeg-devel <
[email protected]> escreveu:
> On 9/15/25 15:26, Helmuth Sc
On 2025-09-16 12:05 am, Timo Rothenpieler via ffmpeg-devel wrote:
On 9/15/2025 8:26 PM, Michael Niedermayer via ffmpeg-devel wrote:
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
On 9/9/2025 9:38 AM, Jerome Martinez via ffmpeg-devel wrote:
diff --git a/libavformat/matroskaenc.c b/libavformat/matroskaenc.c
index 8142d9125e..5339b6fd33 100644
--- a/libavformat/matroskaenc.c
+++ b/libavformat/matroskaenc.c
@@ -1706,16 +1706,16 @@ static void
mkv_write_blockadditionmapping
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
PR #20504 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20504
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20504.patch
Marking this as WIP because I think it may be a little contentious. Mainly
leaving it here as an RFC.
>From 1418fcfe7d326ac9c1b876757
On Wed, 17 Sep 2025, Timo Rothenpieler via ffmpeg-devel wrote:
On 9/16/2025 11:12 PM, Balint Marton via ffmpeg-devel wrote:
- I am not sure what would be the counterpart of doing a last-chance ping
before applying a series in the foregejo system, it was a useful thing
in the ML
Michael Niedermayer via ffmpeg-devel (HE12025-09-16):
> F. keep Forgejo as primary forge for patch/git workflow
> M. switch back to the ML for patch/git workflow
M of course.
We can try again in a year or two when the proponents have had time to
learn from the mistakes of this attempt.
R
PR #20541 opened by Marvin Scholz (ePirat)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20541
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20541.patch
- Fix leading space in the RTSP reason string
- Avoid logging invalid values and instead properly log warnings on failure
reading RT
Staying with Forgejo, so option "F".
On 9/16/2025 10:49 AM, Michael Niedermayer wrote:
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
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 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
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
PR #20543 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20543
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20543.patch
The first 3 commits aren't strictly fixes for existing issues, but just code
cleanup and general improvements found while hunting
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, and the right side is object storage cost,
they're billed separately, so I split them here as well.
On 9/17/2025 8:32 PM, Marton Balint via ffmpeg-devel wrote:
On Wed, 17 Sep 2025, Timo Rothenpieler via ffmpeg-devel wrote:
On 9/16/2025 11:12 PM, Balint Marton via ffmpeg-devel wrote:
- I am not sure what would be the counterpart of doing a last-chance
ping
before applying a series
PR #20535 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20535
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20535.patch
Regression since 5acbdd2264d3b90dc11369f9e031e762f260882e, which removed
setting both values from PerThreadContext.
Given the pthread
On Tue, 16 Sept 2025, 16:17 Lynne via ffmpeg-devel,
wrote:
> PR #20533 opened by Lynne
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20533
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20533.patch
IMO unrelated and independent changes should be different PRs
PR #20536 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20536
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20536.patch
This way `./configure --cc=x86_64-pc-linux-gnu-clang` and the like will do
something sensible, same for variants of gcc.
>From 9
On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote:
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 wa
On 16 Sep 2025, at 10:49, Michael Niedermayer wrote:
> 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
On 2025-09-16 10:49 +0200, Michael Niedermayer via ffmpeg-devel wrote:
>
[...]
>
> * If we keep forgejo we will likely transition our issue tracker tickets
> into forgejo too, discussing with timo yesterday night indicates that
> this likely can be done cleaner and neate
PR #20485 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20485
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20485.patch
This is a script I've used for tidying up my own assembly for many years, and
that I've used for touching up and making the aarch
PR #20577 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20577
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20577.patch
These should also exclude the _NB values themselves.
>From 025b89018fc8a9d9e457a0c102101fd9bf01fa3e Mon Sep 17 00:00:00 2001
From: Nik
libavutil/arm: Make use of elf_aux_info() on FreeBSD/OpenBSD
- FreBSD/OpenBSD have elf_aux_info() on arm
- Wrap AT_HWCAP as the value is different for BSD vs Linux (16 vs 25)
Signed-off-by: Brad Smith
---
libavutil/arm/cpu.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
di
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:
On 2025-09-16 03:16 am, Michael Niedermayer via ffmpeg-devel wrote:
[...]
And what do we gain by avoiding "wholesale migr
PR #20613 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20613
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20613.patch
Supersedes: FFmpeg/FFmpeg#20603
Fixes: FFmpeg/FFmpeg#20589
>From e7cdaf8a842c8c8e9c439e53da70fa61f91f4ce9 Mon Sep 17 00:00:00 2001
Fro
PR #20615 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20615
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20615.patch
>From 38c142874ed506922c3b0452c1078f4c752352d0 Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Fri, 26 Sep 2025 16:06:50 +0800
Subject:
PR #20623 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20623
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20623.patch
sidx earliest_presentation_time as the name says, is in presentation timeline.
I made a mistake in 301141b, which intended to create pres
Hi Remi
On Sun, Sep 28, 2025 at 10:54:14AM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Le maanantaina 15. syyskuuta 2025, 0.23.17 Itä-Euroopan kesäaika Michael
> Niedermayer via ffmpeg-devel a écrit :
[...]
> > we can have custom ticket states and custom
> > w
On 2025-09-28 06:14 am, Michael Niedermayer via ffmpeg-devel wrote:
What you can see here, is there are only 690 open tickets, that is not thousands
The oldest 'new' ticket is from 2013, so that label is misleading.
They are "new" in the sense that they have not been
Hi Remi
On Sun, Sep 28, 2025 at 10:54:14AM +0300, Rémi Denis-Courmont via ffmpeg-devel
wrote:
> Le maanantaina 15. syyskuuta 2025, 0.23.17 Itä-Euroopan kesäaika Michael
> Niedermayer via ffmpeg-devel a écrit :
[...]
> With that said, you can assign thumbs-up, thumbs-down and other
Le lun. 29 sept. 2025 à 11:46, Yalda a écrit :
>
> Hi Romain,
>
> My pleasure and thanks for contributing this change.
>
> I was just wanting to know on this line (tagged in PR comments), if
> there are scenarios
> where we may only get one of these blocks on segment change and if we
need to
> als
PR #20631 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20631
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20631.patch
When the furthest-behind stream is being fed by a demuxer that is also
feeding packets to a choked filter graph, we need to unchoke that
On Fri, 3 Oct 2025, Martin Storsjö wrote:
Filter them out from the preprocessor invocation, and don't remove
them based on matching the "^-m" pattern.
As an alternative, we could also have gas-preprocessor.pl implicitly
add this option if the option "-arm64EC" is found, but requiring
the user t
PR #20688 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20688
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20688.patch
Fixes: 0ce413af9cc8040095a6b714600d6a8dceaca514
From 7d9ad3c070df74b8d7571139fb9761c2bd72e87f Mon Sep 17 00:00:00 2001
From: =
On Fri, Oct 10, 2025 at 11:24 PM Michael Niedermayer via ffmpeg-devel
wrote:
>
> Hi Devin
>
> On Fri, Oct 10, 2025 at 10:07:16AM -0400, Devin Heitmueller via ffmpeg-devel
> wrote:
> > On Fri, Oct 10, 2025 at 10:03 AM Kieran Kunhya via ffmpeg-devel
> > wrote:
>
On Fri, Oct 10, 2025 at 11:36 PM Nicolas George via ffmpeg-devel
wrote:
>
> Kieran Kunhya via ffmpeg-devel (HE12025-10-10):
> > The only reasonable suggestion is get agreement from your shareholders
> > before raising this topic in public.
>
> Are you their lawyer? Bec
2801 - 2900 of 3426 matches
Mail list logo
