On 07.09.2023 23:38, Kacper Michajlow wrote:
On Thu, 7 Sept 2023 at 15:12, Derek Buitenhuis
wrote:
On 9/6/2023 6:31 PM, Kacper Michajlow wrote:
What would be a downside of preferring CXX always if it exists?
FFmpeg runs in a multitude of environments with a multitude of portability
requirem
On 16.11.2024 19:46, Tom Vaughan wrote:
Any further details you or others could provide to help the x265 dev team
resolve the issue would be appreciated.
Can you share your steps to reproduce this issue? What parameters were changed?
Max CTU size?
Is this documentation inadequate?
https://x2
On 14/08/2025 15:17, Marco Oman via ffmpeg-devel wrote:
Hi all,
I am trying to compile FFmpeg with the --enable-libnpp flag configure on Ubuntu
24.04.
but I am getting an error in file vf_scale_npp.c
CC libavfilter/vf_scale_npp.o
libavfilter/vf_scale_npp.c: In function 'nppscale_deinterle
PR #20279 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20279
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20279.patch
>From 9b949e2a5e82e9bba9ff2e533683ef057acc0fb0 Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Mon, 18 Aug 2025 20:28:26 +
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 send all mails as coming from the
list itself.
At least to me this seems hi
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 #20455 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20455
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20455.patch
Captures windows and monitors with the respective WinRt API.
The filter itself is written in C++, since interacting with WinRt with
PR #20480 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20480
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20480.patch
This was added in 4f78711f9c, with the
commit message claiming that it's a Microsoft restriction that array
textures with ArraySize
PR #20520 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20520
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20520.patch
Combining C++ with our w32pthreads does not work out.
The C++ standard lib headers might include pthread.h, which will then
define
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 win64
Locally i run
fate + install on x86-64
build on x86-32, mingw64, arm32, mips, ppc, x86-64 + shared libs
testprogs all
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 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
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 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
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:
Hi
On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via
On 9/11/2025 4:59 PM, Marco Oman via ffmpeg-devel wrote:
Hi,
I compiled the example hw_decode.c on Ubuntu 24.04 with ffmpeg 7.0 compiled
with --enable-cuda-nvcc. Then lauched the decoding over a small mp4 file with a
video encoded H264 and checked the whole thing with valgrind with the followin
On 9/16/2025 11:12 PM, Balint Marton via ffmpeg-devel wrote:
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
On 9/18/2025 7:29 AM, 张洪源 via ffmpeg-devel wrote:
Dear FFmpeg Developers and Maintainers,
I hope this email finds you well.
My name is [Your Name], and I am writing to kindly inquire about a patch I
recently submitted as my first contribution to the FFmpeg project. The patch is
titled:
"[P
On 15/09/2025 14:30, Michael Niedermayer 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 u
On 9/18/2025 11:25 AM, Zhao Zhili wrote:
Current situation:
1. A patch depends on new sample in fate-suit will fail CI
Just temporarily manually download it in the workflow, and before the PR
gets merged, have the sample be uploaded to the fate-suite and remove
the manual download.
That's h
On 15/09/2025 13:09, 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 (maybe) looks at the bug reporting guidlines (which point
PR #20531 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20531
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20531.patch
There is the tiniest chance that the cond var wait function checks the
predicate, but before it can enter the wait, the capture th
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
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
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 #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
PR #20562 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20562
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20562.patch
This is forwarded from
https://lists.ffmpeg.org/lore/ffmpeg-devel/20250703142520.16586-1-ddeso...@nvidia.com/T/#u
so it doesn't g
PR #20524 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20524
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20524.patch
>From f85da32e3a841742fda6e869afa6ce21a84e8550 Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Mon, 15 Sep 2025 14:17:49 +
On 21.09.2025 03:19, Brad Smith via ffmpeg-devel wrote:
libavformat/udp.c:283:9: warning: unused variable 'i' [-Wunused-variable]
Signed-off-by: Brad Smith
---
libavformat/udp.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/libavformat/udp.c b/libavformat/udp.c
in
PR #20554 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20554
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20554.patch
libnpp is a closed source proprietary library, and for most of its
functionality, proper open source functionality via CUDA kernel
31 matches
Mail list logo
