PR #20135 opened by Gyan Doshi (GyanD)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20135
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20135.patch
>From 193f389793c9e7996a1a60d93fc89cde1acddf8b Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Wed, 6 Aug 2025 18:28:16 +0530
Subj
PR #20110 opened by Gyan Doshi (GyanD)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20110
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20110.patch
Time has to be expressed as timestamp x time base
Signed-off-by: GyanD
>From fb2038dc3e6bbcab1f73e2e39ece95588b1bccf4 Mon Sep 17
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?
Regards,
Gyan
To accomplish this, the source.ffmpeg.org domain will be shifted to
point to gi
On 2025-07-31 01:06 pm, 1+1=10 wrote:
If max_packet_size is -1, a crash will occur in the ffio_fdopen function due to
malloc(-1),
but max_packet_size is initialized to 0 in the url_alloc_for_protocol function.
If it is not customized to -1, this situation should not occur.
But your added op
On 2025-07-25 03:29 am, Jack Lau wrote:
Signed-off-by: Jack Lau
---
Changelog | 1 +
1 file changed, 1 insertion(+)
diff --git a/Changelog b/Changelog
index 228029ea00..27531ad0ab 100644
--- a/Changelog
+++ b/Changelog
@@ -25,6 +25,7 @@ version :
- APV in MP4/ISOBMFF muxing and demuxing
On 2025-07-17 07:35 pm, yangsen5 via ffmpeg-devel wrote:
From: yangsen5 <1441923...@qq.com>
Signed-off-by: yangsen5 <1441923...@qq.com>
---
libavformat/file.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavformat/file.c b/libavformat/file.c
index 6a66040b65..80
On 2025-07-13 05:13 pm, Michael Niedermayer wrote:
Hi all
Do people want Forgejo or Gitlab on code.ffmpeg.org for testing?
F. code.ffmpeg.org should run Forgejo
G. code.ffmpeg.org should run Gitlab
all GA members can vote, by publically replying here with a
"F." / "Forgejo" vs "G." / "Gitla
On 2025-07-08 06:45 am, Desmond Liu wrote:
Add missing 'gamma correct scaling' option to documentation.
Signed-off-by: Desmond Liu
---
doc/scaler.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/scaler.texi b/doc/scaler.texi
index eb045de6b7..a9ed10e34e 100644
--- a/doc/sca
On 2025-07-01 04:28 pm, Alexander Strasser via ffmpeg-devel wrote:
> Thus I want this thread to start a discussion, that eventually leads
> to a policy about submitting and integrating "AI" generated content.
In practice. unless a patch(set) is explicitly marked or has telltale
signs of bein
On 2025-06-26 12:16 pm, softworkz wrote:
From: softworkz
Signed-off-by: softworkz
---
doc/developer: Fix typos
Published-As:
https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-103%2Fsoftworkz%2Fsubmit_typos-v1
Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg
pr
On 2025-06-21 11:42 pm, compn wrote:
On Thu, 19 Jun 2025 15:04:27 +0530, Gyan Doshi wrote:
This source looks to be unmaintained since 2024 August.
The latest ffmpeg git master build is from 2024 June, and the latest
release build is 7.0.2, from 2024 August.
---
src/download | 2 --
1
This source looks to be unmaintained since 2024 August.
The latest ffmpeg git master build is from 2024 June, and the latest
release build is 7.0.2, from 2024 August.
---
src/download | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/download b/src/download
index 105eb56..46c581a 100644
--
On 2025-06-18 03:03 am, Tomas Härdin wrote:
fre 2025-06-13 klockan 20:07 +0530 skrev Gyan Doshi:
On 2025-06-13 04:25 pm, Tomas Härdin wrote:
The present level of
edit list support could be reimplemented by just fiddling with the
-ss
and -t options. That is, the ffmpeg CLI could
On 2025-06-16 11:34 pm, Niklas Haas wrote:
From: Niklas Haas
This otherwise generates an inconsistency between the frame state and the
link state, since the link state is set to 1:1 explicitly when `reset_sar`
is enabled, but this line of code unconditionally overwrote the output
frame SAR w
On 2025-06-15 09:17 pm, Clément Péron wrote:
On Sun, 15 Jun 2025 at 17:33, Gyan Doshi wrote:
On 2025-06-15 08:59 pm, Marth64 wrote:
thanks both
Pushed as 90424a447556c45f035a128d673607bff05d0fd6
Not an issue for me but just a remark the email is wrong: "Author:
Clément Péron &quo
On 2025-06-15 08:59 pm, Marth64 wrote:
thanks both
Pushed as 90424a447556c45f035a128d673607bff05d0fd6
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link
On 2025-06-15 08:41 pm, Clément Péron wrote:
usefull -> useful
seperately -> separately
reciever -> receiver
Will apply.
Regards,
Gyan
Signed-off-by: Clément Péron
---
doc/filters.texi| 2 +-
libavdevice/avfoundation.m | 4 ++--
libavfilter/vf_nlmeans_opencl.c |
On 2025-06-13 08:23 pm, Tomas Härdin wrote:
For now I'll probably dummy out elst support and the associated tests
just to make progress on segmented indexes.
Does `-ignore_editlist true` not work for your use-case?
Regards,
Gyan
___
ffmpeg-devel
On 2025-06-13 04:25 pm, Tomas Härdin wrote:
The present level of
edit list support could be reimplemented by just fiddling with the -ss
and -t options. That is, the ffmpeg CLI could automatically derive -ss
and -t from the edit list extracted by lavf.
In mov.c, edit lists are per-track and ca
On 2025-05-31 08:19 pm, Quentin RENARD wrote:
zoompan filter with floating point precision
If this filter is meant to be same as existing zoompan but more precise,
then you should modify the original filter with a mode option for FP use.
Regards,
Gyan
Signed-off-by: Quentin Renard
On 2025-05-26 06:17 pm, Martin Storsjö wrote:
On Mon, 26 May 2025, Gyan Doshi wrote:
Usage of hybrid_fragmented and faststart together can result in files
with
loss of sync and bitstream parsing errors upon playback.
---
libavformat/movenc.c | 6 ++
1 file changed, 6 insertions(+)
diff
Usage of hybrid_fragmented and faststart together can result in files with
loss of sync and bitstream parsing errors upon playback.
---
libavformat/movenc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index 4bc8bd1b2a..9392ba5370 100644
---
On 2025-05-18 02:17 pm, Gyan Doshi wrote:
Only encoding support has been added for liboapv
Pushed as c55d65ac0a789c23192aa555d8c1da399cee71aa
Regards,
Gyan
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 0609dac4ab
Only encoding support has been added for liboapv
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 0609dac4ab..30063e6b34 100755
--- a/configure
+++ b/configure
@@ -249,7 +249,7 @@ External library support:
--enable-liblensfun ena
On 2025-05-16 01:20 pm, softworkz . wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of Martin
Storsjö
Sent: Freitag, 16. Mai 2025 08:22
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/graphprint: Now, make it a
Killer-Feature!
On Thu, 15 May 20
On 2025-04-26 12:53 am, Marton Balint wrote:
On Thu, 24 Apr 2025, Gyan Doshi wrote:
On 2025-04-24 02:05 am, Marton Balint wrote:
On Wed, 23 Apr 2025, cenzhanqu...@gmail.com wrote:
From: zhanquan cen
1. add simple fade when volume.
2. do fade when adjust volume to maximal
On 2025-04-24 02:05 am, Marton Balint wrote:
On Wed, 23 Apr 2025, cenzhanqu...@gmail.com wrote:
From: zhanquan cen
1. add simple fade when volume.
2. do fade when adjust volume to maximal.
when to adjust volume we hope that the audio sample is smooth
we need to calculate the gradient st
On 2025-04-23 02:26 am, Marvin Scholz wrote:
Given the readrate catchup is input-specific, it seems to make sense to
also warn on a per-input demux basis.
We want to warn once each time reading is resumed but only for the first
stream resumption. That's the case right now.
With this change,
On 2025-04-21 11:59 pm, Stefano Sabatini wrote:
On date Tuesday 2025-04-15 16:09:56 +0530, Gyan Doshi wrote:
Utility function to report seekability features for a given input.
Useful for ffprobe and to extend seek possibilities in fftools.
---
v2:
made constants more descriptive
add
On Mon, 21 Apr 2025, softworkz . wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of
Gyan
Doshi
Sent: Montag, 21. April 2025 06:51
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/dump: Change
precision
of
stream start offsets
On 2025-04-21 01:41
On 2025-04-21 01:41 am, softworkz wrote:
From: softworkz
Changing this to 6 digits to align with other
printed times
Signed-off-by: softworkz
---
avformat/dump: Change precision of stream start offsets
Changing this to 6 digits to align with other printed times
S
On 2025-04-19 08:35 pm, softworkz wrote:
ffmpeg | branch: master | softworkz | Sat Feb 23
04:59:10 2019 +0100| [02d7384ed5eec0152056c081b536c16cb86e6361] | committer: softworkz
avformat/dump: Print stream start offsets for input streams
Seeing the offset of video and audio streams to each
On 2025-04-16 07:20 pm, Nicolas George wrote:
Michael Niedermayer (HE12025-04-16):
I think some way to distingish two different "hevc" instances
with high probability should remain.
This is exactly my point. The address is meaningless¹, but it is a sure
way to distinguish instances of the sam
On 2025-04-16 10:37 am, Andreas Rheinhardt wrote:
Gyan Doshi:
Utility function to report seekability features for a given input.
Useful for ffprobe and to extend seek possibilities in fftools.
---
v2:
made constants more descriptive
add exception for rtsp false negative seekability
---
doc/ffprobe.xsd | 2 ++
fftools/ffprobe.c| 15 ++-
tests/ref/fate/cavs-demux| 2 +-
tests/ref/fate/ffprobe_compact | 2 +-
tests/ref/fate/ffprobe_csv | 2 +-
tests/ref/fate/ffprobe_default | 2 ++
tests
Utility function to report seekability features for a given input.
Useful for ffprobe and to extend seek possibilities in fftools.
---
v3:
add some checks for seekability such as
default stream
demuxer seek function for NOFILE formats
doc/APIchanges | 3 ++
libavformat/avfo
---
doc/ffprobe.xsd | 2 ++
fftools/ffprobe.c| 15 ++-
tests/ref/fate/cavs-demux| 2 +-
tests/ref/fate/ffprobe_compact | 2 +-
tests/ref/fate/ffprobe_csv | 2 +-
tests/ref/fate/ffprobe_default | 2 ++
tests
Utility function to report seekability features for a given input.
Useful for ffprobe and to extend seek possibilities in fftools.
---
v2:
made constants more descriptive
add exception for rtsp false negative seekability
doc/APIchanges | 3 +++
libavformat/avformat.h | 22
On 2025-04-14 12:57 pm, softworkz . wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of Gyan
Doshi
Sent: Montag, 14. April 2025 08:54
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2] ffprobe: show seekability
details in format section
On 2025-04-14 10:22
On 2025-04-14 10:22 am, softworkz . wrote:
Hi Gyan,
the problem that I see here is that it's not machine-readable and
would require non-trivial parsing to translate back to the actual
information behind it.
I think that either a separate sub-section or at least three separate
values would
On 2025-04-13 09:48 pm, softworkz . wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of Gyan
Doshi
Sent: Sonntag, 13. April 2025 13:16
To:ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 2/2] ffprobe: show seekability details in
format section
---
fftools/ffprobe.c
On 2025-04-13 09:39 pm, softworkz . wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of Gyan
Doshi
Sent: Sonntag, 13. April 2025 13:16
To:ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 1/2] avformat: add
avformat_query_seekable
Utility function to report seekability
On 2025-04-13 10:12 pm, Zhao Zhili wrote:
On Apr 13, 2025, at 19:15, Gyan Doshi wrote:
Utility function to report seekability features for a given input.
Useful for ffprobe and to extend seek possibilities in fftools.
---
doc/APIchanges | 3 +++
libavformat/avformat.h | 22
---
fftools/ffprobe.c| 49 +++-
tests/ref/fate/cavs-demux| 2 +-
tests/ref/fate/ffprobe_compact | 2 +-
tests/ref/fate/ffprobe_csv | 2 +-
tests/ref/fate/ffprobe_default | 1 +
tests/ref/fate/ffprobe_flat |
Utility function to report seekability features for a given input.
Useful for ffprobe and to extend seek possibilities in fftools.
---
doc/APIchanges | 3 +++
libavformat/avformat.h | 22 ++
libavformat/seek.c | 53 ++
libavform
On 2025-04-09 11:49 pm, softworkz wrote:
diff --git a/fftools/opt_common.c b/fftools/opt_common.c
index 2ac3fd4fb3..edf2f49d0b 100644
--- a/fftools/opt_common.c
+++ b/fftools/opt_common.c
@@ -1304,6 +1304,12 @@ int opt_loglevel(void *optctx, const char *opt, const
char *arg)
} e
On 2025-04-09 02:55 pm, softworkz wrote:
From: softworkz
This commit adds the memaddress log flag.
When specifying this flag at the command line, context prefixes will
be printed with memory addresses like in earlier ffmpeg versions.
Example with memaddresses flag:
[hevc @ 018e72a89cc0
On 2025-03-18 03:34 pm, Gyan Doshi wrote:
On 2025-03-18 03:27 pm, Martin Storsjö wrote:
On Mon, 17 Mar 2025, Gyan Doshi wrote:
On 2025-03-17 09:44 pm, Zhao Zhili wrote:
On Mar 17, 2025, at 23:16, Gyan Doshi wrote:
This is to not break linking with toolchains that don't su
---
configure | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/configure b/configure
index d84e32196d..2c060b0cd4 100755
--- a/configure
+++ b/configure
@@ -5230,12 +5230,6 @@ else
ar_o='$@'
fi
-if $ar 2>&1 | grep -qi "@.*file"; then
-ar_objs="true"
-e
On 2025-03-31 12:09 pm, Andreas Rheinhardt wrote:
Patch attached.
LGTM.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-r
On 2025-04-01 05:39 am, Michael Niedermayer wrote:
These are more secure
Signed-off-by: Michael Niedermayer
---
doc/fate_config.sh.template | 2 +-
doc/git-howto.texi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/fate_config.sh.template b/doc/fate_co
On 2025-03-21 03:43 pm, Danil Iashchenko wrote:
Hi!
Added documentation for the thumbnail_cuda filter and updated its description
to align with the format of other CUDA-based filters.
The new description clarifies its behaviour and avoids confusion with the
{thumbnail} filter.
Thanks.
Adju
On 2025-03-29 10:42 am, Gyan Doshi wrote:
On 2025-03-26 07:38 pm, Gyan Doshi wrote:
---
v2:
*switched state and make var name to response_files
*changed option to standard action-optname format
Plan to push tomorrow.
Pushed as 64087171f67bab220c4d3001eb6b074cf488284c
Regards
On 2025-03-30 11:57 am, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2025-03-29 11:52 pm, Martin Storsjö wrote:
On Sat, 29 Mar 2025, Gyan Doshi wrote:
Did you not try to use GNU make's flie function?
I just benched this and it ranges from 1m28.093s to 1m29.971s (5%
faster) for the
On 2025-03-29 11:52 pm, Martin Storsjö wrote:
On Sat, 29 Mar 2025, Gyan Doshi wrote:
Did you not try to use GNU make's flie function?
I just benched this and it ranges from 1m28.093s to 1m29.971s (5%
faster) for the lavc targets.
However, this was added in make 4.0. Are we suppo
On 2025-03-29 05:51 pm, Ramiro Polla wrote:
Hi Gyan,
On Sat, Mar 29, 2025 at 6:11 AM Gyan Doshi wrote:
On 2025-03-27 10:03 am, Gyan Doshi wrote:
On 2025-03-26 11:37 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2025-03-25 05:11 pm, Ramiro Polla wrote:
On Sat, Mar 22, 2025 at 5:33 AM Gyan
On 2025-03-26 07:38 pm, Gyan Doshi wrote:
---
v2:
*switched state and make var name to response_files
*changed option to standard action-optname format
Plan to push tomorrow.
Regards,
Gyan
configure | 25 +
ffbuild/library.mak | 4 ++--
2
On 2025-03-27 10:03 am, Gyan Doshi wrote:
On 2025-03-26 11:37 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2025-03-25 05:11 pm, Ramiro Polla wrote:
Hi,
On Sat, Mar 22, 2025 at 5:33 AM Gyan Doshi wrote:
On 2025-03-22 03:29 am, Martin Storsjö wrote:
On Fri, 21 Mar 2025, Gyan Doshi
On 2025-03-26 11:37 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2025-03-25 05:11 pm, Ramiro Polla wrote:
Hi,
On Sat, Mar 22, 2025 at 5:33 AM Gyan Doshi wrote:
On 2025-03-22 03:29 am, Martin Storsjö wrote:
On Fri, 21 Mar 2025, Gyan Doshi wrote:
ffbuild/library.mak | 7 +--
1 file
On 2025-03-25 05:11 pm, Ramiro Polla wrote:
Hi,
On Sat, Mar 22, 2025 at 5:33 AM Gyan Doshi wrote:
On 2025-03-22 03:29 am, Martin Storsjö wrote:
On Fri, 21 Mar 2025, Gyan Doshi wrote:
ffbuild/library.mak | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/ffbuild
---
v2:
*switched state and make var name to response_files
*changed option to standard action-optname format
configure | 25 +
ffbuild/library.mak | 4 ++--
2 files changed, 19 insertions(+), 10 deletions(-)
diff --git a/configure b/configure
index 2fdbe
On 2025-03-24 06:42 pm, James Almer wrote:
On 3/24/2025 9:31 AM, Martin Storsjö wrote:
On Mon, 24 Mar 2025, Gyan Doshi wrote:
ffmpeg | branch: master | Gyan Doshi | Sat Mar 15
16:51:05 2025 +0530| [cbbc927a67f142a02bfc5d047c03587599ee5b55] |
committer: Gyan Doshi
ffmpeg: add per-stream
On 2025-03-23 10:06 am, Gyan Doshi wrote:
On 2025-03-19 10:33 am, Gyan Doshi wrote:
Added in bb80445813
Plan to push tomorrow.
Pushed as 6fb1bbd73c4d320733c636a22728a7d747303371
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel
On 2025-03-23 10:06 am, Gyan Doshi wrote:
On 2025-03-19 04:36 pm, Gyan Doshi wrote:
The existing default value is the same as the primary readrate.
This maintains the flow rate as best as possible but does not
reduce the lag. This new value allows catchup to gradually happen
without
On 2025-03-23 10:07 am, Gyan Doshi wrote:
On 2025-03-16 11:39 pm, Gyan Doshi wrote:
On 2025-03-16 11:12 pm, James Almer wrote:
On 3/16/2025 4:18 AM, Gyan Doshi wrote:
This is a replacement in ffmpeg for the deprecated avcodec flag
AV_CODEC_FLAG_DROPCHANGED.
This option is meant to be
On 2025-03-16 11:39 pm, Gyan Doshi wrote:
On 2025-03-16 11:12 pm, James Almer wrote:
On 3/16/2025 4:18 AM, Gyan Doshi wrote:
This is a replacement in ffmpeg for the deprecated avcodec flag
AV_CODEC_FLAG_DROPCHANGED.
This option is meant to be used when the filtergraph should not be
On 2025-03-19 04:36 pm, Gyan Doshi wrote:
The existing default value is the same as the primary readrate.
This maintains the flow rate as best as possible but does not
reduce the lag. This new value allows catchup to gradually happen
without overwhelming the receiver.
Addresses a concern
On 2025-03-19 10:33 am, Gyan Doshi wrote:
Added in bb80445813
Plan to push tomorrow.
Regards,
Gyan
---
libavfilter/vf_scale.c | 16
1 file changed, 16 deletions(-)
diff --git a/libavfilter/vf_scale.c b/libavfilter/vf_scale.c
index 8c03d7fd8d..293eb11a4e 100644
--- a
On 2025-03-22 03:29 am, Martin Storsjö wrote:
On Fri, 21 Mar 2025, Gyan Doshi wrote:
Avoids echo failing due to the same ARG_MAX limit that prompted
response files to be used with the linker.
I presume this is only a fix for a hypothetical issue, _if_ echo would
be a native windows
---
configure | 27 ---
ffbuild/library.mak | 4 ++--
2 files changed, 22 insertions(+), 9 deletions(-)
diff --git a/configure b/configure
index 14f7bcde0e..863b9adf22 100755
--- a/configure
+++ b/configure
@@ -427,6 +427,8 @@ Toolchain options:
--enable-thum
Avoids echo failing due to the same ARG_MAX limit that prompted
response files to be used with the linker.
---
ffbuild/library.mak | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/ffbuild/library.mak b/ffbuild/library.mak
index 7e1871b74c..15302852ec 100644
--- a/ffbuild/
On 2025-03-20 05:39 am, Ramiro Polla wrote:
On Tue, Mar 18, 2025 at 11:06 AM Gyan Doshi wrote:
ffmpeg | branch: master | Gyan Doshi | Mon Mar 17 20:57:28
2025 +0530| [740d4009656abeb006e2d43001b59d875c1a7a6a] | committer: Gyan Doshi
ffbuild: use response files only if ar accepts them
The existing default value is the same as the primary readrate.
This maintains the flow rate as best as possible but does not
reduce the lag. This new value allows catchup to gradually happen
without overwhelming the receiver.
Addresses a concern brought up in #11469
---
fftools/ffmpeg_demux.c |
On 2025-03-19 02:54 pm, Martin Storsjö wrote:
On Tue, 18 Mar 2025, Gyan Doshi wrote:
---
configure | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/configure b/configure
index d84e32196d..14f7bcde0e 100755
--- a/configure
+++ b/configure
@@ -5230,12 +5230,6
Added in bb80445813
---
libavfilter/vf_scale.c | 16
1 file changed, 16 deletions(-)
diff --git a/libavfilter/vf_scale.c b/libavfilter/vf_scale.c
index 8c03d7fd8d..293eb11a4e 100644
--- a/libavfilter/vf_scale.c
+++ b/libavfilter/vf_scale.c
@@ -247,22 +247,6 @@ static int check_ex
---
configure | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/configure b/configure
index d84e32196d..14f7bcde0e 100755
--- a/configure
+++ b/configure
@@ -5230,12 +5230,6 @@ else
ar_o='$@'
fi
-if $ar 2>&1 | grep -qi "@.*file"; then
-ar_objs="true"
-e
On 2025-03-18 03:27 pm, Martin Storsjö wrote:
On Mon, 17 Mar 2025, Gyan Doshi wrote:
On 2025-03-17 09:44 pm, Zhao Zhili wrote:
On Mar 17, 2025, at 23:16, Gyan Doshi wrote:
This is to not break linking with toolchains that don't support
reading
args from a 'response file&
On 2025-03-17 09:44 pm, Zhao Zhili wrote:
On Mar 17, 2025, at 23:16, Gyan Doshi wrote:
This is to not break linking with toolchains that don't support reading
args from a 'response file'.
---
I've assumed that ld on a system will have same support as ar.
con
This is to not break linking with toolchains that don't support reading
args from a 'response file'.
---
I've assumed that ld on a system will have same support as ar.
configure | 7 +++
ffbuild/library.mak | 8
2 files changed, 15 insertions(+)
diff --git a/configure b/co
On 2025-03-17 05:29 pm, Zhao Zhili wrote:
On Mar 17, 2025, at 19:45, Gyan Doshi wrote:
On 2025-03-17 05:02 pm, Zhao Zhili wrote:
On Mar 13, 2025, at 21:02, Gyan Doshi wrote:
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list
On 2025-03-17 05:02 pm, Zhao Zhili wrote:
On Mar 13, 2025, at 21:02, Gyan Doshi wrote:
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
v3:
for reasons unknown to me
On 2025-03-15 01:26 pm, Gyan Doshi wrote:
On 2025-03-13 06:32 pm, Gyan Doshi wrote:
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
v3:
for reasons unknown to me, static
On 2025-03-17 11:25 am, Gyan Doshi wrote:
On 2025-03-17 12:45 am, Danil Iashchenko wrote:
Hi Gyan and Michael,
Thank you for reviewing the patch and providing feedback!
I've addressed all the issues and resubmitting the patch (built and
tested with Texinfo 7.1.1).
Per Gyan's
On 2025-03-17 12:45 am, Danil Iashchenko wrote:
Hi Gyan and Michael,
Thank you for reviewing the patch and providing feedback!
I've addressed all the issues and resubmitting the patch (built and tested with
Texinfo 7.1.1).
Per Gyan's suggestion, I'm resubmitting since Patchwork was down when
On 2025-03-16 11:12 pm, James Almer wrote:
On 3/16/2025 4:18 AM, Gyan Doshi wrote:
This is a replacement in ffmpeg for the deprecated avcodec flag
AV_CODEC_FLAG_DROPCHANGED.
This option is meant to be used when the filtergraph should not be
reinited upon input parameter changes as that
On 2025-03-16 01:21 am, Marton Balint wrote:
On Sat, 15 Mar 2025, Gyan Doshi wrote:
This is a replacement in ffmpeg for the deprecated avcodec flag
AV_CODEC_FLAG_DROPCHANGED.
This option is meant to be used when the filtergraph should not be
reinited upon input parameter changes as that
This is a replacement in ffmpeg for the deprecated avcodec flag
AV_CODEC_FLAG_DROPCHANGED.
This option is meant to be used when the filtergraph should not be
reinited upon input parameter changes as that leads to loss of state
in the filtergraph potentially leading to broken or aborted output,
e.
On 2025-03-12 03:12 pm, Martin Storsjö wrote:
On Wed, 12 Mar 2025, Gyan Doshi wrote:
On 2025-03-12 01:29 pm, Martin Storsjö wrote:
On Wed, 12 Mar 2025, Gyan Doshi wrote:
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now
On 2025-02-24 03:14 pm, Gyan Doshi wrote:
On 2025-02-24 03:36 am, James Almer wrote:
Deprecated since 2023-07-15.
Can you wait to push till I port this to ffmpeg_dec?
Patch for replacement posted at
https://ffmpeg.org/pipermail/ffmpeg-devel/2025-March/341210.html
Regards,
Gyan
This is a replacement in ffmpeg for the deprecated avcodec flag
AV_CODEC_FLAG_DROPCHANGED.
This option is meant to be used when the filtergraph should not be
reinited upon input parameter changes as that leads to loss of state
in the filtergraph potentially leading to broken or aborted output,
e.
On 2025-03-13 06:32 pm, Gyan Doshi wrote:
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
v3:
for reasons unknown to me, static linking doesn't appear to
work on
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
v3:
for reasons unknown to me, static linking doesn't appear to
work on linux with escaped variables, so removed those.
Someone
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
ffbuild/library.mak | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/ffbuild/library.mak b/ffbuild/library.mak
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
v2:
static linking also switched to use a file for object list
objs added to clean target and to gitignore
.gitignore
On 2025-03-12 05:52 pm, Martin Storsjö wrote:
On Wed, 12 Mar 2025, Gyan Doshi wrote:
On 2025-03-12 03:12 pm, Martin Storsjö wrote:
On Wed, 12 Mar 2025, Gyan Doshi wrote:
On 2025-03-12 01:29 pm, Martin Storsjö wrote:
On Wed, 12 Mar 2025, Gyan Doshi wrote:
The linker command can exceed
On 2025-03-12 01:29 pm, Martin Storsjö wrote:
On Wed, 12 Mar 2025, Gyan Doshi wrote:
The linker command can exceed the maximum argument limit on MinGW,
especially for libavcodec.
The objects list is now stored in a file and passed to the linker.
---
ffbuild/library.mak | 4 +++-
1 file
On 2025-03-05 10:00 pm, Soft Works wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of Gyan
Doshi
Sent: Mittwoch, 5. März 2025 17:23
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avutil/log: Replace addresses in log
output with simple ids
On 2025-03-05 09
On 2025-03-05 09:08 pm, softworkz wrote:
From: softworkz
..and individual numbering. The benefits are:
- Smaller log file sizes
- The disambiguation is much easier to recognize and to follow
- It eventually allows comparing and viewing log file diffs
without almost every line being diffe
On 2025-02-23 01:06 pm, Gyan Doshi wrote:
On 2025-02-18 03:16 pm, Gyan Doshi wrote:
At present, if reading from a readrate-limited input is stalled,
then upon resumption, ffmpeg will read the input without any
throttle till the average readrate matches the specified readrate.
This new
On 2025-02-23 01:06 pm, Gyan Doshi wrote:
On 2025-02-21 05:34 pm, Gyan Doshi wrote:
On 2025-02-21 04:34 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2025-02-21 02:21 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
---
fftools/opt_common.c | 5 +
1 file changed, 5 insertions
1 - 100 of 1165 matches
Mail list logo
