From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3] avformat/apvdec: export color information
Date: Sun, 27 Apr 2025 17:55:37 -0300
Message-ID: <6573a68e-f65b-4ad2-9aa2-2f4583c8f123@gmail.com> (raw)
In-Reply-To: <GV1P250MB073731F016394B211DA118318F862@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
[-- Attachment #1.1.1: Type: text/plain, Size: 1429 bytes --]
On 4/27/2025 5:50 PM, Andreas Rheinhardt wrote:
> James Almer:
>> apv_read_header() reads enough information that the generic demux code doesn't
>> attempt to read a frame to fill missing fields in codecpar, so make sure it's
>> set here.
>>
>> Signed-off-by: James Almer <jamrial@gmail.com>
>> ---
>> libavformat/apvdec.c | 40 ++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 38 insertions(+), 2 deletions(-)
>>
>> diff --git a/libavformat/apvdec.c b/libavformat/apvdec.c
>> index e1ac34b003..9f8af35567 100644
>> --- a/libavformat/apvdec.c
>> +++ b/libavformat/apvdec.c
>> @@ -39,6 +39,11 @@ typedef struct APVHeaderInfo {
>> uint8_t chroma_format_idc;
>> uint8_t bit_depth_minus8;
>>
>> + uint8_t color_primaries;
>> + uint8_t transfer_characteristics;
>> + uint8_t matrix_coefficients;
>> + uint8_t full_range_flag;
>> +
>> enum AVPixelFormat pixel_format;
>> } APVHeaderInfo;
>>
>> @@ -111,6 +116,31 @@ static int apv_extract_header_info(APVHeaderInfo *info,
>> if (zero != 0)
>> return AVERROR_INVALIDDATA;
>>
>> + // Return if this function was called by apv_probe()
>
> Why do you want to make probing less strict?
I'm not making it less strict, just ensuring apv_probe() behaves the
exact same.
In any case, I'm withdrawing this patch in favor of a more proper
approach. Will send it in a bit.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next prev parent reply other threads:[~2025-04-27 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 17:53 [FFmpeg-devel] [PATCH] " James Almer
2025-04-27 18:29 ` Mark Thompson
2025-04-27 19:22 ` James Almer
2025-04-27 19:35 ` [FFmpeg-devel] [PATCH v2] " James Almer
2025-04-27 19:42 ` [FFmpeg-devel] [PATCH v3] " James Almer
2025-04-27 20:50 ` Andreas Rheinhardt
2025-04-27 20:55 ` James Almer [this message]
2025-04-27 18:57 ` [FFmpeg-devel] [PATCH] " Andreas Rheinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6573a68e-f65b-4ad2-9aa2-2f4583c8f123@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git