Re: [FFmpeg-devel] [PATCH] avutil/frame: use the maximum compile time supported alignment for strides

2024-08-02 Thread Rémi Denis-Courmont
Le keskiviikkona 31. heinäkuuta 2024, 15.55.23 EEST James Almer a écrit : > This puts lavu frame buffer allocator helpers in sync with lavc's decoder > frame buffer allocator's STRIDE_ALIGN define. STRIDE_ALIGN can go down to 16 or even 8 bytes though. What is the reason for capping at 32 bytes h

Re: [FFmpeg-devel] [PATCH 01/22] avutil/dovi_meta: document static vs dynamic ext blocks

2024-08-02 Thread Cosmin Stejerean via ffmpeg-devel
> On Jul 31, 2024, at 5:14 AM, Niklas Haas wrote: > > On Sun, 28 Jul 2024 12:25:06 +0200 Niklas Haas wrote: >> From: Niklas Haas >> >> --- >> libavutil/dovi_meta.h | 28 +++- >> 1 file changed, 15 insertions(+), 13 deletions(-) >> >> diff --git a/libavutil/dovi_meta.h

[FFmpeg-devel] [PATCH v4 1/1] lavfi/vf_gopromax_opencl: add GoPro Max 360 video filter

2024-08-02 Thread TADANO Tokumei
Add an OpenCL filter for filtering GoPro Max native .360 files into standard equirectangular or youtube equiangular cubemap (eac) projection. The .360 file contains separated two video streams. This filter combine two streams into single stream with standard format. --- configure

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

2024-08-02 Thread TADANO Tokumei
This is updated patch of: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=3943 I contacted to Ronan LE MEILLAT and agreed with him to submit new patch. Abstruct of GoPro Max .360 video file format is described in: https://gopro.com/news/max-tech-specs-stitching-resolution The specificati

[FFmpeg-devel] [PATCH] Fix nullptr dereference with invalid encryption metadata.

2024-08-02 Thread Dale Curtis
Found by fuzzer. Bug: https://crbug.com/356720789 Signed-off-by: Dale Curtis --- libavformat/mov.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) mov_fuzz_fix_v1.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel

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

2024-08-02 Thread François-Simon Fauteux-Chapleau
- On Aug 2, 2024, at 12:11 PM, Quack Doc quackdoct...@gmail.com wrote: > Pipewire video capture is more generic. Some compositors like weston > support pipewire as a backend without portals. Gamescope also creates a > pipewire output without need for portals, it would be *really* nice to > supp

Re: [FFmpeg-devel] [PATCH] avutil/frame: use the maximum compile time supported alignment for strides

2024-08-02 Thread James Almer
On 7/31/2024 9:55 AM, James Almer wrote: This puts lavu frame buffer allocator helpers in sync with lavc's decoder frame buffer allocator's STRIDE_ALIGN define. Remove the comment about av_cpu_max_align() while at it as using it is not ideal when CPU flags can be changed mid process. Should fix

Re: [FFmpeg-devel] [PATCH 1/4] lavc/vp9dsp: R-V V mc bilin h v

2024-08-02 Thread Rémi Denis-Courmont
Looks OK, but missing CFI landing pads. -- Rémi Denis-Courmont http://www.remlab.net/ ___ 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

Re: [FFmpeg-devel] [PATCH 1/4] lavc/vp9dsp: R-V V mc bilin h v

2024-08-02 Thread Rémi Denis-Courmont
Looks OK, but missing CFI landing pads. -- Rémi Denis-Courmont http://www.remlab.net/ ___ 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

Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Rework on DTS generation

2024-08-02 Thread Timo Rothenpieler
On 02.08.2024 18:54, Dennis Mungai wrote: On Fri, 2 Aug 2024, 19:28 Timo Rothenpieler, wrote: applied, thanks This is a bugfix, can it be backported to release 6.x and 7.x? It's also a quite substantial change in behaviour, so I'd like to wait with that for a while. ___

Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Rework on DTS generation

2024-08-02 Thread Dennis Mungai
On Fri, 2 Aug 2024, 19:28 Timo Rothenpieler, wrote: > applied, thanks > This is a bugfix, can it be backported to release 6.x and 7.x? > ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubs

[FFmpeg-devel] [PATCH] Don't reallocate a AVCodecContext when closing a non-open codec.

