From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Petr Matousek <petr.matousek@comprimato.com> Subject: Re: [FFmpeg-devel] [PATCH 0/1] fftools/ffprobe: dump contents of the AV_FRAME_DATA_SEI_UNREGISTERED Date: Wed, 3 Jan 2024 16:44:08 +0100 Message-ID: <ZZWAyGGmid4ZEf+0@mariano> (raw) In-Reply-To: <CAK+ULv7BjrZw9+ZgepByahdaSk0uNg53T5BZt8P+2A-Cyvpo9A@mail.gmail.com> On date Tuesday 2024-01-02 22:08:54 +0000, Kieran Kunhya wrote: [...] > The OP wants to test an implementation they have and they should do it > using the API, not using ffprobe to test their third party implementation > of something. > > > "Parsed by FFmpeg" sounds like you are proposing to extend the FFmpeg > > API to parse some more information (about the SEI subtype?) and make > > it available through some more specific SEI side data? > > > > As the OP says, this SEI data is from "MISB ST 0604" which is something > that could be implemented in FFmpeg and parsed properly like all the other > side data instead of just writing random binary data to the terminal. Fine, so you are proposing to extend the parser to put this information in the side data. This makes sense to me and sounds a better approach than the original proposal. @Petr can you update the patch to extend the parser to expose this information? Feel free to ask in case something is not clear (I'm not familiar myself with that part of the code, but I can try to help). _______________________________________________ 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:[~2024-01-03 15:44 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-18 14:58 Petr Matousek 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 [this message] 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=ZZWAyGGmid4ZEf+0@mariano \ --to=stefasab@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=petr.matousek@comprimato.com \ /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