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 #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
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 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 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 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 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
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
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 +
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
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 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
12 matches
Mail list logo
