On Thu, Aug 26, 2021 at 05:08:15AM +, Maryam Ebrahimzadeh wrote:
> Thanks,
> So when will you apply this?
applied.
-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)
signature.asc
Description: PGP signature
___
ffmpeg-devel mailing list
LGTM
___
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".
This is a more complete and more flexible alternative to the recently submitted
patch "fftools: add -lavfi_dump option"
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
I'm tagging this patch as 'RFC'. There's no need to tell that this is
duplicating
co
On Sat, Aug 14, 2021 at 11:29:40 +, ffmpegandmahanstreamer@e.email wrote:
Just formal stuff:
> /* if macroblock width is 2, apply C-Y-C-Y; else
> * apply C-Y-Y */
> +APPLY_C_PREDICTOR();
> +APPLY_Y_PREDICTOR();
Soft Works (12021-08-26):
> This is a more complete and more flexible alternative to the recently
> submitted
> patch "fftools: add -lavfi_dump option"
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
>
> I'm tagging this patch as 'RFC'. There's no need
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Moritz Barsnick
> Sent: Thursday, 26 August 2021 09:25
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/truemotion1: Cleanup
> prediction code in truemotion1_decode_
Unacceptable, NACK.
___
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".
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 09:34
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to fil
Soft Works (12021-08-26):
> The purpose is to get a precise and detailed view of the filtergraphs
> at runtime including all connections with their negotiated formats and
> media types.
I asked the purpose, you are rephrasing what the patch does.
--
Nicolas George
signature.asc
Description:
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 09:40
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to fil
Soft Works (12021-08-26):
> Does that answer your question?
Yes. It is almost exactly what I had guessed. And therefore my answer is
what I expected it do be: that does not justify thousands, or even
hundreds, of lines of code in the core library and tools.
--
Nicolas George
signature.asc
De
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 10:05
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to fil
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 10:05
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to fil
Soft Works (12021-08-26):
> To be clear: I didn't submit this to end up in a LOC count discussion.
Good.
> My point is that there's much more relevant and important information
> that a filtergraph-information feature should provide than what your
> proposed patch is outputting.
Which one?
> co
Paul B Mahol Wrote:
>
> will apply shortly
>
Gotcha. Much appreciated.
Jianhua
___
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...@ffmp
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 11:03
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to fil
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Monday, 23 August 2021 11:45
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 1/2] lavfi/graphdump: add plain
> listing output
>
> Signed-off-by: Nicolas George
> ---
> libavfilter/avfilter.
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 10:05
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to file
On Tue, Aug 24, 2021 at 09:43:43AM -0400, Olivier Crête wrote:
> From: Stéphane Cerveau
>
> Consider data as invalid if ff_wma_run_level_decode
> gets out with an error.
>
> It avoids an unpleasant sound distorsion.
>
> See http://trac.ffmpeg.org/ticket/9358
> ---
> libavcodec/wmadec.c | 11 ++
On Fri, Aug 20, 2021, at 4:24 PM, Jai Luthra wrote:
> Co-authored-by: Oscar
> Signed-off-by: Jai Luthra
> ---
> libavfilter/signature_lookup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/signature_lookup.c
> b/libavfilter/signature_lookup.c
> index
Soft Works (12021-08-26):
> - Instead you criticized my patch for its LOC count, even though that is
> just made up from the output writers code duplication...
You are mistaken here too. Unlike what you seem to think, I factored
your saying that the writers would have to be de-duplicated in my
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 26 August 2021 13:12
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to fil
On 26.08.2021 06:34, "zhilizhao(赵志立)" wrote:
I tried try `make install` on my machine and I got:
install: cannot create regular file '/usr/local/share/man/man1/ffmpeg.1':
Permission denied
install: cannot create regular file '/usr/local/share/man/man1/ffprobe.1':
Permission denied
i
The problem here is that the lock ctx->frame_lock will become an unreleased
lock if the program returns at line 697, line 735 and line744
Cc: cy...@connect.ust.hk
Bug tracker link: https://trac.ffmpeg.org/ticket/9385\#ticket
Signed-off-by: Chengfeng Ye
---
libavdevice/avfoundation.m | 3 +++
1
The problem here is that the lock ctx->frame_lock will become an unreleased
lock if the program returns at line 1067, line 1071, line 1098, line 1104, line
1108, line 1112, line 1131, line 1142 and line 1162.
Depends-on: series-0001 (libavdevice: Fix a potential deadlock issue on the
lock ctx->
On Tue, Aug 24, 2021 at 11:42 PM Mapul Bhola
wrote:
> I agree with Mahol here. It's good to make sure all the code in FFmpeg meets
> a certain quality.
> I thought there were OpenCV filters in ffmpeg already?
I'm more than happy to address any issues of code quality in this
filter to go into F
Chengfeng Ye (12021-08-26):
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] libavdevice: Fix a potential deadlock
> issue on the lock ctx->frame_lock in function avf_read_packet
"libavdevice/avfoundation"
> The problem here is that the lock ctx->frame_lock will become an unreleased
> lock if the progr
All of the existing filters for video stabilization use an affine model
(or a limited version of it) to represent the movement of the camera. When
used with cameras with a very wide field of view and/or where the camera
shaking is severe, the corrections result in significant geometric
distortion (
All of the existing filters for video stabilization use an affine model
(or a limited version of it) to represent the movement of the camera. When
used with cameras with a very wide field of view and/or where the camera
shaking is severe, the corrections result in significant geometric
distortion (
On Thu, 2021-08-26 at 12:33 +0200, Michael Niedermayer wrote:
> On Tue, Aug 24, 2021 at 09:43:43AM -0400, Olivier Crête wrote:
> > From: Stéphane Cerveau
> >
> > Consider data as invalid if ff_wma_run_level_decode
> > gets out with an error.
> >
> > It avoids an unpleasant sound distorsion.
> >
The problem here is that the lock ctx->frame_lock will
become an unreleased lock if the program returns at
line 697, line 735 and line744.
Cc: cy...@connect.ust.hk
Bug tracker link: https://trac.ffmpeg.org/ticket/9385\#ticket
Signed-off-by: Chengfeng Ye
---
libavdevice/avfoundation.m | 3 +++
1
The problem here is that the lock ctx->frame_lock will become
an unreleased lock if the program returns at patched lines.
Depends-on: series-0001
Cc: cy...@connect.ust.hk
Bug tracker link: https://trac.ffmpeg.org/ticket/9386\#ticket
Signed-off-by: Chengfeng Ye
---
libavdevice/avfoundation.m | 1
We've just added a file to libwebp-test-data that covers this case:
https://chromium.googlesource.com/webm/libwebp-test-data/+/refs/heads/main/dual_transform.webp
FFmpeg currently fails to decode it, but it works with this patch.
My understanding is that an ffmpeg developer needs to upload the fil
Implementation of a grayworld color correction filter
Paul Buxton (1):
Implement gray world color correction uses log LAB colorspace
doc/filters.texi | 12 ++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/version.h | 2 +-
libavfilter/vf_
Signed-off-by: Paul Buxton
---
doc/filters.texi | 12 ++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/version.h | 2 +-
libavfilter/vf_grayworld.c | 368 +
5 files changed, 383 insertions(+), 1 deletion(-
On Thu, Aug 26, 2021 at 7:53 PM Paul Buxton
wrote:
> Signed-off-by: Paul Buxton
> ---
> doc/filters.texi | 12 ++
> libavfilter/Makefile | 1 +
> libavfilter/allfilters.c | 1 +
> libavfilter/version.h | 2 +-
> libavfilter/vf_grayworld.c | 368
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Saturday, 7 August 2021 07:02
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v2] DXVA2: Add ARGB format
>
> Required for uploading frames with alpha for qsv_overlay
> (v2: remove tab indent)
>
Fixes: signed integer overflow: 9223372034248226491 + 3275247799 cannot be
represented in type 'long'
Fixes: clusterfuzz-testcase-minimized-audio_decoder_fuzzer-4538729166077952
Reported-by: Matt Wolenetz
Signed-off-by: Michael Niedermayer
---
libavformat/mov.c | 2 ++
1 file changed, 2 insert
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 29
libavfilter/Makefile | 1 +
libavfilter/af_atilt.c | 287 +++
libavfilter/allfilters.c | 1 +
4 files changed, 318 insertions(+)
create mode 100644 libavfilter/af_atilt.c
diff --gi
On Tue, Aug 24, 2021 at 12:47 AM Jan Ekström wrote:
>
> ---
> libavcodec/libx264.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
> index d48e142e41..379c167e6f 100644
> --- a/libavcodec/libx264.c
> +++ b/libavcodec/libx264.c
> @@ -870,6 +87
On Sun, Aug 22, 2021 at 11:55 PM Jan Ekström wrote:
>
> Fixes passing through mismatching metadata from the input side
> when RGB input (from f.ex. H.264 or HEVC) gets converted to YCbCr.
>
> Fixes #9132
> ---
> libavfilter/vf_scale.c | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --gi
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Paul B Mahol
> Sent: Thursday, 26 August 2021 09:36
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] Add option for writing
> detailed filtergraph information to file
ping
On Mon, Aug 09, 2021 at 03:26:20AM +0200, Sebastian Kirmayer wrote:
> The previous implementation swapped the two halves of the plaintext. The
> existing tests only decrypted data with a plaintext of all zeroes, which is
> not affected by swapping the halves. Tests which detect the old buggy
Hi,
On Thu, Aug 26, 2021 at 9:06 AM Maryla Ustarroz
wrote:
>
Note top posting is discouraged here [1].
> We've just added a file to libwebp-test-data that covers this case:
> https://chromium.googlesource.com/webm/libwebp-test-data/+/refs/heads/main/dual_transform.webp
> FFmpeg currently fails
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Thursday, 19 August 2021 17:31
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 3/3] lavfi/formats: document the
> negotiation process
>
> Signed-off-by: Nicolas George
> ---
> libavfilter/f
This is a more complete and more flexible alternative to the recently submitted
patch "fftools: add -lavfi_dump option"
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
I'm tagging this patch as 'RFC'. There's no need to tell that this is
duplicating
code
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Thursday, August 26, 2021 5:12 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec: Adjust incorrect error
> output
>
>
>
> > -Original Message-
> >
This is a more complete and more flexible alternative to the recently submitted
patch "fftools: add -lavfi_dump option"
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210823094504.100789-2-geo...@nsup.org/
I'm tagging this patch as 'RFC'. There's no need to tell that this is
duplicating
code
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Wang, Fei W
> Sent: Friday, 27 August 2021 05:05
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec: Adjust incorrect
> error output
>
> > -Original Messag
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Friday, 27 August 2021 05:14
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v3] fftools: Add option for writing
> detailed filtergraph information to file or stdout
>
> This is a more complete a
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Friday, August 27, 2021 12:18 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec: Adjust incorrect error
> output
>
>
>
> > -Original Message-
>
Performance(Less is better):
8bit:
ff_hflip_byte_ssse3 0.61
ff_hflip_byte_avx20.37
ff_hflip_byte_avx512 0.19
16bit:
ff_hflip_short_ssse3 1.27
ff_hflip_short_avx2 0.76
ff_hflip_short_avx512 0.40
Signed-off-by: Wu Jianhua
---
libavfilter/x86/vf_hflip.asm| 23 +
As we all know the 10bit samples would also be stored as a 16bits type,
the condition judgment will lead the SIMD optimizations to be uninitialized
when the depth is 10.
Signed-off-by: Wu Jianhua
---
libavfilter/x86/vf_threshold_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Performance(Less is better)
8bit:
ff_threshold8_sse432.7555351
ff_threshold8_avx232.1713562
ff_threshold8_avx512 32.0103531
16bit:
ff_threshold16_sse4 37.7713432
ff_threshold16_avx2 35.3348312
ff_threshold16_avx512 32.6976166
Signed-off-by: Wu Jianhua
---
lib
Signed-off-by: Wu Jianhua
---
libavfilter/vf_avgblur_vulkan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/vf_avgblur_vulkan.c b/libavfilter/vf_avgblur_vulkan.c
index 1e485061cd..2dbfc947a8 100644
--- a/libavfilter/vf_avgblur_vulkan.c
+++ b/libavfilter/vf_avgblu
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Wang, Fei W
> Sent: Friday, 27 August 2021 06:39
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec: Adjust incorrect
> error output
>
>
>
> > -Original
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft
> Works
> Sent: Friday, August 27, 2021 1:25 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/av1dec: Adjust incorrect error
> output
>
>
>
> > -Original Message-
> >
avcodec/wmaprodec: Return value check for init_get_bits
Similar to CVE-2021-38171 as the second argument for init_get_bits(avpkt and
buf) can be crafted,
a return value check for this function call is necessary.
Also replace init_get_bits with init_get_bits8.
---
libavcodec/wmaprodec.c | 9
Similar to CVE-2021-38171 as the second argument for init_get_bits(avpkt and bu$
a return value check for this function call is necessary.
Also replace init_get_bits with init_get_bits8.
---
libavcodec/wmalosslessdec.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/l
59 matches
Mail list logo
