From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
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: Tue, 2 Jan 2024 21:05:47 +0000
Message-ID: <CAK+ULv72XvZ65oWn1pHrh+sQKMQhLJArURe2d4tJuf0WX3f0Jw@mail.gmail.com> (raw)
In-Reply-To: <ZZRrf9Snq1Tk37j/@mariano>
>
> > and not the CLI (something this project is unable to understand).
>
> What is exposed by the API is exercised by the CLI (which is a good
> thing for scripting and for testing).
>
The CLI can't just write random binary data to the terminal. What next, raw
frames available via JSON? I'm sure there are users who want that too.
Again, this is something that should either be parsed by FFmpeg or done via
the API.
Kieran
_______________________________________________
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-02 21:06 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 [this message]
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=CAK+ULv72XvZ65oWn1pHrh+sQKMQhLJArURe2d4tJuf0WX3f0Jw@mail.gmail.com \
--to=kierank@obe.tv \
--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