Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and ffprobe fields (cover letter)

From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: Marth64 <marth64@proxyid.net>
Cc: Kieran Kunhya <kieran618@googlemail.com>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and ffprobe fields (cover letter)
Date: Thu, 30 Jan 2025 06:40:14 +0000
Message-ID: <DM8P223MB036584F6807E5D93469A6776BAE92@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAAhd_PXZ+=eghdH9mLZDZ0cHyRfP7tdAGzkabt_31kbKJBcH3A@mail.gmail.com>

> -----Original Message-----
> From: Marth64 <marth64@proxyid.net>
> Sent: Thursday, January 30, 2025 6:41 AM
> To: Soft Works <softworkz@hotmail.com>
> Cc: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>; Kieran Kunhya <kieran618@googlemail.com>
> Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection
> and ffprobe fields (cover letter)
> 
> > LOL 😊
> lol indeed :)
> 
> > Another use case is in combination with Subtitle Filtering: If
> there's auto-conversion desired in ffmpeg
> Yeah that's reasonable. I would request a manual switch or some other
> way to establish the filter unconditionally, for those who do want to
> operate on the sparse files.

Sure. Either that or filters can always be set up manually as well - whatever Is desired...

The second thing I wanted to talk about with you is extending the analyze_frames feature for more data. If you hadn't done this, I would have submitted something very similar 😊 

The immediate candidates for additional data I'm interested in are HDR10+ side data and DVB subtitles, specifically the target window size, which you would actually want to know beforehand, but DVB subs can appear anywhere or not at all. With analyze_frames and read_intervals it will be possible to define something like 3 or 4 few-minnute time ranges (like start-middle-end) to scan for DVB subs.
There are also other kinds of data which might be of interest, and that's where I'm wondering whether we should keep adding more arrays like streams_with_closed_captions and streams_with_film_grain or whether a more generic would be desireable?

What's even more important for this feature is some kind of auto-exit mechanism similar to this:

Via an option you specify which data you want to scan for - e.g. filmGrain and HDR10+. That would mean that the frames and side data are being processed just like normal, but as soon as all the information has been found, ffprobe would exit instead of running through all defined intervals till the end.

Does that make sense to you?

Best,
sw
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".