e CLI documentation.
Patchwork warns, "Please wrap lines in the body of the commit message
between 60 and 72 characters."
but otherwise LGTM.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listin
On 2024-10-05 06:21 pm, James Almer wrote:
On 10/5/2024 1:44 AM, Gyan Doshi wrote:
Earlier, x265 made an API change to support alpha and
other multiple layer pictures. We added guards to accommodate
that in 1f801dfdb5
They have now reverted that API change in
https://bitbucket.org
Earlier, x265 made an API change to support alpha and
other multiple layer pictures. We added guards to accommodate
that in 1f801dfdb5
They have now reverted that API change in
https://bitbucket.org/multicoreware/x265_git/commits/78e5b703b1
Updated our wrapper guards to unbreak build again.
---
On 2024-09-27 05:03 am, Michael Niedermayer wrote:
On Wed, Sep 25, 2024 at 09:18:56PM +0530, Gyan Doshi wrote:
The decoder wrapper was removed in 60ccb3fe78
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
LGTM
Thanks.
Pushed as 2b689261c5bae0005a76403219392f8a597717ed
Regards
The decoder wrapper was removed in 60ccb3fe78
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 76651d5ff8..c968fc765c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -206,7 +206,6 @@ Codecs:
libgsm.c Michel Bardiaux
I had the impression, that physics count, but in the field of
mathematics and computer sciences I would definitely vote for:
"peters" (https://en.wikipedia.org/wiki/R%C3%B3zsa_P%C3%A9ter)
...the "founding mother of recursion theory".
+1
Regards,
Gyan
On 2024-09-17 05:45 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-09-17 13:15:45)
The option is enc_time_base, not enc_timebase
---
fftools/ffmpeg_mux_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fftools/ffmpeg_mux_init.c b/fftools/ffmpeg_mux_init.c
index
The option is enc_time_base, not enc_timebase
---
fftools/ffmpeg_mux_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fftools/ffmpeg_mux_init.c b/fftools/ffmpeg_mux_init.c
index 30d74d37bd..571c9808b9 100644
--- a/fftools/ffmpeg_mux_init.c
+++ b/fftools/ffmpeg_mux_init.c
On 2024-09-05 01:29 am, Michael Niedermayer wrote:
On Wed, Sep 04, 2024 at 01:33:50PM +0530, Gyan Doshi wrote:
The filter was disabled in 95054bfa48 and re-enabled in 771c27119d
---
doc/filters.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
LGTM
Thanks.
Pushed as
On 2024-09-04 01:33 pm, Gyan Doshi wrote:
The filter was disabled in 95054bfa48 and re-enabled in 771c27119d
Will push tomorrow.
Regards,
Gyan
---
doc/filters.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index 2eb4a380fb
The filter was disabled in 95054bfa48 and re-enabled in 771c27119d
---
doc/filters.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index 2eb4a380fb..b1ca9ad2f3 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -24463,7 +24463,7 @@
On 2024-08-31 04:29 pm, Gyan Doshi wrote:
On 2024-08-28 03:52 pm, Gyan Doshi wrote:
The check is for color space, not range.
Will push tomorrow.
Pushed as b5daaa1503fd149a8e6c4964266ceb93fd7d09cd
Regards,
Gyan
___
ffmpeg-devel mailing list
On 2024-08-28 03:52 pm, Gyan Doshi wrote:
The check is for color space, not range.
Will push tomorrow.
Regards,
Gyan
---
libavfilter/formats.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/formats.c b/libavfilter/formats.c
index eabc3ec946..2b570b466e
The check is for color space, not range.
---
libavfilter/formats.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/formats.c b/libavfilter/formats.c
index eabc3ec946..2b570b466e 100644
--- a/libavfilter/formats.c
+++ b/libavfilter/formats.c
@@ -977,7 +977,7 @@ int f
Patch withdrawn, superfluous since 1afe42852b.
On 2024-08-19 08:33 pm, Gyan Doshi wrote:
filters.h has been needed since 42cbf66fff for FilterLink.
---
libavfilter/vf_quirc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/vf_quirc.c b/libavfilter/vf_quirc.c
index 760f5d97de
filters.h has been needed since 42cbf66fff for FilterLink.
---
libavfilter/vf_quirc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/vf_quirc.c b/libavfilter/vf_quirc.c
index 760f5d97de..afd172fa34 100644
--- a/libavfilter/vf_quirc.c
+++ b/libavfilter/vf_quirc.c
@@ -27,6 +27,7 @@
On 2024-08-14 10:01 am, Gyan Doshi wrote:
On 2024-08-11 04:03 pm, Gyan Doshi wrote:
x265 added support for alpha starting with build 210.
While doing so, x265_encoder_encode() changed its fifth arg to
an array of pointers to x265_picture. This broke building lavc/libx265.c
This patch
Andreas Cadhalpun, Carl Eugen Hoyos,
Clément Bœsch, Michael Niedermayer, Reimar Doeffinger, rcombs, wm4
+ffmpeg-security [2] Michael Niedermayer, Reimar Doeffinger
Does the status apply to just you or all listed? The notation is ambiguous.
Regards,
Gyan
On 2024-08-11 04:03 pm, Gyan Doshi wrote:
x265 added support for alpha starting with build 210.
While doing so, x265_encoder_encode() changed its fifth arg to
an array of pointers to x265_picture. This broke building lavc/libx265.c
This patch simply unbreaks the build and maintains existing
x265 added support for alpha starting with build 210.
While doing so, x265_encoder_encode() changed its fifth arg to
an array of pointers to x265_picture. This broke building lavc/libx265.c
This patch simply unbreaks the build and maintains existing single-layer
non-alpha encoding support.
Fixes
On 2024-07-22 01:01 pm, Gyan Doshi wrote:
On 2024-07-22 12:53 pm, Shin Han wrote:
Hi
We found a very simple typo in the libvmaf_cuda section of doc/filters
where the order of the [dis] and [ref] labels is reversed.
We believe fixing this typo would be benefical of those who are new to
.
Thanks,
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-requ...@ffmpeg.org with subject "unsubscribe".
On 2024-07-16 09:40 am, Marth64 wrote:
Gyan:
The former is not an error. The user was asked and the application
behaved as per their reply.
Could it make sense to only return the AVERROR(EEXIST) if -nostdin is
passed (otherwise current behavior)?
Agreed.
Regards,
Gyan
OR(EEXIST);
The former is not an error. The user was asked and the application
behaved as per their reply.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visi
On 2024-07-14 02:14 pm, Gyan Doshi wrote:
On 2024-07-11 02:52 pm, Gyan Doshi wrote:
Can lead to printing of nonsensical negative memory usage
Plan to push in 24h.
Pushed as 350146a1ea9d2d0220cc8d024125b77240e3e98d
Regards,
Gyan
___
ffmpeg
On 2024-07-11 02:52 pm, Gyan Doshi wrote:
Can lead to printing of nonsensical negative memory usage
Plan to push in 24h.
Regards,
Gyan
---
fftools/ffmpeg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 00ab1cce51
Can lead to printing of nonsensical negative memory usage
---
fftools/ffmpeg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 00ab1cce51..3aa2e12780 100644
--- a/fftools/ffmpeg.c
+++ b/fftools/ffmpeg.c
@@ -309,8 +309,8 @@ const AVI
On 2024-07-04 04:14 am, Vittorio Giovara wrote:
On Wed, Jul 3, 2024 at 9:29 PM Gyan Doshi wrote:
On 2024-07-02 10:45 am, Gyan Doshi wrote:
---
doc/filters.texi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index
On 2024-07-02 10:45 am, Gyan Doshi wrote:
---
doc/filters.texi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index 0ff7c142b6..c9c4f7cf6b 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -23546,13 +23546,13 @@ tile
---
doc/filters.texi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index 0ff7c142b6..c9c4f7cf6b 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -23546,13 +23546,13 @@ tile=3x2:nb_frames=5:padding=7:margin=2
@end itemize
On 2024-06-25 11:51 am, Gyan Doshi wrote:
On 2024-06-21 04:18 pm, Gyan Doshi wrote:
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Plan to improve commit messages and push set in 24h.
Pushed as 27284b780087f9217f628a440e977f207b8b2885 and
On 2024-06-21 04:18 pm, Gyan Doshi wrote:
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Plan to improve commit messages and push set in 24h.
diff --git a/configure b/configure
index 1e58c0dbac..db11a78c74 100755
--- a/configure
+++ b/configure
@@ -7764,14
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 1e58c0dbac..db11a78c74 100755
--- a/configure
+++ b/configure
@@ -7764,14 +7764,14 @@ enabled elbg_filter && prepend avfilter_deps
"avcodec"
enabled find_rect_filter&& pr
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 3bca638459..1e58c0dbac 100755
--- a/configure
+++ b/configure
@@ -7767,8 +7767,8 @@ enabled mcdeint_filter && prepend avfilter_deps
"avcodec"
enabled movie_filter&& prepend
On 2024-06-19 06:04 pm, Martin Storsjö wrote:
On Mon, 17 Jun 2024, Gyan Doshi via ffmpeg-devel wrote:
Ultimately, as long as the doc is clear about what the use of this
option is, and what to do next if the muxing does abort, it should
not matter too much what the option is called.
So
On 2024-06-18 11:53 pm, Timo Rothenpieler wrote:
On 18.06.2024 18:56, Gyan Doshi wrote:
FWIW, I had to do the same for securetransport on a project a couple
of years back to get rtmps working. Worked fine, and did not get any
reports of ill-effects.
You mean the FFmpeg implementation of
av_log(h, AV_LOG_ERROR, "Writing encrypted data to
socket failed\n");
goto done;
ping
I'm specifically unsure if implementing the sending-side like this is
valid and would appreciate review from someone familiar with the code
and schannel.
FWIW, I
On 2024-06-17 04:08 pm, Martin Storsjö wrote:
On Sat, 15 Jun 2024, Gyan Doshi wrote:
On 2024-06-15 03:54 am, Dennis Sädtler via ffmpeg-devel wrote:
On 2024-06-14 13:23, Gyan Doshi wrote:
On 2024-06-14 04:35 pm, Timo Rothenpieler wrote:
On 14/06/2024 12:44, Martin Storsjö wrote:
On Fri
On 2024-06-15 03:54 am, Dennis Sädtler via ffmpeg-devel wrote:
On 2024-06-14 13:23, Gyan Doshi wrote:
On 2024-06-14 04:35 pm, Timo Rothenpieler wrote:
On 14/06/2024 12:44, Martin Storsjö wrote:
On Fri, 14 Jun 2024, Gyan Doshi wrote:
On 2024-06-14 02:18 am, Martin Storsjö wrote:
On Thu
On 2024-06-14 04:35 pm, Timo Rothenpieler wrote:
On 14/06/2024 12:44, Martin Storsjö wrote:
On Fri, 14 Jun 2024, Gyan Doshi wrote:
On 2024-06-14 02:18 am, Martin Storsjö wrote:
On Thu, 13 Jun 2024, Gyan Doshi wrote:
On 2024-06-13 06:20 pm, Martin Storsjö wrote:
I'd otherwise wa
On 2024-06-14 02:18 am, Martin Storsjö wrote:
On Thu, 13 Jun 2024, Gyan Doshi wrote:
On 2024-06-13 06:20 pm, Martin Storsjö wrote:
On Wed, 5 Jun 2024, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable
the option name quite yet. I'm pondering if we should call it
"hybrid_fragmented" - any opinions, Dennis or Timo?
How about `resilient_mode` or `recoverable`?
I agree that the how is secondary.
Regards,
Gyan
___
ffmpeg-devel mailing l
On 2024-06-05 12:47 am, Stefano Sabatini wrote:
On date Tuesday 2024-06-04 23:41:05 +0530, Gyan Doshi wrote:
Similar to select filter for video - it can only pass through or drop frames
---
libavfilter/trim.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/trim.c b
Similar to select filter for video - it can only pass through or drop frames
---
libavfilter/trim.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/trim.c b/libavfilter/trim.c
index 4c1a2b4f48..4afc4c74bb 100644
--- a/libavfilter/trim.c
+++ b/libavfilter/trim.c
@@ -364,6 +364,7 @@
On 2024-05-31 09:07 pm, Pierre-Anthony Lemieux wrote:
On Fri, May 31, 2024 at 8:32 AM Gyan Doshi wrote:
Decoding is no longer possible as the decoder wrapper was removed
in 60ccb3fe78
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
Decoding is no longer possible as the decoder wrapper was removed
in 60ccb3fe78
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 96b181fd21..6c5b8aab9a 100755
--- a/configure
+++ b/configure
@@ -253,7 +253,7 @@ External library support:
AT, {.dbl=0.5}, 0, 1, VF },
+ { "lightness", "set the lightness", OFFSET(lightness),
AV_OPT_TYPE_FLOAT, {.dbl=0.5}, 0, 1, VF },
+ { "mix", "set the mix of source lightness", OFFSET(mix),
AV_OPT_TYPE_FLOAT, {.dbl=1}, 0, 1,
y[ref];
in new flow:
[base]split=5[base][refa][refb][refc][refd];
[a][refa]scale[a];
[b][refb]scale[b];
[c][refc]scale[c];
[d][refd]scale[d];
[base][a]overlay[outa];
[outa][b]overlay[outb];
[outb][c]overlay[outc];
[outc][d]overlay[out];
Regards,
Gyan
On 2024-04-17 05:25 pm, James Almer wrote:
On 4/17/2024 8:31 AM, Gyan Doshi wrote:
sum_delta_pts is unused since 3b358f151d
---
libavformat/ivfenc.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/libavformat/ivfenc.c b/libavformat/ivfenc.c
index 09782eecd6
sum_delta_pts is unused since 3b358f151d
---
libavformat/ivfenc.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/libavformat/ivfenc.c b/libavformat/ivfenc.c
index 09782eecd6..9feaea3516 100644
--- a/libavformat/ivfenc.c
+++ b/libavformat/ivfenc.c
@@ -24,7 +24,7 @@
typede
organisms decide to resolve
conflicts for controversial features.
Only if they respond. My matter is pending with the TC for close to 2
months now.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listi
Ping x2.
On 2024-04-02 10:55 am, Gyan Doshi wrote:
Ping.
As the TC rules matter has been concluded, this should go ahead.
Regards,
Gyan
On 2024-02-17 05:15 pm, Gyan Doshi wrote:
Issue:
Patch: avcodec/s302m: enable non-PCM decoding
URL:
https://patchwork.ffmpeg.org/project/ffmpeg/patch
,
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-requ...@ffmpeg.org with subject "unsubscribe".
Ping.
As the TC rules matter has been concluded, this should go ahead.
Regards,
Gyan
On 2024-02-17 05:15 pm, Gyan Doshi wrote:
Issue:
Patch: avcodec/s302m: enable non-PCM decoding
URL:
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20240127103854.9971-1-ffm...@gyani.pro/
The issue
ed to this email for future reference.
How come there's an entry with all 7s?
The choices were ranks, not weight markers.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To uns
#endif
+ ,
.p.codec_tag = mp4_codec_tags_list,
.check_bitstream = mov_check_bitstream,
.p.priv_class = &mov_isobmff_muxer_class,
LGTM. Should have been done a long time ago.
What about the other muxers in movenc?
Regards,
On 2024-03-25 03:11 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-03-22 14:05:05)
Please do post the final text and options a day in advance.
I have now created the poll, but not started it yet (the text and
options can still be edited). It looks like this:
The description, my option
wants to vote for, as it imposes a burden on the voters who have to
carefully read and compare all the options.
Beyond that, I am planning to start the vote on Monday 2024-03-25.
Please do post the final text and options a day in advance.
Regards,
Gyan
Ping.
Anton announced to have a vote on 4th Mar for changing the rule [1].
That's long past.
It is holding up the consideration of the matter I raised [2] to the TC.
Regards,
Gyan
[1]: https://ffmpeg.org/pipermail/ffmpeg-devel/2024-March/322464.html
[2]: https://ffmpeg.org/pipermail/f
On 2024-03-18 04:11 pm, Liu Steven wrote:
On Mar 18, 2024, at 18:11, Gyan Doshi wrote:
---
tests/fate/lavf-container.mak | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/fate/lavf-container.mak b/tests/fate/lavf-container.mak
index b18ed2362b..7a925117c3 100644
---
tests/fate/lavf-container.mak | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/fate/lavf-container.mak b/tests/fate/lavf-container.mak
index b18ed2362b..7a925117c3 100644
--- a/tests/fate/lavf-container.mak
+++ b/tests/fate/lavf-container.mak
@@ -80,7 +80,7 @@ FATE_LAV
On 2024-03-16 02:02 pm, Marton Balint wrote:
On Sat, 16 Mar 2024, Gyan Doshi wrote:
8559cce3c3 made the bitstream check generic using a LUT.
However, one of the comparisons which involves a bitwise AND
and equality check is faulty due to operator precedence.
First reported and analysed at
8559cce3c3 made the bitstream check generic using a LUT.
However, one of the comparisons which involves a bitwise AND
and equality check is faulty due to operator precedence.
First reported and analysed at
https://github.com/streamlink/streamlink/issues/5876
Fixes #10908
---
libavformat/mpegtsen
On 2024-03-14 03:46 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-03-13 08:49:52)
Are there any limitations to loopback decoding e.g. would a vpx w/alpha
encode be decoded back to a alpha pix fmt?
I don't know how vpx alpha works, was it a separate stream in the
demuxer or some
this
change has occurred (and when) as existing scripts will fail due to the
surplus output pad.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or em
t;) &&
+strcmp(link->dst->filter->name, "scale2ref")) {
av_assert1(frame->format == link->format);
av_assert1(frame->width == link->w);
av_assert1(frame->height== link->h);
LGTM.
Regards,
Gyan
vc generic + private option to a loopbacked stream?
Are there any limitations to loopback decoding e.g. would a vpx w/alpha
encode be decoded back to a alpha pix fmt?
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.
eps="d3d11va DXVA_PicParams_AV1"
lgtm
Thanks. Pushed as 9e8be937fc4933ade00a18578f8c1420006d4291
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-requ...@ffmpeg.org with subject "unsubscribe".
initial
step showing export.
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-requ...@ffmpeg.org with subject "unsubscribe".
Fixes #10900
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index 05f8283af9..e0b5bcf589 100755
--- a/configure
+++ b/configure
@@ -3076,6 +3076,7 @@ nvdec_deps="ffnvcodec"
vaapi_x11_deps="xlib_x11"
videotoolbox_hwaccel_deps="videotoolbox pthreads"
video
On 2024-03-06 11:02 am, Gyan Doshi wrote:
On 2024-03-01 07:41 pm, Gyan Doshi wrote:
At present, consume_update evaluates timeline state on all links for
a multi-input filter. This can lead to the filter being incorrectly
en/dis-abled when evaluation on a frame on a secondary link leads to
On 2024-03-01 07:41 pm, Gyan Doshi wrote:
At present, consume_update evaluates timeline state on all links for
a multi-input filter. This can lead to the filter being incorrectly
en/dis-abled when evaluation on a frame on a secondary link leads to
a different result than the frame on the
On 2024-03-03 07:04 am, Michael Niedermayer wrote:
On Sat, Mar 02, 2024 at 11:07:40AM +0530, Gyan Doshi wrote:
On 2024-03-01 11:03 pm, Anton Khirnov wrote:
* Any member of the TC who had a strong opinion on the question raised
before it was raised should recuse themselves.
In
---
doc/community.texi | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/doc/community.texi b/doc/community.texi
index 90d2b6f366..8d5722bd7f 100644
--- a/doc/community.texi
+++ b/doc/community.texi
@@ -82,7 +82,20 @@ The TC has 2 modes of operation: a RFC one and
FFmpeg governance bodies for a period of no less
than
two years.
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-requ
At present, consume_update evaluates timeline state on all links for
a multi-input filter. This can lead to the filter being incorrectly
en/dis-abled when evaluation on a frame on a secondary link leads to
a different result than the frame on the current main link next in
line for processing.
---
Unbreaks movenc compilation in minimal configuration.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 197f762b58..2d0e6a444a 100755
--- a/configure
+++ b/configure
@@ -3554,7 +3554,7 @@ mlp_demuxer_select="mlp_parser"
mmf_muxer_select=
;s a disagreement with the rule, not with its interpretation.
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-requ...@ffmpeg.org with subject "unsubscribe".
does that
mean they can vote regardless of what the other members think? In other
words, by whom and how is a claim of conflict adjudicated?
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-
member) of making a conflict of interest
determination?
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-requ...@ffmpeg.org with subject "unsubscribe".
On 2024-02-19 08:00 pm, Vittorio Giovara wrote:
On Mon, Feb 19, 2024 at 6:11 AM Gyan Doshi wrote:
The TC is invoked when there's an intractable dispute. So the dispute
precedes the TC activity hence the parties to the dispute are the main
opposing participants at the venue of the di
On 2024-02-19 03:16 am, Vittorio Giovara wrote:
On Sun, Feb 18, 2024 at 8:02 PM Gyan Doshi wrote:
On 2024-02-18 11:33 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-18 05:06:30)
b) what "maximalist" interpretation?
A non-maximalist interpretation would be that a TC memb
On 2024-02-18 11:33 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-18 05:06:30)
b) what "maximalist" interpretation?
A non-maximalist interpretation would be that a TC member is only
excluded from voting when they authored the patch that is being
disputed.
If the promulga
On 2024-02-18 01:25 am, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-17 13:37:38)
On 2024-02-17 05:52 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-17 12:46:27)
As a TC member who is part of the disagreement, I believe your
participation is recused.
No, I do not think &qu
On 2024-02-17 07:12 pm, Niklas Haas wrote:
On Sat, 17 Feb 2024 18:45:57 +0530 Gyan Doshi wrote:
Whilst s302m multiple substreams I haven't seen, Dolby E streams internally
contain multiple programs, often 5.1 and a 2.0 downmix.
That is downstream of the Dolby-E decoder and user will
On 2024-02-17 05:31 pm, Kieran Kunhya wrote:
On Sat, 17 Feb 2024, 11:46 Gyan Doshi, wrote:
Issue:
Patch: avcodec/s302m: enable non-PCM decoding
URL:
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20240127103854.9971-1-ffm...@gyani.pro/
The issue needing resolution is whether the
On 2024-02-17 05:52 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-17 12:46:27)
As a TC member who is part of the disagreement, I believe your
participation is recused.
No, I do not think "TC members who commented on a patch lose their right
to vote" is a reasonable interpr
On 2024-02-16 02:33 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-15 17:47:49)
This patch facilitates a certain productive use of ffmpeg with respect
to processing of live inputs that wasn't possible earlier,
and which currently is being used successfully by multiple people ove
ilter might be a
better fit if s302m streams with multiple media
payloads ever start appearing - none have, so far - but for single media
payloads, a decoder remains the best place.
Regards,
Gyan
[1]: https://ffmpeg.org/pipermail/ffmpeg-devel/2024-January/320119.html
[2]: https://ffmpeg.org/
On 2024-02-16 07:25 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2024-02-15 04:17 pm, Anton Khirnov wrote:
Hi,
sorry for the delay, I've been busy fixing things for the release
Quoting Gyan Doshi via ffmpeg-devel (2024-01-29 05:00:33)
On 2024-01-28 04:24 pm, Anton Khirnov wrote:
On 2024-02-16 01:56 am, Kieran Kunhya wrote:
On Thu, 15 Feb 2024 at 16:48, Gyan Doshi wrote:
On 2024-02-15 09:40 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-15 13:31:59)
On 2024-02-15 04:17 pm, Anton Khirnov wrote:
Hi,
sorry for the delay, I've been busy fixing things fo
On 2024-02-15 09:40 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-02-15 13:31:59)
On 2024-02-15 04:17 pm, Anton Khirnov wrote:
Hi,
sorry for the delay, I've been busy fixing things for the release
Quoting Gyan Doshi via ffmpeg-devel (2024-01-29 05:00:33)
On 2024-01-28 04:24 pm,
On 2024-02-15 04:17 pm, Anton Khirnov wrote:
Hi,
sorry for the delay, I've been busy fixing things for the release
Quoting Gyan Doshi via ffmpeg-devel (2024-01-29 05:00:33)
On 2024-01-28 04:24 pm, Anton Khirnov wrote:
a) it would mean essentially inlining this decoder in the demuxer.
On 2024-01-27 04:08 pm, Gyan Doshi wrote:
Set up framework for non-PCM decoding in-place and
add support for Dolby-E decoding.
Useful for direct transcoding of non-PCM audio in live inputs.
Plan to push in 3 days, barring objections.
Regards,
Gyan
---
configure | 1 +
doc
On 2024-02-02 03:34 pm, Gyan Doshi wrote:
On 2024-01-29 10:30 am, Gyan Doshi wrote:
Existing use of strtoll can lead to ERANGE errors leading to incorrect
storage of UMID.
Plan to push tomorrow.
Pushed as 7375a6ca7b4a4b223a71f85a772c64a34e60eabe
Regards,
Gyan
On 2024-01-29 10:30 am, Gyan Doshi wrote:
Existing use of strtoll can lead to ERANGE errors leading to incorrect
storage of UMID.
Plan to push tomorrow.
Regards,
Gyan
---
libavformat/wavenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/wavenc.c b
On 2024-01-31 09:49 am, Gyan Doshi wrote:
On 2024-01-26 07:39 pm, Gyan Doshi wrote:
The video param change check will print loglines below debug level
for each frame which is different from the inlink parameters. This
can spam the console. It is now printed at warning level once for
each
On 2024-01-26 07:39 pm, Gyan Doshi wrote:
The video param change check will print loglines below debug level
for each frame which is different from the inlink parameters. This
can spam the console. It is now printed at warning level once for
each param change else it is kept at debug level
On 2024-01-29 02:57 pm, Nicolas Gaullier wrote:
On 2024-01-28 04:24 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2024-01-26 05:23:50)
On 2024-01-25 06:47 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
On 2024-01-25 10:29 am, Andreas Rheinhardt wrote:
Gyan Doshi:
Set up framework for non-PCM
Existing use of strtoll can lead to ERANGE errors leading to incorrect
storage of UMID.
---
libavformat/wavenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/wavenc.c b/libavformat/wavenc.c
index 82acb9ef0f..a41f40b449 100644
--- a/libavformat/wavenc.c
+++ b/liba
1 - 100 of 1111 matches
Mail list logo
