Re: [FFmpeg-devel] [PATCH] lavu/hwcontext_qsv: Derive bind flag from frame type if no valid surface

On Ma, 2024-07-29 at 15:27 +, Tong Wu wrote: -Original Message- From: ffmpeg-devel mailto:ffmpeg-devel-boun...@ffmpeg.org>> On Behalf Of fei.w.wang-at-intel@ffmpeg.org Sent: 2024年7月23日 9:27 To: ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH v2 2/2] lavc/qsvdec: Add VVC decoder

On Vr, 2024-07-26 at 04:43 +, Xiang, Haihao wrote: > On Vr, 2024-06-14 at 16:28 +0800, fei.w.wang-at-intel@ffmpeg.org wrote: > > From: Fei Wang > > > > Signed-off-by: Fei Wang > > --- > >  Changelog  | 1 + > >  configure  | 1 + > >  doc/decoders.texi  | 2 +- >

Re: [FFmpeg-devel] [PATCH 02/18] avcodec/pcm-bluray/dvd: Use correct pointer types on BE

Hi On 2024-03-29 00:10:31 +0100, Andreas Rheinhardt wrote: > Signed-off-by: Andreas Rheinhardt > --- > libavcodec/pcm-bluray.c | 5 +++-- > libavcodec/pcm-dvd.c| 2 +- > 2 files changed, 4 insertions(+), 3 deletions(-) > > diff --git a/libavcodec/pcm-bluray.c b/libavcodec/pcm-bluray.c > ind

Re: [FFmpeg-devel] [PATCH 1/2] lavc/vaapi_decode: Make it possible to send multiple slice params buffers

On 2024-05-07 06:59:51 +, Xiang, Haihao wrote: > On So, 2024-04-28 at 09:26 +0200, David Rosca wrote: > > --- > >  libavcodec/vaapi_av1.c    | 2 +- > >  libavcodec/vaapi_decode.c | 3 ++- > >  libavcodec/vaapi_decode.h | 1 + > >  libavcodec/vaapi_h264.c   | 2 +- > >  libavcodec/vaapi_hevc.c   |

Re: [FFmpeg-devel] [PATCH] libavcodec: fix -Wint-conversion in vulkan

On 2024-01-06 22:40:39 +0100, Lynne wrote: > Jan 6, 2024, 07:18 by s...@gentoo.org: > > > > > Sam James writes: > > > >> FIx warnings (soon to be errors in GCC 14, already so in Clang 15): > >> ``` > >> src/libavcodec/vulkan_av1.c: In function ‘vk_av1_create_params’: > >> src/libavcodec/vulkan_av

Re: [FFmpeg-devel] [PATCH] libavcodec: fix -Wint-conversion in vulkan

On 2024-07-30 11:58:15 +0200, Sebastian Ramacher wrote: > On 2024-01-06 22:40:39 +0100, Lynne wrote: > > Jan 6, 2024, 07:18 by s...@gentoo.org: > > > > > > > > Sam James writes: > > > > > >> FIx warnings (soon to be errors in GCC 14, already so in Clang 15): > > >> ``` > > >> src/libavcodec/vulka

[FFmpeg-devel] [PATCH] Revert "lavf/vf_setpts: unset output framerate"

This reverts commit 43fd3d5df6a19fc768a33e37855aa7f8c7050cf0. Fixes: 43fd3d5df6a1 ("lavf/vf_setpts: unset output framerate") Fixes: #11086 Signed-off-by: Arkadiusz Hiler --- libavfilter/setpts.c | 17 +-- tests/ref/fate/filter-setpts | 89 +++- 2 files

Re: [FFmpeg-devel] [PATCH] Revert "lavf/vf_setpts: unset output framerate"

> 在 2024年7月30日，下午8:19，Arkadiusz Hiler 写道： > > This reverts commit 43fd3d5df6a19fc768a33e37855aa7f8c7050cf0. > > Fixes: 43fd3d5df6a1 ("lavf/vf_setpts: unset output framerate") > Fixes: #11086 It’s a bug of svtav1 encoder to not support VFR. You can use -enc_time_base as a workaround. > Signe

Re: [FFmpeg-devel] [PATCH 1/4] swscale/yuv2rgb: prepare YUV2RGBFUNC macro for multi-planar rgb

On Tue, Jul 23, 2024 at 2:46 PM Ramiro Polla wrote: > This will be used in the upcoming yuv42{0,2}p -> gbrp unscaled > colorspace converters. ping on this patchset. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinf

