From: Petr Matousek <petr.matousek@comprimato.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Petr Matousek <petr.matousek@comprimato.com>
Subject: [FFmpeg-devel] [PATCH 0/1] fftools/ffprobe: dump contents of the AV_FRAME_DATA_SEI_UNREGISTERED
Date: Mon, 18 Dec 2023 14:58:58 +0000
Message-ID: <20231218145859.1162669-1-petr.matousek@comprimato.com> (raw)
Before this patch being applied the ffprobe just tells the user whether
the H.26[45] User Data Unregistered SEI message is present in the frame side data
or not. After the patch being appliend it also dumps the contents of the data
similar way as for the other already supported frame side data types.
Petr Matousek (1):
fftools/ffprobe: dump contents of the AV_FRAME_DATA_SEI_UNREGISTERED
fftools/ffprobe.c | 15 +++
tests/ref/fate/hevc-dv-rpu | 4 +
tests/ref/fate/hevc-hdr-vivid-metadata | 4 +
tests/ref/fate/hevc-monochrome-crop | 4 +
tests/ref/fate/mov-zombie | 130 ++++++++++++-------------
5 files changed, 92 insertions(+), 65 deletions(-)
--
2.34.1
_______________________________________________
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 reply other threads:[~2023-12-18 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 14:58 Petr Matousek [this message]
2023-12-18 14:58 ` [FFmpeg-devel] [PATCH 1/1] " Petr Matousek
2024-01-02 16:35 ` Derek Buitenhuis
2023-12-18 19:06 ` [FFmpeg-devel] [PATCH 0/1] " Kieran Kunhya
2024-01-02 11:27 ` Stefano Sabatini
2024-01-02 11:34 ` Kieran Kunhya
2024-01-02 20:01 ` Stefano Sabatini
2024-01-02 21:05 ` Kieran Kunhya
2024-01-02 21:09 ` Vittorio Giovara
2024-01-02 21:24 ` Stefano Sabatini
2024-01-02 22:08 ` Kieran Kunhya
2024-01-03 15:44 ` Stefano Sabatini
2024-01-03 17:37 ` Kieran Kunhya
2023-12-18 23:01 ` Stefano Sabatini
2023-12-19 7:39 ` Petr Matoušek
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=20231218145859.1162669-1-petr.matousek@comprimato.com \
--to=petr.matousek@comprimato.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