On date Tuesday 2024-01-02 21:05:47 +0000, Kieran Kunhya wrote: > > > > > 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. This is already available through the -show_data option since years (but note that the binary data is rendered as a data dump). My point is that we might opt-out the verbose dump if we have a clear criterion for opting-in/out. For example -show_data is off by default, and we could mark special side-data fields with some flags to opt them out by default. > Again, this is something that should either be parsed by FFmpeg or done via > the API. I still don't understand. The CLI exposes what the API does, so if the API can't do it, the CLI cannot do either. "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? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
