On Thu, 2 May 2024, James Almer wrote:
On 5/2/2024 6:23 PM, Marton Balint wrote:
On Wed, 1 May 2024, Michael Niedermayer wrote:
This allows detecting issues in side data related code, same as what
framecrc does for before already for packet data itself.
This basically reverts c6ae560a18d67b9ddaa25a0338b7fb55e3312e57.
Can you at least add an option which allows disabling dumping the side
data? Changing the format of framecrc output again and again is not very
The framehash/framemd5 muxer is versioned, which is what you should use if
you want parseable output.
Okay, but then the question is that why framecrc is using different code
and options?
Regards,
Marton
_______________________________________________
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".
