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:
"[PATCH] fftools/opt_common: add separator line to show
On Tue, 16 Sep 2025 10:49:00 +0200
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
PR #20545 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20545
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20545.patch
From c373636f554579340c7b1f46c42cc3a6989a7da6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kacper=20Michaj=C5=82ow?=
Date: Thu, 18
PR #20544 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20544
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20544.patch
Refer to RFC 4588.
Add and set the basic param of RTX like
ssrc, payload_type, srtp.
Modify the SDP to add RTX info so that
the peer be
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 i
PR #20477 opened by indecisive_turtle
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20477
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20477.patch
This is a compute implementation of the prores kostya encoder. On my NVIDIA GTX
1650 it's about 3-4x faster than the reference code. Ther
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
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.
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
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
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
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
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 wor
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.
Regards,
Martin Storsjö via ffmpeg-devel (HE12025-09-16):
> No, that is not the point at all.
>
> The point is having one's voice and vote count, without needing to disclose
> it publicly. On potentially contentious matters, people eligible to vote may
> wish to do so, without having to publicly state thei
> -Original Message-
> From: Michael Niedermayer
> Sent: Tuesday, September 16, 2025 10:49 AM
> To: FFmpeg development discussions and patches
> Cc: g...@ffmpeg.org
> Subject: [POLL] [VOTE] code.ffmpeg.org vs. ML
>
> Hi all
>
> 2 months ago we voted on testing Forgejo vs Gitlab, we p
On Tue, 16 Sep 2025 23:12:55 +0200 Balint Marton via ffmpeg-devel
wrote:
> [...]
>
> - Comparing pull request versions does not remove the upstreamed commits
>from the comparison, so if a new version is newly rebased, I see
>upstream commits as well in the comparison.
>
> [...]
I think t
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
PR #20539 opened by Leo Izen (Traneptora)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20539
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20539.patch
When calculating the max size of an output PNG packet, we should
include the size of a possible eXIf chunk that we may write.
Signed-
19 matches
Mail list logo
