Due to making the decode frames context use the coded size, the
filter started to display those artifacts as it reused the input frame's size.
Change it to instead output the real image size for images, not the input.
Patch attached.
>From 93d0b1012012b1a1a8d0701f9c78e4a1a9502d29 Mon Sep 17 00:0
Oct 27, 2023, 09:37 by quinkbl...@foxmail.com:
> From: Zhao Zhili
>
> Move it to transfer_get_formats.
>
Could you backport this, along with the other two patches to the v6.1 branch
too?
Thanks
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
Oct 29, 2023, 05:51 by mich...@niedermayer.cc:
> On Sat, Oct 28, 2023 at 09:23:45PM +0200, Lynne wrote:
>
>> Oct 28, 2023, 18:49 by mich...@niedermayer.cc:
>>
>> > On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote:
>> >
>> >> It's been a while since we've had a release, and we've had
>> >> a l
On Sat, Oct 28, 2023 at 09:23:45PM +0200, Lynne wrote:
> Oct 28, 2023, 18:49 by mich...@niedermayer.cc:
>
> > On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote:
> >
> >> It's been a while since we've had a release, and we've had
> >> a lot of new features in.
> >> We did say we would make rele
Oct 29, 2023, 03:31 by quinkbl...@foxmail.com:
>
> On 2023/10/29 03:32, Lynne wrote:
>
>> Oct 28, 2023, 20:14 byquinkbl...@foxmail.com:
>>
>
> Fixed in patch v4.
>
> Maybe we should export optional_device_exts in API.
>
Patch welcome.
>>
>> Is there no option to let libavutil create the hwdevic
On 2023/10/29 03:32, Lynne wrote:
Oct 28, 2023, 20:14 byquinkbl...@foxmail.com:
From: Zhao Zhili
---
v3: shared vulkan instance between libplacebo and hwcontext
fftools/ffplay.c | 43 ++
fftools/ffplay_renderer.c | 316 +-
fftools/ffplay
From: Zhao Zhili
---
configure | 2 +-
fftools/Makefile | 2 +
fftools/ffplay.c | 46 ++-
fftools/ffplay_renderer.c | 271 ++
fftools/ffplay_renderer.h | 38 ++
5 files changed, 353 insertions(+), 6 deletions(-)
From: Zhao Zhili
---
v4: add more optional extensions
v3: shared vulkan instance between libplacebo and hwcontext
fftools/ffplay.c | 43 +
fftools/ffplay_renderer.c | 393 --
fftools/ffplay_renderer.h | 2 +
3 files changed, 418 insertions(+),
our downstream list shows no maintained users of that release
https://trac.ffmpeg.org/wiki/Downstreams
Signed-off-by: James Almer
---
src/download| 37 -
src/olddownload | 37 +
2 files changed, 37 insertions(+), 37 dele
On Fri, Oct 20, 2023 at 06:01:38PM +0200, Michael Niedermayer wrote:
> our downstream list shows no maintained users of that release
> https://trac.ffmpeg.org/wiki/Downstreams
>
> Signed-off-by: Michael Niedermayer
> ---
> src/download| 36
> src/olddownl
On Sat, Oct 28, 2023 at 12:46:38PM +0200, Niklas Haas wrote:
> On Fri, 27 Oct 2023 23:42:41 +0200 Michael Niedermayer
> wrote:
> > On Fri, Oct 27, 2023 at 07:04:39PM +0200, Niklas Haas wrote:
> > > From: Niklas Haas
> > >
> > > More commonly, this fixes the case of sws_setColorspaceDetails afte
On Sat, 28 Oct 2023 at 18:21, Michael Niedermayer
wrote:
> Hi ronald
>
> On Sat, Oct 28, 2023 at 12:43:15PM -0400, Ronald S. Bultje wrote:
> > Hi Thilo,
> >
> > On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via ffmpeg-devel <
> > ffmpeg-devel@ffmpeg.org> wrote:
> >
> > > What this is about, is
On Sat, Oct 28, 2023 at 08:01:57PM +0200, Michael Niedermayer wrote:
> On Sat, Oct 28, 2023 at 07:21:03PM +0200, Michael Niedermayer wrote:
> > Hi ronald
> >
> > On Sat, Oct 28, 2023 at 12:43:15PM -0400, Ronald S. Bultje wrote:
> > > Hi Thilo,
> > >
> > > On Sat, Oct 28, 2023 at 11:31 AM Thilo Bo
Oct 28, 2023, 20:14 by quinkbl...@foxmail.com:
> From: Zhao Zhili
>
> ---
> v3: shared vulkan instance between libplacebo and hwcontext
>
> fftools/ffplay.c | 43 ++
> fftools/ffplay_renderer.c | 316 +-
> fftools/ffplay_renderer.h | 2 +
> 3 f
Oct 28, 2023, 18:49 by mich...@niedermayer.cc:
> On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote:
>
>> It's been a while since we've had a release, and we've had
>> a lot of new features in.
>> We did say we would make releases more often, and I think
>> it's about time we have a new release
jpeg2000_rct_int_c: 2592.2
jpeg2000_rct_int_rvv_i32: 1154.2
---
libavcodec/riscv/jpeg2000dsp_init.c | 8 ++--
libavcodec/riscv/jpeg2000dsp_rvv.S | 23 +++
2 files changed, 29 insertions(+), 2 deletions(-)
diff --git a/libavcodec/riscv/jpeg2000dsp_init.c
b/libavcod
jpeg2000_ict_float_c: 3112.2
jpeg2000_ict_float_rvv_f32: 1225.0
---
libavcodec/jpeg2000dsp.c| 4 ++-
libavcodec/jpeg2000dsp.h| 1 +
libavcodec/riscv/Makefile | 2 ++
libavcodec/riscv/jpeg2000dsp_init.c | 36 +
libavcodec/riscv/jpeg2000
This is so that they can be loaded from assembler, rather than
duplicated.
---
libavcodec/jpeg2000dsp.c | 3 ++-
libavcodec/jpeg2000dsp.h | 2 ++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavcodec/jpeg2000dsp.c b/libavcodec/jpeg2000dsp.c
index b1bff6d5b1..50bc1ecee6 100644
--
On Sat, Oct 28, 2023 at 8:02 PM Michael Niedermayer
wrote:
> On Sat, Oct 28, 2023 at 07:21:03PM +0200, Michael Niedermayer wrote:
> > Hi ronald
> >
> > On Sat, Oct 28, 2023 at 12:43:15PM -0400, Ronald S. Bultje wrote:
> > > Hi Thilo,
> > >
> > > On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via
From: Zhao Zhili
---
v3: shared vulkan instance between libplacebo and hwcontext
fftools/ffplay.c | 43 ++
fftools/ffplay_renderer.c | 316 +-
fftools/ffplay_renderer.h | 2 +
3 files changed, 355 insertions(+), 6 deletions(-)
diff --git a/ff
From: Zhao Zhili
---
configure | 2 +-
fftools/Makefile | 2 +
fftools/ffplay.c | 46 ++-
fftools/ffplay_renderer.c | 271 ++
fftools/ffplay_renderer.h | 38 ++
5 files changed, 353 insertions(+), 6 deletions(-)
On Sat, Oct 28, 2023 at 07:21:03PM +0200, Michael Niedermayer wrote:
> Hi ronald
>
> On Sat, Oct 28, 2023 at 12:43:15PM -0400, Ronald S. Bultje wrote:
> > Hi Thilo,
> >
> > On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via ffmpeg-devel <
> > ffmpeg-devel@ffmpeg.org> wrote:
> >
> > > What this
Am 28.10.23 um 18:43 schrieb Ronald S. Bultje:
Hi Thilo,
On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
What this is about, is to set up a way to properly spend the SPI money
aside
from travel & hw. Why we should not do it because some compan
Hi ronald
On Sat, Oct 28, 2023 at 12:43:15PM -0400, Ronald S. Bultje wrote:
> Hi Thilo,
>
> On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> > What this is about, is to set up a way to properly spend the SPI money
> > aside
> > from travel
On 10/28/2023 1:49 PM, Michael Niedermayer wrote:
On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote:
It's been a while since we've had a release, and we've had
a lot of new features in.
We did say we would make releases more often, and I think
it's about time we have a new release.
Anything
On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote:
> It's been a while since we've had a release, and we've had
> a lot of new features in.
> We did say we would make releases more often, and I think
> it's about time we have a new release.
>
> Anything anyone wants to have merged or should we
Hi Thilo,
On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> What this is about, is to set up a way to properly spend the SPI money
> aside
> from travel & hw. Why we should not do it because some companies
> beurocracy, I
> cannot see.
>
I since
Hi,
Am 28.10.23 um 16:20 schrieb Ronald S. Bultje:
Hi,
On Thu, Oct 26, 2023 at 11:45 AM Michael Niedermayer
wrote:
This is financial sustainability Plan A (SPI)
ATM SPI has like 150k $, we do not activly seek donations, we do not
currently
use SPI money to fund any development. SPI money is
From: Niklas Haas
PGMYUV seems to be always limited range. This was a format originally
invented by FFmpeg at a time when YUVJ distinguished limited from full
range YUV, and this codec never appeared to output YUVJ in any
circumstance, so hard-coding limited range preserves the status quo.
The o
From: Niklas Haas
When using vf_scale to force a specific output color space, also tag
this on the AVFrame. (Mirroring existing logic for output range)
---
libavfilter/vf_scale.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavfilter/vf_scale.c b/libavfilter/vf_scale.c
index 21cac607
From: Niklas Haas
No need to write a custom string parser when we can just use an integer
option with preset values. The various bits of fallback logic are wholly
redundant with equivalent logic already inside sws_getCoefficients.
Note: I disallowed setting 'out_color_matrix=auto', because this
From: Niklas Haas
YUV->YUV conversions should preserve input range, if the output range is
unspecified. Ensures full-range YUV input comes out as full-range YUV
output by default, even through YUV->YUV pixel format conversions.
---
libavfilter/vf_scale.c | 23 +++
1 file chan
From: Niklas Haas
This code, as written, skips sws_init_context if scale->in_range was not
set, even if scale->in_frame_range is set to something. So this would
hit the 'no sws context' fast path in scale_frame and skip color range
conversion even where technically required. This had the effect o
From: Niklas Haas
Alpha planes must always be full range, so complain loudly if fed
limited range grayscale input.
---
libavfilter/vf_alphamerge.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavfilter/vf_alphamerge.c b/libavfilter/vf_alphamerge.c
index 4bbc06da36..a5f5baf77e 1006
From: Niklas Haas
Alpha planes are explicitly full range, even for limited range YUVA
formats. Mark them as such.
---
libavfilter/vf_extractplanes.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavfilter/vf_extractplanes.c b/libavfilter/vf_extractplanes.c
index 7b7149ab24..ca406ff323
From: Niklas Haas
The documentation states that invalid entries default to SWS_CS_DEFAULT.
A value of 0 is not a valid SWS_CS_*, yet the code incorrectly
hard-codes it to BT.709 coefficients instead of SWS_CS_DEFAULT.
---
libswscale/yuv2rgb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Niklas Haas
This was a complete hack seemingly designed to work around a different
bug, which was fixed in the previous commit. As such, there is no more
reason not to do this, as it simply breaks changing color range in
sws_setColorspaceDetails for no reason.
---
libswscale/utils.c | 4 +-
From: Niklas Haas
More commonly, this fixes the case of sws_setColorspaceDetails after
sws_getContext, since the latter implies sws_init_context.
The problem here is that sws_init_context sets up the range conversion
and fast path tables based on the values of srcRange/dstRange at init
time. Thi
Changes since v1:
- Fixed convert_unscaled setting for alpha blendaway case
- Reworded log message to be less misleading
- Fixed sws_setColorspaceDetails not working for non-8bit formats
- Fixed wrong (undocumented/inconsistent) behavior for AVCOL_SPC_RGB
- Fixed in_color_matrix default value
- Mov
On Fri, 27 Oct 2023 23:42:41 +0200 Michael Niedermayer
wrote:
> the av_log() message will be wrong if this path is unused
Well, this is a problem even if we move the log printing to context
reinit after sws_setColorspaceDetails, because it will still get printed
on the initial init (before range
Hi,
On Thu, Oct 26, 2023 at 11:45 AM Michael Niedermayer
wrote:
> This is financial sustainability Plan A (SPI)
> ATM SPI has like 150k $, we do not activly seek donations, we do not
> currently
> use SPI money to fund any development. SPI money is ultimately controlled
> by
> the FFmpeg communi
Le lauantaina 28. lokakuuta 2023, 16.56.40 EEST Rémi Denis-Courmont a écrit :
> +#include "config.h"
> +#include "libavutil/attributes.h"
> +#include "libavutil/cpu.h"
> +#include "libavcodec/huffyuvdsp.h"
> +
> +void ff_add_int16_rvv(uint16_t *dst, const uint16_t *src, unsigned m, int
> w); +
> +a
add_int16_128_c: 2390.5
add_int16_128_rvv_i32: 832.0
add_int16_rnd_width_c: 2390.2
add_int16_rnd_width_rvv_i32: 832.5
---
libavcodec/huffyuvdsp.c| 4 +++-
libavcodec/huffyuvdsp.h| 2 ++
libavcodec/riscv/Makefile | 2 ++
libavcodec/riscv/huffyuvdsp_init
On Fri, 27 Oct 2023 19:04:44 +0200 Niklas Haas wrote:
> -{ "in_color_matrix", "set input YCbCr type", OFFSET(in_color_matrix),
> AV_OPT_TYPE_STRING, { .str = "auto" }, .flags = FLAGS, "color" },
> -{ "out_color_matrix", "set output YCbCr type",
> OFFSET(out_color_matrix), AV_OPT_TYP
With the rise of object storage, like S3, it is not uncommon to generate
long pre-signed URLs. When a pre-signed URL is generated using a
short-lived credentials it may include a query parameter called
X-Amz-Security-Token that is 4kB on its own.
The current MAX_URL_SIZE will trim the URL with no
restore_rgb_planes10_c: 185852.2
restore_rgb_planes10_rvv_i32: 90130.5
---
libavcodec/riscv/utvideodsp_init.c | 9 +++-
libavcodec/riscv/utvideodsp_rvv.S | 35 ++
2 files changed, 43 insertions(+), 1 deletion(-)
diff --git a/libavcodec/riscv/utvideodsp_init.
restore_rgb_planes_c: 133065.7
restore_rgb_planes_rvv_i32: 33317.2
---
libavcodec/riscv/Makefile | 2 ++
libavcodec/riscv/utvideodsp_init.c | 38 +
libavcodec/riscv/utvideodsp_rvv.S | 53 ++
libavcodec/utvideodsp.c| 4 ++-
On Sat, 28 Oct 2023 12:50:14 +0200 Niklas Haas wrote:
> On Fri, 27 Oct 2023 23:01:25 +0200 Michael Niedermayer
> wrote:
> > On Fri, Oct 27, 2023 at 07:04:42PM +0200, Niklas Haas wrote:
> > > From: Niklas Haas
> > >
> > > This code, as written, skips sws_init_context if scale->in_range was not
On Fri, 27 Oct 2023 23:01:25 +0200 Michael Niedermayer
wrote:
> On Fri, Oct 27, 2023 at 07:04:42PM +0200, Niklas Haas wrote:
> > From: Niklas Haas
> >
> > This code, as written, skips sws_init_context if scale->in_range was not
> > set, even if scale->in_frame_range is set to something. So this
On Fri, 27 Oct 2023 23:42:41 +0200 Michael Niedermayer
wrote:
> On Fri, Oct 27, 2023 at 07:04:39PM +0200, Niklas Haas wrote:
> > From: Niklas Haas
> >
> > More commonly, this fixes the case of sws_setColorspaceDetails after
> > sws_getContext, since the latter implies sws_init_context.
> >
> >
P.S.:
It took some additional efforts to get some benchmarks with proto-RVV.
But here they are:
idctdsp.add_pixels_clamped_c: 259.5
idctdsp.add_pixels_clamped_rvv_i64: 90.5
idctdsp.put_pixels_clamped_c: 186.5
idctdsp.put_pixels_clamped_rvv_i64: 65.5
idctdsp.put_signed_pixels_clamped_c: 209.5
idct
51 matches
Mail list logo