[FFmpeg-devel] [PATCH 0/2] Interpret a degenerate SAR as 1/1.

I came across some H.264 files in the wild whose SAR is set to 20480/0. The files are provided by the Ubisoft game OddBallers, and are seemingly accepted and played properly when the game is played on Windows (thus using the Microsoft Media Foundations implementation). When running the game with W

[FFmpeg-devel] [PATCH 1/2] avcodec/h2645_vui: Interpret a degenerate SAR as 1/1.

The specification doesn't say what should happen in this case. Other implementations (e.g., Microsoft's Media Foundations) seem to interpret this as 1/1. Signed-off-by: Giovanni Mascellani --- libavcodec/h2645_vui.c | 4 1 file changed, 4 insertions(+) diff --git a/libavcodec/h2645_vui.c b

[FFmpeg-devel] [PATCH 2/2] avcodec/evc_ps: Interpret a degenerate SAR as 1/1.

The specification doesn't say what should happen in this case. Other implementations (e.g., Microsoft's Media Foundations) seem to interpret this as 1/1. Signed-off-by: Giovanni Mascellani --- libavcodec/evc_ps.c | 4 1 file changed, 4 insertions(+) diff --git a/libavcodec/evc_ps.c b/libav

Re: [FFmpeg-devel] [PATCH] Revert "lavf/vf_setpts: unset output framerate"

Quoting Arkadiusz Hiler (2024-07-30 14:19:25) > This reverts commit 43fd3d5df6a19fc768a33e37855aa7f8c7050cf0. Rejected, unsetting framerate is in general correct. -- Anton Khirnov ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org

[FFmpeg-devel] [PATCH] lavu/riscv: Fallback to getauxval() for cpu flags

Signed-off-by: Nathan E. Egge --- libavutil/riscv/cpu.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/libavutil/riscv/cpu.c b/libavutil/riscv/cpu.c index e035f4b024..13b939b9d9 100644 --- a/libavutil/riscv/cpu.c +++ b/libavutil/riscv/cpu.c @@ -90,7 +90,8 @@ int f

[FFmpeg-devel] [PATCH 0/2] some cleanups for compat/w32dlfcn.h

I have only tested that it builds, but not that it runs on a real Windows system. Ramiro Polla (2): compat/w32dlfcn: remove backup definitions for safe LoadLibrary flags compat/w32dlfcn: remove support for pre-KB2533623 Win7 systems compat/w32dlfcn.h | 58

[FFmpeg-devel] [PATCH 2/2] compat/w32dlfcn: remove support for pre-KB2533623 Win7 systems

The KB2533623 security update has been released 13 years ago and Windows 7 has reached end of extended support 4 years ago. --- compat/w32dlfcn.h | 52 --- 1 file changed, 52 deletions(-) diff --git a/compat/w32dlfcn.h b/compat/w32dlfcn.h index 8ae718f4

[FFmpeg-devel] [PATCH 1/2] compat/w32dlfcn: remove backup definitions for safe LoadLibrary flags

Since we now expect C17, it is safe to assume that the toolchain will have these flags defined. --- compat/w32dlfcn.h | 6 -- 1 file changed, 6 deletions(-) diff --git a/compat/w32dlfcn.h b/compat/w32dlfcn.h index ac20e83a7a..8ae718f4bd 100644 --- a/compat/w32dlfcn.h +++ b/compat/w32dlfcn.h @

Re: [FFmpeg-devel] [PATCH v3 2/2] libavformat/vapoursynth: Update to API version 4, load library at runtime

On Mon, Jul 29, 2024 at 5:56 AM Stefan Oltmanns via ffmpeg-devel wrote: > Am 28.07.24 um 15:15 schrieb Ramiro Polla: > > I think calling win32_dlopen() with a full path will be problematic for > > systems without KB2533623. win32_dlopen() might need to be fixed in a > > separate patch. > > Yes, wi

[FFmpeg-devel] [PATCH] avformat/mov: support sidx reference_type = 1

