Quoting James Almer (2024-06-18 21:03:12) > ffprobe is meant to generate parseable output, and if a field is present, it > should be printed even if it has a default value.
This approach implies that adding new fields will change existing output, possibly just by updating the libraries without any changes in ffprobe itself. I was recently bitten by it when adding a new disposition, which suddenly breaks a number of completely unrelated FATE tests. I don't have strong opinions on how ffprobe Should Work(tm), but this result seems annoying in practice at least. -- Anton Khirnov _______________________________________________ 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".
