> > 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, for unregistered SEI you don't have a choice. Some encoders put tons of private data in there. Some of the stuff is human readable, some of it isn't. > > 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. 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. I don't understand why any of this is hard to comprehend. 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-requ...@ffmpeg.org with subject "unsubscribe".