Re: [FFmpeg-devel] [PATCH] fftools: notify user of flags upon loglevel parse failure

2025-02-22 Thread Gyan Doshi
On 2025-02-21 05:34 pm, Gyan Doshi wrote: On 2025-02-21 04:34 pm, Andreas Rheinhardt wrote: Gyan Doshi: On 2025-02-21 02:21 pm, Andreas Rheinhardt wrote: Gyan Doshi: ---    fftools/opt_common.c | 5 +    1 file changed, 5 insertions(+) diff --git a/fftools/opt_common.c b/fftools/opt_

Re: [FFmpeg-devel] [PATCH] ffmpeg_demux: add option readrate_catchup

2025-02-22 Thread Gyan Doshi
On 2025-02-18 03:16 pm, Gyan Doshi wrote: At present, if reading from a readrate-limited input is stalled, then upon resumption, ffmpeg will read the input without any throttle till the average readrate matches the specified readrate. This new option allows to set a speed limit when reading i

Re: [FFmpeg-devel] [PATCH v3 2/2] lavc/vvc: Ensure subpictures don't overlap

2025-02-22 Thread Frank Plowman
On 22/02/2025 07:51, Nuo Mi wrote: > From: Frank Plowman > > This is essentially a re-implementation of > https://patchwork.ffmpeg.org/project/ffmpeg/patch/20241005223955.54158-1-p...@frankplowman.com/ > > That patch was not applied last time. Instead we opted to identify > issues which could b

Re: [FFmpeg-devel] [PATCH] libavcodec/cuviddec.c: increase CUVID_DEFAULT_NUM_SURFACES

2025-02-22 Thread Timo Rothenpieler
On 22.02.2025 03:52, Scott Theisen wrote: On 2/21/25 08:26, Timo Rothenpieler wrote: On 20.02.2025 21:37, Scott Theisen wrote: The default value of CuvidContext::nb_surfaces was reduced from 25 to 5 (as (CUVID_MAX_DISPLAY_DELAY + 1)) in 402d98c9d467dff6931d906ebb732b9a00334e0b. In cuvid_is_b

Re: [FFmpeg-devel] [PATCH] avcodec/libsvtav1: unbreak build with latest svtav1

2025-02-22 Thread Gyan Doshi
On 2025-02-22 06:47 pm, Timo Rothenpieler wrote: On 22.02.2025 06:14, Gyan Doshi wrote: SVT-AV1 made a change in their public API in 988e930c but without a version bump or any other accessible marker, thus breaking ffmpeg build with current versions of SVT-AV1. They have finally bumped versio

Re: [FFmpeg-devel] [PATCH] avcodec/libsvtav1: unbreak build with latest svtav1

2025-02-22 Thread Timo Rothenpieler
On 22.02.2025 06:14, Gyan Doshi wrote: SVT-AV1 made a change in their public API in 988e930c but without a version bump or any other accessible marker, thus breaking ffmpeg build with current versions of SVT-AV1. They have finally bumped versions a month later, so check added. --- libavcodec/l

Re: [FFmpeg-devel] I've written a filter in Rust

2025-02-22 Thread Rémi Denis-Courmont
Le perjantaina 21. helmikuuta 2025, 15.18.06 UTC+2 Lynne a écrit : > > - 1: get a working and efficient implementation of the SORT algorithm. > > - 2: start learning Rust again (it's been ~5 years since I used it) > > - 3: learn more about the libavfilter codebase > > - 4: evaluate whether Rust cou

Re: [FFmpeg-devel] I've written a filter in Rust

2025-02-22 Thread Rémi Denis-Courmont
Le perjantaina 21. helmikuuta 2025, 20.02.16 UTC+2 Tomas Härdin a écrit : > The above said, I'm not against Rust. It has some nice properties. But > it does not seem very "stable" so far. Perhaps this has changed in > recent years.. IME, it's become very usable for user-space code. Bare metal stil

[FFmpeg-devel] [PATCH v3 2/2] lavc/vvc: Ensure subpictures don't overlap

2025-02-22 Thread Nuo Mi
From: Frank Plowman This is essentially a re-implementation of https://patchwork.ffmpeg.org/project/ffmpeg/patch/20241005223955.54158-1-p...@frankplowman.com/ That patch was not applied last time. Instead we opted to identify issues which could be caused by invalid subpicture layouts and remedy

Re: [FFmpeg-devel] [PATCH 2/2] lavc/vvc: Ensure subpictures don't overlap

2025-02-22 Thread Nuo Mi
On Thu, Feb 20, 2025 at 4:29 AM Frank Plowman wrote: > Hi, > > Thanks for your review. > > On 16/02/2025 15:19, Nuo Mi wrote: > > Hi Frank, > > Thank you for the patch. > > > > On Sun, Feb 9, 2025 at 11:45 PM Frank Plowman > wrote: > > > >> This is essentially a re-implementation of > >> > >> >