PR #20584 opened by rcombs
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20584
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20584.patch
>From 5f00beecfcc26d05d486578e64a07a4c7775 Mon Sep 17 00:00:00 2001
From: rcombs
Date: Tue, 23 Sep 2025 00:45:58 -0700
Subject: [PATCH] l
PR #20581 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20581
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20581.patch
>From 1fc2742ae595ae175eafca502b976bd8bfd19876 Mon Sep 17 00:00:00 2001
From: Andreas Rheinhardt
Date: Tue, 23 Sep 2025 05:40:39 +0200
Subj
PR #20580 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20580
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20580.patch
Get and set remote addr when dtls server mode.
(Refer to url_bio_bread in tls_openssl.c)
Add tls_handshake function.
TODO:
add
PR #20579 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20579
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20579.patch
The udp buffer size might be too small to easily
be full temporarily and return WSAEWOULDBLOCK.
The udp code will handle the windows
PR #20578 opened by Derek Buitenhuis (dwbuiten)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20578
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20578.patch
This was a regression introduced in 292c1df7c159c8a1a7afe52613d164ff417e81ce.
Since we don't know the length of the stts
PR #20576 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20576
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20576.patch
It may call the function multiple times.
>From 5f80608feca66b611cf863b6f46357b32fd8709c Mon Sep 17 00:00:00 2001
From: Andreas Rheinhardt
D
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
F
PR #20574 opened by Sean McGovern (sean_mcg)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20574
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20574.patch
From d84eeb1624517d15efae08afb04df3cfdaf01e2a Mon Sep 17 00:00:00 2001
From: Sean McGovern
Date: Mon, 22 Sep 2025 08:31:16 -0400
On Mon, 22 Sep 2025, harish.rajaselvan--- via ffmpeg-devel wrote:
I have been working on enabling ARM64EC compilation and have
successfully built FFmpeg binaries for this target. To achieve this it
required modifications to the build configuration files and to the
gas-preprocessor.pl script
if (hwcap & HWCAP_ ## cap) \
+if (hwcap & HWCAP_ARM_ ## cap) \
flags |= AV_CPU_FLAG_ ## flag; \
} while (0)
--
2.51.0
___
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
changed, 9 insertions(+), 3 deletions(-)
LGTM
// Martin
___
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
return flags;
#define check_cap(cap, flag) do { \
--
2.51.0
___________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
PR #20570 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20570
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20570.patch
Fixes: ../configure: 7820: [: Illegal number: 13-win32
Signed-off-by: Michael Niedermayer
>From 45a2307024ce23bbc29a425159f73a77c3b0ac10
PR #20569 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20569
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20569.patch
>From 161f9ab8166dc673b226f790a23113a15c6c23a1 Mon Sep 17 00:00:00 2001
From: Zhao Zhili
Date: Mon, 22 Sep 2025 00:42:02 +0800
Subj
PR #20568 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20568
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20568.patch
simply updated and rebased to current git master
is it ok as is or should we ignore ANMF chunks if strict_std_compliance
PR #20567 opened by Vittorio Palmisano (vpalmisano)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20567
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20567.patch
avfilter/af_whisper: fix srt index
The srt index should be incremented for each segment.
>F
PR #20566 opened by Vittorio Palmisano (vpalmisano)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20566
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20566.patch
avfilter/af_whisper: fix srt index and int64 printf format
- Use PRId64 for printing int64_t values in the SRT output
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/libavfo
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.
>F
ess %d is of incorrect
protocol family\n", i + 1);
--
2.51.0
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
PR #20494 opened by tmatth
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20494
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20494.patch
Benched on SpaceMIT for VLEN 256
Reviewed-by: Nathan E. Egge
C RVV256
pred8x8_horizontal_8: 36.4
ts: 0.00 pos:901 size:
27837
--
2.46.0.windows.1
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
re at most the provided amount of bytes in a
cluster", OFFSET(cluster_size_limit),
AV_OPT_TYPE_INT , { .i64 = -1 }, -1, INT_MAX, FLAGS },
{ "cluster_time_limit", "store at most the provided number of
milliseconds in a cluster",
OFFSET(cluster_time_limit), AV_OPT_TYPE_INT64, { .i64 = -1 }, -1, INT64_MAX,
FLAGS },
--
2.46.0.windows.1
___
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
slave owners. -- Vladimir Lenin
signature.asc
Description: PGP signature
___
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
PR #20565 opened by rcombs
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20565
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20565.patch
Adds support for decoding animated webp files.
This is a revised version of the patch from
https://patchwork.ffmpeg.org/project/ffmpeg/patch
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
PR #20493 opened by jianhuaw
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20493
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20493.patch
The tiff reads the icc profile to the side data but doesn't write the icc
profile from side data to the TIFF_ICC_PROFILE.
Signed-off-b
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 #20563 opened by welder
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20563
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20563.patch
The primary optimization is to load the first row before entering the loop
instead of loading two rows each iteration.
>F
Timo Rothenpieler via ffmpeg-devel (HE12025-09-18):
> The problem is they can be very frequent. And not only force pushes.
> So the current implementation is a compromise between visibility and
> spam-level.
They are not more frequent than v2, v3, etc., used to be, and therefore
below a
bug tracking for the time being.
I am also neutral on GitLab vs ForgeJo - I think both systems have their
strengths and weaknesses, although it appears simpler to smooth out ForgeJo's
bugs than to modify GitLab's monolithic codebase.
_______
ffmpeg-devel m
PR #20561 opened by Lynne
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20561
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20561.patch
This PR adds support for the Panasonic V-Log transfer function, used in
Panasonic cameras.
To avoid bloating structures unnecessarily, the
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&#
> On Sep 20, 2025, at 14:06, 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 | 3 ++-
> 1 file changed, 2 insertions(+), 1 dele
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
PR #20559 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20559
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20559.patch
Fixes: out of array read
Fixes: BIGSLEEP-445383648
Fixes: crash_input_1/2/3.dhav
Found-by: Google Big Sleep
Signed-off-by: Michael Niedermayer
PR #20560 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20560
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20560.patch
Signed-off-by: Michael Niedermayer
>From 798c4c50d53a01eb24f172575869738c9e26d93c Mon Sep 17 00:00:00 2001
From: Michael Niedermayer
D
ports supplying the interface based on its
* address. */
-int i;
for (i = 0; i < nb_sources; i++) {
struct group_source_req mreqs;
int level = addr->sa_family == AF_INET ? IPPROTO_IP : IPPROTO_IPV6;
--
2.51.0
_____
PR #20557 opened by frankplow
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20557
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20557.patch
This loosens the coupling between CBS and the decoder by no longer using
`CodedBitstreamH266Context` (containing the most recently parsed PSs
PR #20556 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20556
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20556.patch
Also a bit mccdec.
>From 8e4cbb053bd2dd9c345701e940e5ff4ec2eca766 Mon Sep 17 00:00:00 2001
From: Andreas Rheinhardt
Date: Fri, 19 Sep 2025 19
PR #20555 opened by Marton Balint (cus)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20555
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20555.patch
This removes lots of parsing code duplications, unifies parsing rules and also
enhances the documentation.
Some notable changes, some
PR #20552 opened by ArazIusubov
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20552
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20552.patch
Implement AV1 hardware encoding using Direct3D 12 Video API (D3D12VA).
D3D12 AV1 headers are available starting with Windows SDK 10.0.26100
{
0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x0a,0x04,0x01,0x02,0x02,0x01,0x01,0x5C,0x00
},
mxf_write_s436m_anc_desc },
___
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
On Tue, Sep 16, 2025 at 10:49:00AM +0200, 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 tes
han 32 bit timecodes
The last 2 patches adds timecode support in Matroska
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
PR #20551 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20551
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20551.patch
The existing is_luma check is fragile as depending on the order
of channels it can be set or reset
No testcase
Signed-off-by: Michael
PR #20550 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20550
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20550.patch
>From 38d62a1a51a84e220b6dbeaefd961f170d2d5c72 Mon Sep 17 00:00:00 2001
From: Michael Niedermayer
Date: Thu, 18 Sep 2025 17:32:46 +0200
Subj
Hi Martin
On Tue, Sep 16, 2025 at 10:54:19PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote:
>
> > On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel
> > wrote:
> > > On Tue, 16 Se
Hi,
I currently work on VVC implementation on Amlogic platform. There we use ffmpeg
to demux the stream.
All other codecs like h264 or h265 do have codec parameters extra data:
https://github.com/xbmc/xbmc/blob/master/xbmc/cores/VideoPlayer/DVDDemuxers/DVDDemuxFFmpeg.cpp#L2377
Is there just no
mån 2025-09-15 klockan 10:26 -0300 skrev Helmuth Schmitz via ffmpeg-
devel:
> The first UL of the SMPTE 436M descriptor triple in mxfenc.c used
> 0x0a
> instead of 0x09. This caused generated MXF files without "MXF-GC
> Generic
> ANC
> Data Mapping" essence container
fre 2025-09-12 klockan 15:09 + skrev Niklas Haas via ffmpeg-devel:
> 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
On Thu, 18 Sep 2025, Timo Rothenpieler via ffmpeg-devel wrote:
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
PR #20549 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20549
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20549.patch
Right now, the private contexts of every decoder supporting
H.274 film grain synthesis (namely H.264, HEVC and VVC)
contain a H274FilmGrainDatabase
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
On Mon, Sep 15, 2025 at 02:57:53PM +0200, 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:
> [...]
> > > I
On September 18, 2025 2:15:22 AM PDT, Nicolas George via ffmpeg-devel
wrote:
> If this web monster does not let you push code in your private fork
> without asking to include it upstream, it is one more reason not to use
> that thing.
It does let you push to your private for
PR #20548 opened by mkver
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20548
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20548.patch
This reverts commits fd55c4b5f72a157fbb128d0ef203e9922b53552b
(for tls_openssl.c) and c74181a04b5f4e650eae662231e56518daef64d4
(for tls_gnutls.c
it.
2. Add new sample via sending PR to this fate-suit repo.
3. Add cross link and rerun CI manually in FFmpeg repo’s PR after fate-suit’s
PR merged.
Maybe there are more simpler methods to do that.
So far all methods I could think of were more or less the same level of
effort than the curren
On Thu, 18 Sep 2025 01:52:31 -0700 Jacob Lifshay via ffmpeg-devel
wrote:
> On Thu, Sep 18, 2025 at 12:03 AM Nicolas George via ffmpeg-devel
> wrote:
> >
> > Timo Rothenpieler via ffmpeg-devel (HE12025-09-18):
> > > The problem is they can be very frequent. And not
PR #20547 opened by add-uos-ffmpeg
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20547
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20547.patch
Add a separator line to show_filters() function output to maintain
consistent formatting with other show functions like show_codecs
Jacob Lifshay via ffmpeg-devel (HE12025-09-18):
> I don't know about you, but whenever I'm developing code, I sometimes
> push new changes multiple times in a day and then only ask for more
> review after I'm done developing whatever thing I'm working on, maybe
> af
sample via sending PR to this fate-suit repo.
3. Add cross link and rerun CI manually in FFmpeg repo’s PR after fate-suit’s
PR merged.
Maybe there are more simpler methods to do that.
___
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe
On 2025-09-16 02:19 pm, 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 Sep 17, 2025, at 22:44, Niklas Haas via ffmpeg-devel
> wrote:
>
> 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
On Thu, Sep 18, 2025 at 12:03 AM Nicolas George via ffmpeg-devel
wrote:
>
> Timo Rothenpieler via ffmpeg-devel (HE12025-09-18):
> > The problem is they can be very frequent. And not only force pushes.
> > So the current implementation is a compromise between visibility
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 li
e 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 neater than at
> first expected.
>
> * if we switch back to the ML, we still could have subsystem
> maintaine
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
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
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 #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
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
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 -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
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
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
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
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
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
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 havi
> -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
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.
>
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
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
PR #20538 opened by James Almer (jamrial)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20538
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20538.patch
Don't keep around information from a previous traf atom.
Fixes issue #20492.
>From 9c18a8d1802726c7d59c5d067890b7f2f8c7
; bug submission page...
Cheers!
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote:
On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel wrote:
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
iling
list for code review.
// Martin
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
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
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
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
Hi Alexander
On Tue, Sep 16, 2025 at 03:59:38PM +0200, Alexander Strasser via ffmpeg-devel
wrote:
> On 2025-09-16 10:49 +0200, Michael Niedermayer via ffmpeg-devel wrote:
> >
> [...]
> >
> > * If we keep forgejo we will likely transition our issue tracker ticket
Hi Martin
On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> 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 t
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
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
>From f46d078521e6ce8fe2ce2648ae7d29367eb9c928 Mon Sep 17 00:00:00 2001
From: Lynne
Date: Wed, 27 Aug 2025 17:39:16 +0900
Subject: [PATCH 1/6] l
+return -1;
+}
c->found_mdat=1;
return 0; /* now go for moov */
}
--
2.34.1
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
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 want to eventually retire it.
btw, anyone kno
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
/ "Forgejo" 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)
F (Keep Forgejo)
__
Any vote on anything that can be even potentially contentious should be
made with closed voting, not requiring everybody to publicly state their
preference.
// Martin
_______
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-le...@ffmpeg.org
1 - 100 of 2180 matches
Mail list logo
