From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 09/11] avcodec/decode: check for global side data in AVCodecContext side data Date: Wed, 4 Oct 2023 00:22:38 -0300 Message-ID: <e1717ddd-ab47-4fdf-85ce-2f7530249df6@gmail.com> (raw) In-Reply-To: <8144112d-046f-46a8-9ee2-dbc26cdb6edf@gmail.com> On 10/3/2023 3:46 PM, James Almer wrote: > On 10/3/2023 9:34 AM, Anton Khirnov wrote: >> Quoting James Almer (2023-09-27 15:12:40) >>> avcodec/decode: check for global side data in AVCodecContext side data >> >> I don't think this makes it clear what this commit actually does. >> Make it something like 'propagate global side data to frames'. >> >>> Signed-off-by: James Almer <jamrial@gmail.com> >>> --- >>> libavcodec/decode.c | 48 +++++++++++++++++++++++++++++++++++++-------- >>> 1 file changed, 40 insertions(+), 8 deletions(-) >>> >>> diff --git a/libavcodec/decode.c b/libavcodec/decode.c >>> index a7196b5740..3b4bb70689 100644 >>> --- a/libavcodec/decode.c >>> +++ b/libavcodec/decode.c >>> @@ -1422,6 +1422,20 @@ static int add_metadata_from_side_data(const >>> AVPacket *avpkt, AVFrame *frame) >>> return av_packet_unpack_dictionary(side_metadata, size, frame_md); >>> } >>> +static const struct { >>> + enum AVPacketSideDataType packet; >>> + enum AVFrameSideDataType frame; >>> +} sd_global_map[] = { >>> + { AV_PKT_DATA_REPLAYGAIN , >>> AV_FRAME_DATA_REPLAYGAIN }, >>> + { AV_PKT_DATA_SPHERICAL, >>> AV_FRAME_DATA_SPHERICAL }, >>> + { AV_PKT_DATA_STEREO3D, AV_FRAME_DATA_STEREO3D }, >>> + { AV_PKT_DATA_AUDIO_SERVICE_TYPE, >>> AV_FRAME_DATA_AUDIO_SERVICE_TYPE }, >>> + { AV_PKT_DATA_MASTERING_DISPLAY_METADATA, >>> AV_FRAME_DATA_MASTERING_DISPLAY_METADATA }, >>> + { AV_PKT_DATA_CONTENT_LIGHT_LEVEL, >>> AV_FRAME_DATA_CONTENT_LIGHT_LEVEL }, >>> + { AV_PKT_DATA_ICC_PROFILE, >>> AV_FRAME_DATA_ICC_PROFILE }, >>> + { AV_PKT_DATA_DYNAMIC_HDR10_PLUS, >>> AV_FRAME_DATA_DYNAMIC_HDR_PLUS }, >>> +}; >>> + >>> int ff_decode_frame_props_from_pkt(const AVCodecContext *avctx, >>> AVFrame *frame, const AVPacket >>> *pkt) >>> { >>> @@ -1429,18 +1443,10 @@ int ff_decode_frame_props_from_pkt(const >>> AVCodecContext *avctx, >>> enum AVPacketSideDataType packet; >>> enum AVFrameSideDataType frame; >>> } sd[] = { >>> - { AV_PKT_DATA_REPLAYGAIN , >>> AV_FRAME_DATA_REPLAYGAIN }, >>> { AV_PKT_DATA_DISPLAYMATRIX, >>> AV_FRAME_DATA_DISPLAYMATRIX }, >> >> Why are you leaving displaymatrix out? > > See the code patch 10/11 removes. Display matrix in global side data is > apparently not meant to be propagated to frames. If i move this line to > the global map, a couple tests change their output due to new side data > in frames. > If you want that to happen (After all, the CLI is not the only library > user), I'd rather remove the skipping code in the CLI first, with the > relevant test refs changes, so this patch is not the one to change them. Actually, both tests use ffprobe, which never injected stream side data into packets before this set, so the ffmpeg code removed in 10/11 makes no difference. Adding DISPLAYMATRIX to the global map here will still mean ffmpeg.c will pass stream side data to decoded frames, though, even if no test covers it. So it would be nice to know why was it being skipped. > >> >> Also, what happens if the same side data is present at both global and >> packet level? Won't you get two instances in the frame? >> I think the correct behaviour would be that packet overrides global. > > I'm keeping the behavior from before this set intact with this at > Andreas' request. > In a previous iteration i ensured packet side data would replace global > side data in the output frames, but Andreas asked me to not do that, as > a decoder could add that same side data type and it should have priority > over container level side data (All entries will be added to the frame > anyway). _______________________________________________ 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:[~2023-10-04 3:22 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-27 13:12 [FFmpeg-devel] [PATCH 00/11 v5] AVCodecContext and AVCodecParameters " James Almer 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 01/11] avcodec/packet: add generic side data helpers James Almer 2023-10-03 12:54 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 02/11] avcodec/codec_par: add side data to AVCodecParameters James Almer 2023-10-03 11:23 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 03/11] avformat/avformat: use the side data from AVStream.codecpar James Almer 2023-10-03 11:38 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 04/11] avcodec/packet: add some documentation for AVPacketSideData James Almer 2023-10-03 11:02 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 05/11] fftools/ffmpeg: stop using AVStream.side_data James Almer 2023-10-03 11:50 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 06/11] fftools/ffplay: " James Almer 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 07/11] fftools/ffprobe: " James Almer 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 08/11] avcodec/hevcdec: check for DOVI configuration record in AVCodecContext side data James Almer 2023-10-03 10:18 ` Anton Khirnov 2023-10-03 19:11 ` James Almer 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 09/11] avcodec/decode: check for global side data " James Almer 2023-10-03 12:34 ` Anton Khirnov 2023-10-03 18:46 ` James Almer 2023-10-04 3:22 ` James Almer [this message] 2023-10-04 14:36 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 10/11] fftools/ffmpeg: stop injecting stream side data in packets James Almer 2023-10-03 11:04 ` Anton Khirnov 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 11/11] fftools/ffplay: " James Almer 2023-10-03 10:11 ` Anton Khirnov 2023-10-03 11:28 ` Anton Khirnov
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=e1717ddd-ab47-4fdf-85ce-2f7530249df6@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