Fixed in v3. Feel free to reword the log message (not sure if this can be done
in forgejo before merge).
---
View it on FFmpeg Forgejo (
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20020#issuecomment-379 ) or reply
to this email directly.
___
ffmpeg-d
*quink* force-pushed the *bugfix-mxf* from *9c38dc581f* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/9c38dc581f388b0dea90f0ff2307fa490864f7c1
) to *cafe808c70* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/cafe808c700e2566d62e6b85da1e8fd902b60ada
).
---
View it on FFmpeg Forgejo (
https://
*kasper93* force-pushed the *cov_report* from *7e2f0cb9a2* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7e2f0cb9a212ec5f82faa41bdb70f619c3d6c9f0
) to *1d7ca722bd* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/1d7ca722bd7d2a31efc30fb9a635dedbb789af19
).
---
View it on FFmpeg Forgejo (
https
*kasper93* force-pushed the *cov_report* from *af5e035c87* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/af5e035c8736b8f58657541eecaf347877d47f67
) to *7e2f0cb9a2* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7e2f0cb9a212ec5f82faa41bdb70f619c3d6c9f0
).
---
View it on FFmpeg Forgejo (
https
*kasper93* force-pushed the *cov_report* from *ef39d2d144* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/ef39d2d144658a1fb37ea0fc2cc3ebb435a355fb
) to *af5e035c87* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/af5e035c8736b8f58657541eecaf347877d47f67
).
---
View it on FFmpeg Forgejo (
https
On Thu, 24 Jul 2025 at 03:39, kasper93 wrote:
>
> *kasper93* force-pushed the *cov_report* from *d1d6603b3b* (
> https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/d1d6603b3bdd98270cbac44c5384f575879c17c7
> ) to *ef39d2d144* (
> https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/ef39d2d144658a1fb37ea0fc2cc
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
getting contributions, then either
*kasper93* force-pushed the *cov_report* from *d1d6603b3b* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/d1d6603b3bdd98270cbac44c5384f575879c17c7
) to *ef39d2d144* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/ef39d2d144658a1fb37ea0fc2cc3ebb435a355fb
).
---
View it on FFmpeg Forgejo (
https
*kasper93* force-pushed the *cov_report* from *7d134c6292* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7d134c629254571796cc8044af8d550a40ae7f3a
) to *d1d6603b3b* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/d1d6603b3bdd98270cbac44c5384f575879c17c7
).
---
View it on FFmpeg Forgejo (
https
*kasper93* force-pushed the *cov_report* from *7a30756f57* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7a30756f579fc0ac86bed3c8c94723ca6c25979f
) to *7d134c6292* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7d134c629254571796cc8044af8d550a40ae7f3a
).
---
View it on FFmpeg Forgejo (
https
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.
__
*kasper93* force-pushed the *cov_report* from *b17f8b26f2* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/b17f8b26f2372e70e51e2d48049785f50074ce61
) to *7a30756f57* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/7a30756f579fc0ac86bed3c8c94723ca6c25979f
).
---
View it on FFmpeg Forgejo (
https
On 7/23/2025 11:01 AM, Niklas Haas wrote:
On Wed, 23 Jul 2025 16:01:14 +0200 Niklas Haas wrote:
On Wed, 23 Jul 2025 13:43:43 +0200 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 follow
*kasper93* force-pushed the *cov_report* from *5112eb49c2* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/5112eb49c28140a7d30a7ec179d67b437fda394b
) to *b17f8b26f2* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/b17f8b26f2372e70e51e2d48049785f50074ce61
).
---
View it on FFmpeg Forgejo (
https
*@kasper93* created #20027.
---
View it on FFmpeg Forgejo ( https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20027 )
or reply to this email directly.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To u
On Wed, Jul 23, 2025 at 11:19:57AM -0700, Jacob Lifshay wrote:
>
>
> On July 23, 2025 10:48:51 AM PDT, Michael Niedermayer
> wrote:
> > On Wed, Jul 23, 2025 at 06:43:51PM +0200, Dimitry Andric wrote:
> > > As long as there is a command line option to disable checking, it should
> > > be a good
On Wed, Jul 23, 2025 at 08:40:22PM +0200, Nicolas George wrote:
> Michael Niedermayer (HE12025-07-23):
> > the fix for this is to check crt.sh
> >
> > example: https://crt.sh/?q=ffmpeg.org
> >
> > and if there are or where correct certificates, reject the self signed one
> > otherwise allow self
On July 23, 2025 3:06:40 PM PDT, Timo Rothenpieler
wrote:
> I've registered a dummy-user with the ffmpeg-devel address as its E-Mail and
> subscribed it to all the repo notifications.
>
> So things will get forwared to the ML via it now.
It seems to not be working, since you sent this I've got
The new logic should be easier to follow.
It also uses ff_inlink_consume_frame() for all simple passthrough operations
making custom get_audio_buffer callback unnecessary.
Fate changes are because the new logic does not repacketize input audio up
until the crossfade. Content is the same.
Signed-
Use ff_outlink_get_status directly to get pending EOF state.
Fixes assertion failure with:
ffmpeg -lavfi
"sine=f=1000:d=2[a];sine=f=440:d=2,atrim=end=0[b];[a][b]acrossfade=d=1" -f
framecrc -
ffmpeg -lavfi
"sine=f=1000:d=2,atrim=end=0[a];sine=f=440:d=2[b];[a][b]acrossfade=d=1" -f
framecrc -
Si
No change in functionality.
Signed-off-by: Marton Balint
---
libavfilter/af_afade.c | 206 ++---
1 file changed, 111 insertions(+), 95 deletions(-)
diff --git a/libavfilter/af_afade.c b/libavfilter/af_afade.c
index a9318c0ac5..b006420111 100644
--- a/libavfil
There is no benefit in delaying processing all available frames.
Signed-off-by: Marton Balint
---
libavfilter/trim.c | 42 +-
1 file changed, 17 insertions(+), 25 deletions(-)
diff --git a/libavfilter/trim.c b/libavfilter/trim.c
index 7200680716..6d1016ac
*@cus* commented on this pull request.
Otherwise looks good.
In libavformat/mxfenc.c:
diff --git a/libavformat/mxfenc.c b/libavformat/mxfenc.c
--- a/libavformat/mxfenc.c
+++ b/libavformat/mxfenc.c
@@ -1985,2 +1985,3 @@
-static void mxf_write_index_table_segment(AVFormatContext *s)
+static inline
On Wed, 23 Jul 2025, Tomas Härdin wrote:
ons 2025-07-23 klockan 13:45 +0200 skrev Michael Niedermayer:
Fixes: read of uninitialized memory
Fixes: 391916474/clusterfuzz-testcase-minimized-
ffmpeg_dem_MXF_fuzzer-4935250956845056
Found-by: continuous fuzzing process
https://github.com/google/os
*kasper93* force-pushed the *add_lrc_ms* from *040266fe08* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/040266fe08d67815244d23865e79804fce8fe065
) to *2aaa900abf* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/2aaa900abf62699e1c0bbe59b136018696c219f2
).
---
View it on FFmpeg Forgejo (
https
*@kasper93* pushed 1 commit to add_lrc_ms
* 040266fe08 (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/040266fe08d67815244d23865e79804fce8fe065
) - [DO NOT MERGE] fate-staging: add local fate samples
---
View it on FFmpeg Forgejo (
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20025#issuecomment-
This patchset adds new boxes and projection values from from
https://developer.apple.com/av-foundation/Stereo-Video-ISOBMFF-Extensions.pdf
Vittorio Giovara (2):
mov: Export frame packing information from pack box
lavu/spherical: Add support for Spherical Immersive type
libavformat/mov.c
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
*kasper93* force-pushed the *add_lrc_ms* from *c38b10f751* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/c38b10f7518c96a9b292293913ddb3685009f300
) to *2785182fda* (
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/2785182fda0e91f45a67491dc3508e814d9c
).
---
View it on FFmpeg Forgejo (
https
On July 23, 2025 1:01:32 PM PDT, "Tomas Härdin" wrote:
> Perhaps I should have made it clear that I'm just spitballing what kind
> of workflows we should keep in mind with this stuff. I'm not suggesting
> we need to add support for everything right away. Just that we should
> take steps toward a s
On 7/23/2025 4: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
ons 2025-07-23 klockan 13:45 +0200 skrev Michael Niedermayer:
> Fixes: read of uninitialized memory
> Fixes: 391916474/clusterfuzz-testcase-minimized-
> ffmpeg_dem_MXF_fuzzer-4935250956845056
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
tis 2025-07-22 klockan 13:56 -0700 skrev Jacob Lifshay:
> On July 22, 2025 5:21:24 AM PDT, "Tomas Härdin"
> > * combining 436M and video essence to a full frame for playout
> iirc ffmpeg architecturally doesn't support merging a 608 stream into
> video side data since bitstream filters only have
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
notifications or it should be made very clear here, rep
Le sam. 21 juin 2025 à 16:59, Michael Niedermayer
a écrit :
>
> On Sat, Jun 21, 2025 at 10:45:32AM +0200, Romain Beauxis wrote:
> > Le dim. 15 juin 2025 à 00:57, Michael Niedermayer
> > a écrit :
> > >
> > > On Wed, Jun 04, 2025 at 11:58:52AM -0500, Romain Beauxis wrote:
> > > > This is a redo of
Michael Niedermayer (HE12025-07-23):
> the fix for this is to check crt.sh
>
> example: https://crt.sh/?q=ffmpeg.org
>
> and if there are or where correct certificates, reject the self signed one
> otherwise allow self signed by default with a warning
“502 Bad Gateway” I doubt it can be a fix fo
On July 23, 2025 10:48:51 AM PDT, Michael Niedermayer
wrote:
> On Wed, Jul 23, 2025 at 06:43:51PM +0200, Dimitry Andric wrote:
> > As long as there is a command line option to disable checking, it should
> > be a good default.
>
> > There are many sites out there with badly configured
> > cer
Hi,
Pinging this patch from a couple weeks ago. To be clear, I am not sure
how people typically use ffmpeg's ID3v2 support, so please let me know
if the patch is missing something and I'm happy to iterate on it, but
it does seem to me that trying to parse it from rawvideo inputs is
wrong.
Thank y
On Wed, Jul 23, 2025 at 06:43:51PM +0200, Dimitry Andric wrote:
> On 23 Jul 2025, at 18:27, Michael Niedermayer wrote:
> >
> > On Wed, Jul 23, 2025 at 03:45:28PM +0200, Timo Rothenpieler wrote:
> >> On 23/07/2025 13:43, Michael Niedermayer wrote:
> >>> Hi everyone
> >>>
> >>> I intend to create
Niklas Haas (HE12025-07-23):
> [PATCH v2 05/18] avcodec/encode: enforce alpha mode compatibility at encode
> time
That handles it for encoders, I suppose. But I do not see anything
protecting you from stacking images with different kind of alpha or
sending this kind of frames to a muxer with unco
On 23 Jul 2025, at 18:27, Michael Niedermayer wrote:
>
> On Wed, Jul 23, 2025 at 03:45:28PM +0200, Timo Rothenpieler wrote:
>> 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 t
On Wed, Jul 23, 2025 at 03:45:28PM +0200, Timo Rothenpieler wrote:
> 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
On Wed, 23 Jul 2025 at 15:57, Niklas Haas wrote:
>
> From: Niklas Haas
>
> This header bit ("alpha_associated") was incorrectly ignored.
> ---
> libavcodec/jpegxl_parse.c | 7 +--
> libavcodec/jpegxl_parse.h | 1 +
> libavcodec/jpegxl_parser.c | 5 +
> 3 files changed, 11 insertions(+)
On Wed, 23 Jul 2025 at 15:57, Niklas Haas wrote:
>
> From: Niklas Haas
>
> ---
> libavfilter/vf_showinfo.c | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_showinfo.c
> index c706d00c96..b564d03a84 100644
> --- a/libavfilter/vf_showinfo.
On Wed, 23 Jul 2025 at 15:56, Niklas Haas wrote:
>
> From: Niklas Haas
>
> FFmpeg currently handles alpha in a quasi-arbitrary way. Some filters/codecs
> assume alpha is premultiplied, others assume it is independent. If there is
> to be any hope for order in this chaos, we need to start by defin
On Wed, 23 Jul 2025 at 10:43, Michael Niedermayer
wrote:
>
> Fixes: use of uninitialized memory
> Fixes:
> 403675492/clusterfuzz-testcase-minimized-ffmpeg_dem_ASF_fuzzer-4754281823797248
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> S
On Wed, 23 Jul 2025 16:11:45 +0200 Nicolas George wrote:
> Niklas Haas (HE12025-07-23):
> > Changes since v1:
> > - Correctly implement alpha mode tagging for JPEG XL
> > - Set correct alpha mode for OpenEXR (which is always premultiplied)
> > - Ensure -alpha_mode specified on the command line cor
Niklas Haas (HE12025-07-23):
> Changes since v1:
> - Correctly implement alpha mode tagging for JPEG XL
> - Set correct alpha mode for OpenEXR (which is always premultiplied)
> - Ensure -alpha_mode specified on the command line correctly propagates
> - Print out a warning when overriding the alpha
On Wed, 23 Jul 2025 16:01:14 +0200 Niklas Haas wrote:
> On Wed, 23 Jul 2025 13:43:43 +0200 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 th
On Wed, 23 Jul 2025 13:43:43 +0200 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
>
From: Niklas Haas
Error out if trying to encode frames with an incompatible alpha mode.
---
libavcodec/encode.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/libavcodec/encode.c b/libavcodec/encode.c
index 38833c566c..9012708130 100644
--- a/libavcodec/encode.c
From: Niklas Haas
---
fftools/ffmpeg_enc.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/fftools/ffmpeg_enc.c b/fftools/ffmpeg_enc.c
index 4568c15073..babfca6c0a 100644
--- a/fftools/ffmpeg_enc.c
+++ b/fftools/ffmpeg_enc.c
@@ -287,6 +287,17 @@ int enc_open(void *opaque, const
From: Niklas Haas
Chooses the desired output alpha mode. Note that this depends on
an upstream version of libplacebo new enough to respect the corresponding
AVFrame field in pl_map_avframe_ex.
---
doc/filters.texi| 4
libavfilter/vf_libplacebo.c | 13 +
2 files chan
From: Niklas Haas
---
libavfilter/vf_premultiply.c | 8
1 file changed, 8 insertions(+)
diff --git a/libavfilter/vf_premultiply.c b/libavfilter/vf_premultiply.c
index 322fc39094..1c08cf524a 100644
--- a/libavfilter/vf_premultiply.c
+++ b/libavfilter/vf_premultiply.c
@@ -512,6 +512,7 @@
From: Niklas Haas
---
doc/filters.texi | 13 +
libavfilter/vf_setparams.c | 10 ++
2 files changed, 23 insertions(+)
diff --git a/doc/filters.texi b/doc/filters.texi
index fbf8aff382..13ca065f85 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -21602,6 +2160
From: Niklas Haas
---
libavfilter/vf_alphamerge.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavfilter/vf_alphamerge.c b/libavfilter/vf_alphamerge.c
index f5779484a9..98c61e282d 100644
--- a/libavfilter/vf_alphamerge.c
+++ b/libavfilter/vf_alphamerge.c
@@ -85,6 +85,8 @@ static int d
From: Niklas Haas
---
doc/filters.texi | 3 +-
libavfilter/vf_overlay.c | 199 --
libavfilter/vf_overlay.h | 4 +-
libavfilter/x86/vf_overlay_init.c | 8 +-
4 files changed, 116 insertions(+), 98 deletions(-)
diff --git a/doc/
From: Niklas Haas
This code always ignored the user-provided enc_ctx->chroma_sample_location
in favor of the location tagged on the frame. This leads to a very (IMHO)
unexpected outcome where -chroma_sample_location works differently from the
related options like -colorspace and -color_range, the
From: Niklas Haas
Works around a bug where older versions of libjxl don't correctly forward
the alpha channel information to the extra channel info.
---
libavcodec/libjxlenc.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/libavcodec/libjxlenc.c b/libavcodec/libjxlenc.c
index
From: Niklas Haas
PNG always uses straight alpha.
cf. https://www.w3.org/TR/PNG-Rationale.html
> Although each form of alpha storage has its advantages, we did not want to
> require all PNG viewers to handle both forms. We standardized on non-
> premultiplied alpha as being the lossless and mor
From: Niklas Haas
OpenEXR always uses premultiplied alpha, as per the spec.
cf. https://openexr.com/en/latest/TechnicalIntroduction.html
> By convention, all color channels are premultiplied by alpha, so that
> `foreground + (1-alpha) x background` performs a correct “over” operation.
> (See Pr
From: Niklas Haas
JPEG XL supports both premultiplied and straight alpha, and the basic info
struct contains signalling for this. Forward the correct tagging on decode
and encode.
---
libavcodec/libjxldec.c | 6 ++
libavcodec/libjxlenc.c | 15 +++
2 files changed, 21 insertions(
From: Niklas Haas
This header bit ("alpha_associated") was incorrectly ignored.
---
libavcodec/jpegxl_parse.c | 7 +--
libavcodec/jpegxl_parse.h | 1 +
libavcodec/jpegxl_parser.c | 5 +
3 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/libavcodec/jpegxl_parse.c b/libavcod
From: Niklas Haas
This filter was, for some reason, always ignoring the incoming chroma
location in favor of the user-specified value, even when that value was set
to the default (unspecified).
This has been the status quo for quite some time, although commit 04ce01df0bb
made the situation worse
From: Niklas Haas
Following in the footsteps of the previous commit, this commit adds the
new fields to AVCodecContext so we can start properly setting it on codecs,
as well as limiting the list of supported options to detect a format mismatch
during encode.
This commit also sets up the necessar
From: Niklas Haas
---
libavfilter/vf_showinfo.c | 8
1 file changed, 8 insertions(+)
diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_showinfo.c
index c706d00c96..b564d03a84 100644
--- a/libavfilter/vf_showinfo.c
+++ b/libavfilter/vf_showinfo.c
@@ -887,6 +887,14 @@ static int fi
From: Niklas Haas
FFmpeg currently handles alpha in a quasi-arbitrary way. Some filters/codecs
assume alpha is premultiplied, others assume it is independent. If there is
to be any hope for order in this chaos, we need to start by defining an enum
for the possible range of values.
---
doc/APIcha
Changes since v1:
- Correctly implement alpha mode tagging for JPEG XL
- Set correct alpha mode for OpenEXR (which is always premultiplied)
- Ensure -alpha_mode specified on the command line correctly propagates
- Print out a warning when overriding the alpha mode explicitly
Includes an unrelated
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 Jul 22, 2025, at 20:43, Timo Rothenpieler wrote:
>
> 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/libavfo
Signed-off-by: Jack Lau
---
Changelog | 1 +
1 file changed, 1 insertion(+)
diff --git a/Changelog b/Changelog
index 228029ea00..1c6c27919f 100644
--- a/Changelog
+++ b/Changelog
@@ -2,6 +2,7 @@ Entries are sorted chronologically from oldest to youngest
within each release,
releases are sorted
---
libavutil/hwcontext_d3d12va.c | 17 -
libavutil/hwcontext_d3d12va.h | 11 +++
2 files changed, 27 insertions(+), 1 deletion(-)
diff --git a/libavutil/hwcontext_d3d12va.c b/libavutil/hwcontext_d3d12va.c
index 6507cf69c1..dca8ddc0c3 100644
--- a/libavutil/hwcontext_d3d12
Michael Niedermayer (HE12025-07-23):
> 2. hire more reviewers/maintainers, so we have more manpower, FFlabs and STF
> are
>options here, both these options should be used.
It seems to me that the influence of FFlabs on the project has done much
more harm than good, especially with regard to o
Michael Niedermayer (HE12025-07-23):
> Let me quote the president and CEO:
>
> "The company is just a way to finance the community to work on the same
> things as usual."
>
> and
>
> "To me, the company should be transparent to the project. It's just a way
> to funnel money to the community."
Fixes: read of uninitialized memory
Fixes:
391916474/clusterfuzz-testcase-minimized-ffmpeg_dem_MXF_fuzzer-4935250956845056
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/mxfdec.c | 4 +++-
1
Fixes: use of uninitialized memory
Fixes:
412125811/clusterfuzz-testcase-minimized-ffmpeg_dem_VQF_fuzzer-6253774274887680
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/vqf.c | 4 +++-
1 fil
Fixes: use of uninitialized memory
Fixes:
394990189/clusterfuzz-testcase-minimized-ffmpeg_dem_MOV_fuzzer-6431722199908352
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/mov.c | 4 +++-
1 fil
Fixes: use of uninitialized memory
Fixes:
378102648/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_HEVC_fuzzer-5896308499480576
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/hevc/hevcdec.
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.
And if theres a bugfix that you want included make sure it either
Signed-off-by: Dariusz Frankiewicz
---
configure | 2 +-
libavcodec/liboapvenc.c | 24
2 files changed, 25 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index ac143f2fea..5527c20578 100755
--- a/configure
+++ b/configure
@@ -6983,7 +6983,
Update: the correct time base is stored inside inlink->time_base, not
in frame->time_base
On Wed, Jul 23, 2025 at 12:19 PM Vittorio Palmisano
wrote:
>
> > > To understand why this is a problem, consider some audio input device
> > > which samples at 16khz. This hardware contains lets say for simp
> > To understand why this is a problem, consider some audio input device
> > which samples at 16khz. This hardware contains lets say for simplicity a
> > 16khz
> > crystal and samples based on that. But depending on temperature of this
> > crystal it will really sample lets say between 15990 and
On Wed, Jul 23, 2025 at 10:59 AM Michael Niedermayer
wrote:
>
> Hello Kieran
>
> On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> > >
> > >
> > >
> > > About 2. (IMHO)
> > > * The solution is to hire carl or someone else (or find a volunteer)
> > > to do this
Hello Kieran
On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> >
> >
> >
> > About 2. (IMHO)
> > * The solution is to hire carl or someone else (or find a volunteer)
> > to do this work. Changing the tracker will not fix this.
> >
> > FFlabs should have enough
When CONFIG_H261_DECODER, CONFIG_H263_DECODER, and CONFIG_MPEG4_DECODER are set
to 0 by default, resulting in a "statement will never be executed" warning
during compilation. To enhance code robustness, this patch fixes the warning.
Signed-off-by: zhaozhenghang <15083277...@163.com>
---
libavfo
On Wed, 23 Jul 2025 05:30:57 + Sarthak Indurkhya via ffmpeg-devel
wrote:
> Thank you for the thoughtful feedback.
>
> Advantages over vf_libplacebo’s inverse tone mapping:
>
> 1. Algorithmic Differentiation:
> My filter is based on a novel local adaptation + inverse tone mapping
> strateg
>
>
>
> About 2. (IMHO)
> * The solution is to hire carl or someone else (or find a volunteer)
> to do this work. Changing the tracker will not fix this.
>
> FFlabs should have enough captial to hire carl for this. People should
> ask
> FFlabs to hire him and carl to accept to be hired for t
Hi Lynne
On Wed, Jul 23, 2025 at 01:01:06PM +0900, Lynne wrote:
>
>
> On 23/07/2025 08:04, Michael Niedermayer wrote:
> > Hi Lynne
> >
> > On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:
[...]
> > > +
> > > +We are also hoping that this will significantly reduce the amount of
> >
Hi Lynne
On Wed, Jul 23, 2025 at 01:01:06PM +0900, Lynne wrote:
>
>
> On 23/07/2025 08:04, Michael Niedermayer wrote:
> > Hi Lynne
> >
> > On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:
> >
> > [...]
> >
> > > +
> > > +Bugs/issues will be accepted on > > href="https://code.ffmp
Hi,
I've applied some changes and created a pull request:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20022
>
> > +frames = FFMAX(0, FFMIN(frames, wctx->audio_buffer_fill_size));
>
> I would call it samples, sample_count or nb_samples
>
> why are you cliping the number of samples ?
>
> I assum
Fixes: use of uninitialized memory
Fixes:
403675492/clusterfuzz-testcase-minimized-ffmpeg_dem_ASF_fuzzer-4754281823797248
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/asfdec_f.c | 4 +++-
Please reword the commit subject description.
> On Jul 23, 2025, at 10:51, zhaozhenghang <15083277...@163.com> wrote:
>
> remove the conditional compilation inside the switch to avoid warnings.
>
> Signed-off-by: zhaozhenghang <15083277...@163.com>
> ---
> libavformat/mov.c | 10 ++
> 1 f
92 matches
Mail list logo