2024-08-02 Thread Dale Curtis
This results in an unnecessary ~800k allocation with H.264. A nearby callsite uses avcodec_is_open() to avoid this, so do the same when exiting avformat_find_stream_info(). Signed-off-by: Dale Curtis --- libavformat/demux.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) no_real

Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Rework on DTS generation

2024-08-02 Thread Timo Rothenpieler
applied, thanks ___ 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".

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

2024-08-02 Thread Quack Doc
Pipewire video capture is more generic. Some compositors like weston support pipewire as a backend without portals. Gamescope also creates a pipewire output without need for portals, it would be *really* nice to support gamescope capture with this. Pipewire also gives access to video devices direct

Re: [FFmpeg-devel] [PATCH v2] avcodec/cuvidddec: Guess pixel format based on probed bit depth and chroma sampling

2024-08-02 Thread Timo Rothenpieler
On 02.08.2024 16:05, Roman Arzumanyan wrote: Thanks a lot Timo ! Just for my own education: in my application I follow the usual sequence of API calls to init hw device context and open the codec. What's the right place to probe the input? I was under the impression that it's done within avforma

[FFmpeg-devel] [PATCH] lavc/videodsp: work-around LLVM-as

2024-08-02 Thread Rémi Denis-Courmont
For some reason, it can't handle the normal syntax for an address operand without an offset, so add a dummy zero offset. --- libavcodec/riscv/videodsp.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/riscv/videodsp.S b/libavcodec/riscv/videodsp.S index 72bf70ec52..0

Re: [FFmpeg-devel] [PATCH v2] avcodec/cuvidddec: Guess pixel format based on probed bit depth and chroma sampling

2024-08-02 Thread Roman Arzumanyan
Thanks a lot Timo ! Just for my own education: in my application I follow the usual sequence of API calls to init hw device context and open the codec. What's the right place to probe the input? I was under the impression that it's done within avformat_find_stream_info(). пт, 2 авг. 2024 г. в 16:

Re: [FFmpeg-devel] [PATCH v2] avcodec/cuvidddec: Guess pixel format based on probed bit depth and chroma sampling

2024-08-02 Thread Timo Rothenpieler
On 02/08/2024 15:31, Roman Arzumanyan wrote: Hello world, Please find v2 of the previous patch attached. Both bit depth and chroma sampling (420 and 444 as supported by Nvdec) are now taken into account when selecting sw_pix_fmt. It's actually AV_PIX_FMT_YUV444P16 for both 10 and 12 bit, due t

[FFmpeg-devel] [PATCH v2] avcodec/cuvidddec: Guess pixel format based on probed bit depth and chroma sampling

2024-08-02 Thread Roman Arzumanyan
Hello world, Please find v2 of the previous patch attached. Both bit depth and chroma sampling (420 and 444 as supported by Nvdec) are now taken into account when selecting sw_pix_fmt. From a0c0c8497e75987ae771a466c9f0fce5c3ef106c Mon Sep 17 00:00:00 2001 From: Roman Arzumanyan Date: Thu, 1 Aug 2

Re: [FFmpeg-devel] [PATCH 2/3] avcodec/vvc/cabac: remove vvc_refill2

2024-08-02 Thread Nuo Mi
On Wed, Jul 24, 2024 at 2:56 AM wrote: > From: Wu Jianhua > > See https://github.com/ffvvc/FFmpeg/issues/178 > > Signed-off-by: Wu Jianhua > Hi Jianhua, https://patchwork.ffmpeg.org/check/105889/ build failed. Could you help check? thank you > --- > libavcodec/vvc/cabac.c | 28 +---

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

2024-08-02 Thread Jan Garcia via ffmpeg-devel
Since ffmpeg 6.1 video stats are accidentally hidden from streamcopy progress output. This patch re-enables video stats (like frames=) in the progress output. --- fftools/ffmpeg.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c index

Re: [FFmpeg-devel] [PATCH] avcodec/cuvidddec: Guess pixel format based on probed bit depth

2024-08-02 Thread Roman Arzumanyan
Hi Timo, > Why can't the application simply also look at the probed format? It's certainly possible, but in my opinion it makes sense to improve the codec behavior. All required information is already there, why not return the correct value ? > The 12 bit format should be AV_PIX_FMT_P016. > Also,