Won't this busy-loop in filter.c if it keeps returning EAGAIN for longer
periods of time/forever?
The whole API really isn't prepared for non-blocking operations, so I'm
not sure this is a good idea.
OpenPGP_0xD85AAA6874B7507E.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Descript
proceed via the standard SPI donation route.
Thank you for all your work on FFmpeg.
I don't think there is any problem with that model, we're not AGPL after
all.
The donations are of course greatly appreciated!
Timo
___
ffmpeg-devel ma
On 13/11/2025 04:06, Michael Niedermayer via ffmpeg-devel wrote:
Hi Kieran
On Wed, Nov 12, 2025 at 12:09:00AM -0800, Kieran Kunhya via ffmpeg-devel wrote:
On Mon, 10 Nov 2025, 19:00 Michael Niedermayer via ffmpeg-devel, <
[email protected]> wrote:
Hi Remi
On Mon, Nov 10, 2025 at 06:03:
On 06/11/2025 09:40, Nicolas George via ffmpeg-devel wrote:
Rémi Denis-Courmont (HE12025-11-04):
From a technical standpoint, that seems very agreeable indeed. But at
the same time, it sounds unreasonable to expect that of a bounty
claimant.
Can you elaborate why you think that? We set the ru
PR #20824 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20824
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20824.patch
>From f0b423a688cb75fa83c064485103007425892f96 Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Sun, 2 Nov 2025 23:31
On 02.11.2025 00:38, Niklas Haas via ffmpeg-devel wrote:
Hi all,
at VDD'25 multiple people discussed interest in the ability to improve the
filter negotiation around hardware filters; specifically about avoiding
the need to constantly set the pixel formats manually when going from HW to
SW, and
On 22.10.2025 19:07, Rémi Denis-Courmont via ffmpeg-devel wrote:
Le keskiviikkona 22. lokakuuta 2025, 16.07.36 Itä-Euroopan kesäaika Timo
Rothenpieler via ffmpeg-devel a écrit :
C++ can be used as-is, since it can read all our headers just fine.
FFmpeg public headers are C++-compatible and
On 22.10.2025 14:09, Gregor Riepl via ffmpeg-devel wrote:
My main motivation is to be able to use STL, which would simplify
string handling and memory management, and give us access to its data
structures. Manual memory management has its place, especially in lavc.
In lavf less so. RAII would do
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/[email protected]/thread/HS46O6K62MHRHJDJC45XL
/ funding people
fulltime.
Since we have just been approved for the EUs YesWeHack program, someone
will need to work through the incoming bugs and triage/fix/look at them.
That could definitely be something someone could use some sponsoring for.
Timo
OpenPGP_0xD85AAA6874B7507E.asc
Description
On 23.09.2025 22:44, Stefano Sabatini via ffmpeg-devel wrote:
On Tue, Sep 16, 2025 at 12:41 AM Michael Niedermayer via ffmpeg-devel
wrote:
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
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 #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
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/[email protected]/T/#u
so it doesn&#
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
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 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 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
x27;d be good if this was billed directly to
FFmpeg via SPI somehow.
Timo
smime.p7s
Description: S/MIME Cryptographic Signature
___
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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 hu
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
unity wants to extend that.
(Also if results are inconclusive like because a 3rd option emerges
then ill restart this with condorcet on vote.ffmpeg.org)
* If we keep forgejo we will likely transition our issue tracker tickets
into forgejo too, discussing with timo yesterday night indicates
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.
>F
ot; vs "M." / "ML"
End time is in 7 days unless teh community wants to extend that.
(Also if results are inconclusive like because a 3rd option emerges
then ill restart this with condorcet on vote.ffmpeg.org)
* If we keep forgejo we will likely transition our issue tracker
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
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
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/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
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
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
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
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
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, <
[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 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
worked for
nut-devel, but that's not exactly the most active list.
Timo
smime.p7s
Description: S/MIME Cryptographic Signature
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, v
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
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 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:
Because of course there is homer-bot... I think everyone seen
marge-bot too https://github.com/smarkets/marge-bot (als
On 8/12/2025 7:04 PM, Marton Balint wrote:
On Tue, 5 Aug 2025, Kacper Michajlow wrote:
On Mon, 4 Aug 2025 at 23:38, Marton Balint wrote:
- Previously it was pretty clear from git history who actually committed
a change from the comitter field. With using forgejo the comitter
field
PR #20218 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20218
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20218.patch
>From ca8f1a6a88958c07d94a972e62a0f74a78eee681 Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Mon, 11 Aug 2025 18:47
PR #20186 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20186
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20186.patch
>From b5ab096897e92a56642a17a6ef212620f5c7d79b Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Fri, 8 Aug 2025 21:37
PR #20180 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20180
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20180.patch
>From ae490baa69b68edf12c423c53c23a9cf4654122a Mon Sep 17 00:00:00 2001
From: Timo Rothenpieler
Date: Fri, 8 Aug 2025 17:21
PR #20114 opened by Timo Rothenpieler (BtbN)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20114
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20114.patch
Not sure on the Changelog entry. How is that normally handled, to document an
important change that will happen on next major
On 8/4/2025 9:17 PM, [email protected] wrote:
Hi *ffmpeg-devel* ,
The primary mail of your account was just changed to [email protected].
This means that this e-mail address will no longer receive e-mail notifications
for your account.
Sorry for the noise, the original plan with this ac
On 8/3/2025 10:29 PM, Michael Niedermayer wrote:
Hi Timo
On Sun, Aug 03, 2025 at 10:01:42PM +0200, Timo Rothenpieler wrote:
On 8/3/2025 9:02 PM, Michael Niedermayer wrote:
Hi
On Sun, Aug 03, 2025 at 05:31:39PM +0200, Michael Niedermayer wrote:
[...]
The solutions are obvious:
1. ignore
On 8/3/2025 9:02 PM, Michael Niedermayer wrote:
Hi
On Sun, Aug 03, 2025 at 05:31:39PM +0200, Michael Niedermayer wrote:
[...]
The solutions are obvious:
1. ignore security and supply chain attacks
2. use merges not rebases on the server
3. rebase locally, use fast forward only
4. verify on serv
On 8/3/2025 9:12 PM, James Almer wrote:
On 8/3/2025 3:55 PM, Marton Balint wrote:
On Thu, 31 Jul 2025, Timo Rothenpieler wrote:
Hi!
We will migrate away from using git.videolan.org to hosting the two
repos there on our own infrastructure.
To accomplish this, the source.ffmpeg.org domain
On 8/3/2025 5:31 PM, Michael Niedermayer wrote:
Hi
The "on server rebase" process that we are using with forgejo looks a bit
insecure
Previously we wrote code, discussed and then signed and pushed
In this setup the code coming from a developer is not manipulatable
because noone else
On 8/3/2025 3:26 PM, Michael Niedermayer wrote:
On Sun, Aug 03, 2025 at 01:45:17PM +0200, Timo Rothenpieler wrote:
On 8/3/2025 9:41 AM, Michael Niedermayer wrote:
Hi
can we have a tag that causes "automerge on approve" ?
so that if i open a pr i can set that tag and if someone a
On 8/3/2025 9:41 AM, Michael Niedermayer wrote:
Hi
can we have a tag that causes "automerge on approve" ?
so that if i open a pr i can set that tag and if someone approves it, its
merged and i dont have to come back and click that button ?
That is how it should already work normally.
If there
On 7/31/2025 11:57 PM, Stephen Hutchinson wrote:
On 7/31/25 5:26 PM, Derek Buitenhuis wrote:
* I had assumed Forgejo would import my full name from github when I
signed in
via it. It imported absolutely nothing.
Quasi-related to the Github login option, I'm just getting 500 internal
server
On 7/31/2025 10:16 PM, Gyan Doshi wrote:
On 2025-08-01 12:05 am, Timo Rothenpieler wrote:
Hi!
We will migrate away from using git.videolan.org to hosting the two
repos there on our own infrastructure.
What is the timeline for this?
It's already implem
On 7/31/2025 8:35 PM, Timo Rothenpieler wrote:
RSA:
ssh-rsa
B3NzaC1yc2EDAQABAAABAQDLI6KmhvYyBuyjRLC1BgyMHqZzBkloPfnPKJfjVhlE/QsPIQndH1BvzDbCk8478Urhk0ItpeoQL7hXj5D0y1rX5T0GBG1mIZnJBv+Xt9SPbyPoKdw8PN2txCp7TQENg1O5hCNvoQlZwuWb6WKJUVeYLbOZ0RmLO/xIU+7qWA6Puzoh2XDqKeqOZPq6DYqQ54cu
flexibility to configure mirroring and forwarding between our
own servers.
git.videolan.org will turn into a read-only mirror.
Timo
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit
On 7/30/2025 12:39 AM, James Almer wrote:
On 7/29/2025 5:56 PM, Kacper Michajlow wrote:
On Tue, 29 Jul 2025 at 22:11, James Almer wrote:
On 7/29/2025 5:02 PM, Kieran Kunhya via ffmpeg-devel wrote:
Hello,
It seem there is strong evidence that AI wrote TLS code as part of the
WHIP patch. It
On 7/29/2025 2:51 PM, Michael Niedermayer wrote:
On Mon, Jul 28, 2025 at 08:14:58PM -0300, James Almer wrote:
On 7/28/2025 8:13 PM, Michael Niedermayer wrote:
Hi
with git send email i can send 5 independant patches with
git send-email --to='FFmpeg development discussions and patches
' -5
On 7/28/2025 7:24 PM, Michael Niedermayer wrote:
On Mon, Jul 28, 2025 at 06:15:53PM +0200, Timo Rothenpieler wrote:
On 7/28/2025 4:40 PM, Diederick C. Niehorster wrote:
On Mon, Jul 28, 2025 at 4:21 PM Michael Niedermayer
wrote:
Hi
regression: issue aaddresses a regression
bug
On 7/28/2025 4:40 PM, Diederick C. Niehorster wrote:
On Mon, Jul 28, 2025 at 4:21 PM Michael Niedermayer
wrote:
Hi
regression: issue aaddresses a regression
bug:something is not working
This is inconsistent
Label X cannot sometimes mean "X is removed" and "X is added"
bug seems mean
On 7/27/2025 12:44 AM, Michael Niedermayer wrote:
Hi Timo
On Sat, Jul 26, 2025 at 10:41:57PM +0200, Timo Rothenpieler wrote:
On 7/26/2025 10:24 PM, Kacper Michajlow wrote:
On Sat, 26 Jul 2025 at 22:14, Timo Rothenpieler wrote:
On 7/26/2025 10:01 PM, Derek Buitenhuis wrote:
On 7/26/2025 8
On 7/26/2025 11:07 PM, Kacper Michajlow wrote:
On Sat, 26 Jul 2025 at 22:42, Timo Rothenpieler wrote:
On 7/26/2025 10:24 PM, Kacper Michajlow wrote:
On Sat, 26 Jul 2025 at 22:14, Timo Rothenpieler wrote:
On 7/26/2025 10:01 PM, Derek Buitenhuis wrote:
On 7/26/2025 8:29 PM, Timo
On 7/26/2025 10:24 PM, Kacper Michajlow wrote:
On Sat, 26 Jul 2025 at 22:14, Timo Rothenpieler wrote:
On 7/26/2025 10:01 PM, Derek Buitenhuis wrote:
On 7/26/2025 8:29 PM, Timo Rothenpieler wrote:
It's still an extended test. You cannot push to it, since it's just a
mirror.
That&
On 7/26/2025 10:14 PM, Kacper Michajlow wrote:
n Sat, 26 Jul 2025 at 21:29, Timo Rothenpieler wrote:
On 7/26/2025 7:03 PM, Derek Buitenhuis wrote:
On 7/22/2025 4:53 AM, Lynne wrote:
---
src/contact | 11 +++
src/index | 52
On 7/26/2025 10:01 PM, Derek Buitenhuis wrote:
On 7/26/2025 8:29 PM, Timo Rothenpieler wrote:
It's still an extended test. You cannot push to it, since it's just a
mirror.
That's not what written in the announcement, and the fact it is "still
a test" has not been comm
On 7/26/2025 7:03 PM, Derek Buitenhuis wrote:
On 7/22/2025 4:53 AM, Lynne wrote:
---
src/contact | 11 +++
src/index | 52
2 files changed, 63 insertions(+)
So I am a bit unclear, is development now Forgejo or ML, or both?
Bec
On 7/25/2025 7:45 PM, Derek Buitenhuis wrote:
On 7/25/2025 6:35 PM, Timo Rothenpieler wrote:
The problem is changing it now might de-auth everyone who already signed
in via Github. Though better now then later, might force a few people to
sign up a second time.
I think it should be done
On 7/25/2025 7:14 PM, Derek Buitenhuis wrote:
https://0x0.st/85bn.png
I know who BtbN is, random contributor does not. Appears sketchy.
The problem is changing it now might de-auth everyone who already signed
in via Github. Though better now then later, might force a few people to
sign up a
On 7/24/2025 7:58 PM, Kyle Swanson wrote:
Hi,
On Thu, Jul 24, 2025 at 10:46 AM Timo Rothenpieler
wrote:
The mails will never contain patches, they're just notifications.
They do contain a link to the patches and the PR number to fetch it via
CLI though.
If you append ".patch"
On 7/24/2025 7:30 PM, Michael Niedermayer wrote:
Hi all
how can i simply follow all changes, patches and discussions ?
prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel
folder.
In that folder,
I can leave things as new that i want to look at later
I can mark
On 7/24/2025 6:48 PM, Nicolas George wrote:
Timo Rothenpieler (HE12025-07-24):
I don't see any need for this, no.
If the patch does not reach our inbox, it will not be reviewed.
That's what it does, just not as format-patch, but simply as a link.
A link is not enough. When w
On 7/24/2025 5:09 PM, Nicolas George wrote:
Timo Rothenpieler (HE12025-07-24):
If the "was synchronized" notifications could be disabled, it'd be much more
reasonable I feel.
But that does not seem to be an option, it's all or nothing.
I am not sure what you mean
On 24/07/2025 03:55, Lynne wrote:
On 24/07/2025 07:06, Timo Rothenpieler wrote:
On 7/23/2025 9:24 PM, Nicolas George wrote:
Hi. I just saw somebody mention this on trac:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20025
But I have no trace of it in my inbox. If this is now an accepted way of
You're gonna have to use a bash-array to handle those args in a sane way.
Also, the runner does not have clang installed, let alone the coverage tools.
---
View it on FFmpeg Forgejo (
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20027#issuecomment-369 ) or reply
to this email directly.
__
On 7/23/2025 9:24 PM, Nicolas George wrote:
Hi. I just saw somebody mention this on trac:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20025
But I have no trace of it in my inbox. If this is now an accepted way of
getting contributions, then either the devel mailing-list should receive
notificat
On 23/07/2025 13:43, 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 release in the following 1-2 weeks
If theres something you want in it make sure its pushed before the branch
is made.
Would it be sen
On 7/22/2025 7:09 PM, Michael Niedermayer wrote:
Hi
On Tue, Jul 22, 2025 at 01:00:49AM +0200, Timo Rothenpieler wrote:
On 7/22/2025 12:17 AM, Michael Niedermayer wrote:
On Mon, Jul 21, 2025 at 06:37:06PM +0200, Timo Rothenpieler wrote:
[...]
--enable-version3
--cc='ccache gcc'
On 22/07/2025 14:36, Jack Lau wrote:
Openssl 1.1.0 version haven't DTLS_get_data_mtu API
Signed-off-by: Jack Lau
---
libavformat/tls_openssl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index fa852aac18..54860857c
On 22/07/2025 08:15, Hendrik Leppkes wrote:
On Mon, Jul 21, 2025 at 3:03 AM Timo Rothenpieler wrote:
* announce code.ffmpeg.org publically so people can start submitting
and reviewing on it as an alternative to the ML
Just be aware that merging is not possible, since the sync script
On 7/22/2025 12:17 AM, Michael Niedermayer wrote:
On Mon, Jul 21, 2025 at 06:37:06PM +0200, Timo Rothenpieler wrote:
It runs basic fate with no special dependencies enabled on x86_64 and
aarch64.
---
.forgejo/workflows/test.yml | 39 +
.gitignore
On 7/21/2025 7:44 PM, Timo Rothenpieler wrote:
On 7/21/2025 7:02 PM, Leo Izen wrote:
On 7/21/25 12:37, Timo Rothenpieler wrote:
It runs basic fate with no special dependencies enabled on x86_64 and
aarch64.
---
.forgejo/workflows/test.yml | 39
On 7/21/2025 7:02 PM, Leo Izen wrote:
On 7/21/25 12:37, Timo Rothenpieler wrote:
It runs basic fate with no special dependencies enabled on x86_64 and
aarch64.
---
.forgejo/workflows/test.yml | 39 +
.gitignore | 1 +
2 files changed, 40
It runs basic fate with no special dependencies enabled on x86_64 and
aarch64.
---
.forgejo/workflows/test.yml | 39 +
.gitignore | 1 +
2 files changed, 40 insertions(+)
create mode 100644 .forgejo/workflows/test.yml
diff --git a/.forgejo/wo
3 Votes
Forgejo: 12 Votes
After we decide what to run on code.ffmpeg.org, I intend to
* apply the CI patches which timo currently keeps rebasing on the Forgejo git
(maybe timo can post these to ffmpeg-devel)
timo, ping can you post the patches ?
I'll rebase them into one patch and
On 16/07/2025 15:36, Glen Edwards wrote:
Add Support for Muxing VP8, VP9, and AV1 Video Codecs in the mov muxer,
than Add Support for Muxing TTA, FLAC and Opus audio Codecs in the mov
muxer, plus improvements in the mov muxer plus modern audio/video codec
support , Plus Modern Audio and Video Cod
I intend to push this series soon-ish.
So if you intended to review it, please let me know and I can wait.
___
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
On 7/15/2025 12:01 AM, Michael Niedermayer wrote:
On Mon, Jul 14, 2025 at 10:00:19PM +0200, Timo Rothenpieler wrote:
On 7/14/2025 9:21 PM, Michael Niedermayer wrote:
On Sun, Jul 13, 2025 at 01:42:28PM +0200, Timo Rothenpieler wrote:
On 7/13/2025 3:10 AM, Michael Niedermayer wrote:
Fixes
On 7/14/2025 9:21 PM, Michael Niedermayer wrote:
On Sun, Jul 13, 2025 at 01:42:28PM +0200, Timo Rothenpieler wrote:
On 7/13/2025 3:10 AM, Michael Niedermayer wrote:
Fixes: Infinite loop
Fixes:
427538726/clusterfuzz-testcase-minimized-ffmpeg_dem_FLV_fuzzer-6582567304495104
Found-by
On 7/14/2025 9:21 PM, Michael Niedermayer wrote:
On Sun, Jul 13, 2025 at 01:42:28PM +0200, Timo Rothenpieler wrote:
On 7/13/2025 3:10 AM, Michael Niedermayer wrote:
Fixes: Infinite loop
Fixes:
427538726/clusterfuzz-testcase-minimized-ffmpeg_dem_FLV_fuzzer-6582567304495104
Found-by
I intend to
* apply the CI patches which timo currently keeps rebasing on the
Forgejo git (maybe timo can post these to ffmpeg-devel)
* extend my github cronjob to autosync Forgejo or Gitlab too
(or someone else can set one up)
* announce code.ffmpeg.org publically so people can start submitting
t;F." / "Forgejo" vs "G." / "Gitlab"
End time is in 7 days unless teh community wants to extend that.
(or do people want a formal vote to be setup? on vote.ffmpeg.org)
After we decide what to run on code.ffmpeg.org, I intend to
* apply the CI patches which timo cur
---
libavformat/tls_openssl.c | 26 --
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index c58044b46b..34dd22daf7 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -161,8 +161,8 @
OpenSSL docs say:
These functions have no impact when used with DTLS.
---
libavformat/tls_openssl.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index 63fc085e28..c58044b46b 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_
---
libavformat/tls_openssl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index a497d4dfd8..63fc085e28 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -810,7 +810,7 @@ static int dtls_start(URLC
---
libavformat/tls_openssl.c | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index bb9a5b8054..a497d4dfd8 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -674,15 +674,6 @@ s
---
libavformat/tls_openssl.c | 22 --
1 file changed, 22 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index 8326762592..bb9a5b8054 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -776,15 +776,12 @@ static int dtls_s
---
libavformat/tls_openssl.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index 900ee0f5ab..8326762592 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -987,9 +987,14 @@ static int tls_write(URLContext *h,
---
libavformat/tls_openssl.c | 35 ++-
1 file changed, 30 insertions(+), 5 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index 48d8edb08a..07d1af40d8 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -485,7
---
libavformat/tls_openssl.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index cd11419fee..48d8edb08a 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -216,11 +216,13 @@ in
1 - 100 of 1325 matches
Mail list logo