--- libavformat/mov.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/libavformat/mov.c b/libavformat/mov.c index 1052691936..38f015a766 100644 --- a/libavformat/mov.c +++ b/libavformat/mov.c @@ -5964,11 +5964,10 @@ static int mov_read_sidx(MOVContext *c, AVIOContext *p

Re: [FFmpeg-devel] [PATCH 2/2] compat/w32dlfcn: remove support for pre-KB2533623 Win7 systems

Le tiistaina 30. heinäkuuta 2024, 17.09.15 EEST Ramiro Polla a écrit : > The KB2533623 security update has been released 13 years ago and > Windows 7 has reached end of extended support 4 years ago. No objections, but what will this imply in terms of which Windows versions FFmpeg supports? -- 雷

Re: [FFmpeg-devel] [PATCH 1/2] compat/w32dlfcn: remove backup definitions for safe LoadLibrary flags

On 7/30/2024 11:09 AM, Ramiro Polla wrote: Since we now expect C17, it is safe to assume that the toolchain will have these flags defined. We expect C11, but probe for C17 and use it if available. --- compat/w32dlfcn.h | 6 -- 1 file changed, 6 deletions(-) diff --git a/compat/w32dlfc

Re: [FFmpeg-devel] [PATCH] lavu/riscv: Fallback to getauxval() for cpu flags

Le tiistaina 30. heinäkuuta 2024, 17.07.52 EEST Nathan E. Egge a écrit : > Signed-off-by: Nathan E. Egge > --- > libavutil/riscv/cpu.c | 11 +++ > 1 file changed, 7 insertions(+), 4 deletions(-) > > diff --git a/libavutil/riscv/cpu.c b/libavutil/riscv/cpu.c > index e035f4b024..13b939b9d9

Re: [FFmpeg-devel] [PATCH 2/2] compat/w32dlfcn: remove support for pre-KB2533623 Win7 systems

On Tue, Jul 30, 2024 at 5:17 PM Rémi Denis-Courmont wrote: > Le tiistaina 30. heinäkuuta 2024, 17.09.15 EEST Ramiro Polla a écrit : > > The KB2533623 security update has been released 13 years ago and > > Windows 7 has reached end of extended support 4 years ago. > > No objections, but what will t

[FFmpeg-devel] [PATCHv2] lavc/h264dsp: stick R-V V biweight to 16-bit

T-Head C908 (ns): h264_biweight2_8_c:2414.5 h264_biweight2_8_rvv_i32: 701.8 (before) h264_biweight2_8_rvv_i32: 468.5 (after) h264_biweight4_8_c:4655.3 h264_biweight4_8_rvv_i32: 1377.5 (before) h264_biweight4_8_rvv_i32: 931.8 (after) h264_biweight8_8_c:9701.5 h264_biwe

Re: [FFmpeg-devel] [PATCH] avformat/mov: support sidx reference_type = 1

On 7/30/2024 11:56 AM, jiangjie wrote: --- libavformat/mov.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/libavformat/mov.c b/libavformat/mov.c index 1052691936..38f015a766 100644 --- a/libavformat/mov.c +++ b/libavformat/mov.c @@ -5964,11 +5964,10 @@ static int m

[FFmpeg-devel] [PATCH] lavc/h264dsp: stick R-V V weight to 16-bit precision

T-Head C908 (ns): h264_weight2_8_c:1607.8 h264_weight2_8_rvv_i32: 515.0 (before) h264_weight2_8_rvv_i32: 348.5 (after) h264_weight4_8_c:2255.8 h264_weight4_8_rvv_i32: 1015.0 (before) h264_weight4_8_rvv_i32: 691.0 (after) h264_weight8_8_c:3857.5 h264_weight8_8_rvv_i32:

Re: [FFmpeg-devel] [PATCH 1/4] lavc/vp8dsp: R-V V 256 bilin,epel

Hi, these four patches have v2 (although the first one seems to be the same). From my understanding, moving from supporting only 128b to adding 256b versions can simultaneously improve LMUL and solve some issues related to insufficient vector registers (vvc, vp9). This can be very helpful in certa

[FFmpeg-devel] [PATCH] fftools/ffmpeg: show video stats in progress output without filters

Since ffmpeg 6.1 video stats are accidentally hidden from progress output if no filters are used. This patch re-enables video stats (like frames=) in the progress output. --- Changelog| 1 + fftools/ffmpeg.c | 8 +--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/Chang

Re: [FFmpeg-devel] [PATCH v2] libavfilter: add PipeWire-based grab

- On Jul 28, 2024, at 10:53 AM, Quack Doc quackdoct...@gmail.com wrote: > Is it possible to use this without using the portals API and without > systemd? That would be much appreciated if so since the portal is not very > flexible. I don't like the portals API either and would rather not have

[FFmpeg-devel] [PATCH] avcodec/av1_vaapi: Enable AV1Profile2 VAAPI support.

AV1Profile2 VAAPI is supported and tested on AMD VCN5. Signed-off-by: David (Ming Qiang) Wu --- libavcodec/av1dec.c | 3 +++ libavcodec/vaapi_decode.c | 3 +++ 2 files changed, 6 insertions(+) diff --git a/libavcodec/av1dec.c b/libavcodec/av1dec.c index 1d5b9ef4f4..77f63661a0 100644 --- a

Re: [FFmpeg-devel] [PATCH] avcodec/h264_mp4toannexb: Prepend SPS/PPS to buffering period SEI

On Mon, 22 Jul 2024 at 17:17, Timo Rothenpieler wrote: > > On 23/07/2024 01:01, Josh Allmann wrote: > > On Tue, 9 Jul 2024 at 12:06, Josh Allmann wrote: > >> > >> Encoders may emit a buffering period SEI without a corresponding > >> SPS/PPS if the SPS/PPS is carried out-of-band, eg with avcc. > >

Re: [FFmpeg-devel] [PATCH v4 1/3] avcodec/jpeg2000dec: Add support for CAP and CPF markers

fre 2024-07-26 klockan 23:29 +0200 skrev Michael Niedermayer: > On Thu, Jul 25, 2024 at 05:06:04PM -0700, Pierre-Anthony Lemieux > wrote: > > On Thu, Jul 25, 2024 at 2:17 AM Tomas Härdin > > wrote: > > > > > > sön 2024-07-21 klockan 14:07 +0900 skrev Pierre-Anthony Lemieux: > > > > On Sat, Jul 20

Re: [FFmpeg-devel] [PATCH v2 1/1] lavfi/vf_gopromax_opencl: add GoPor Max 360 video filter

On Mon, Jul 29, 2024 at 01:30:34AM +0900, TADANO Tokumei wrote: > On 2024/07/28 18:26, Michael Niedermayer wrote: > > On Sun, Jul 28, 2024 at 01:42:09AM +0900, TADANO Tokumei wrote: > > > > > > On 2024/07/27 13:30, TADANO Tokumei wrote: > > > > Add an OpenCL filter for filtering GoPro Max native .

Re: [FFmpeg-devel] [PATCH 0/2] Interpret a degenerate SAR as 1/1.

On Tue, Jul 30, 2024 at 03:11:47PM +0200, Giovanni Mascellani wrote: > I came across some H.264 files in the wild whose SAR is set to > 20480/0. The files are provided by the Ubisoft game OddBallers, and > are seemingly accepted and played properly when the game is played on > Windows (thus using t

Re: [FFmpeg-devel] [PATCH 0/2] Interpret a degenerate SAR as 1/1.

On 7/30/2024 5:54 PM, Michael Niedermayer wrote: On Tue, Jul 30, 2024 at 03:11:47PM +0200, Giovanni Mascellani wrote: I came across some H.264 files in the wild whose SAR is set to 20480/0. The files are provided by the Ubisoft game OddBallers, and are seemingly accepted and played properly when

Re: [FFmpeg-devel] [PATCH 0/2] Interpret a degenerate SAR as 1/1.

On Tue, Jul 30, 2024 at 06:15:30PM -0300, James Almer wrote: > On 7/30/2024 5:54 PM, Michael Niedermayer wrote: > > On Tue, Jul 30, 2024 at 03:11:47PM +0200, Giovanni Mascellani wrote: > > > I came across some H.264 files in the wild whose SAR is set to > > > 20480/0. The files are provided by the

Re: [FFmpeg-devel] [PATCH v4 1/3] avcodec/jpeg2000dec: Add support for CAP and CPF markers

On Tue, Jul 30, 2024 at 10:22:37PM +0200, Tomas Härdin wrote: > fre 2024-07-26 klockan 23:29 +0200 skrev Michael Niedermayer: > > On Thu, Jul 25, 2024 at 05:06:04PM -0700, Pierre-Anthony Lemieux > > wrote: > > > On Thu, Jul 25, 2024 at 2:17 AM Tomas Härdin > > > wrote: > > > > > > > > sön 2024-07

Re: [FFmpeg-devel] [PATCH] Check codec_whitelist before reinitializing AVCtx.priv_data.

I realized there are a couple more allocations that can be skipped here when a codec is not on the allow list. Here's the updated patch. - dale On Mon, Jul 29, 2024 at 10:19 AM Dale Curtis wrote: > This ensures that if a codec isn't on codec_whitelist, its VUI > information can still be populat