From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v3] avformat/framecrcenc: compute the checksum for side data Date: Sat, 4 May 2024 18:02:25 -0300 Message-ID: <83b46d22-7d4a-4b3b-a9eb-daa99a7599eb@gmail.com> (raw) In-Reply-To: <20240504205857.GW6420@pb2> On 5/4/2024 5:58 PM, Michael Niedermayer wrote: > On Sat, May 04, 2024 at 12:16:00PM -0300, James Almer wrote: >> On 5/4/2024 5:34 AM, Marton Balint wrote: >>> >>> >>> 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? >> >> Originally it was framecrc (using AVAdler) and framemd5 (using AVMD5). The >> latter was renamed/aliased to framehash and made to use the AVHash API, >> which supports all lavu hashing algorithms, and is versioned. >> If anyone cared, framecrc could be also made into an alias of framehash that >> defaults to adler32 output, but it would result in a massive change to >> reference files, if anything because AVHash initializes adler32 with a 1 >> whereas framecrc does it with a 0. > > normally starting adler32 at 0 is bad as one could prefix by a 0 byte with > no checksum change, but given we also show the size that spcific case isnt > an issue > > can we make the initial value for adler32 configureable so as to improve long > term stability of checksums ? (or add a adler32_1 to AVHash) av_hash_init() already initializes adler32 with a 1. No need to do anything there. It's the framecrc muxer that uses adler32 with 0 as init value. > > thx > > [...] > > > _______________________________________________ > 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". _______________________________________________ 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-05-04 21:02 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-30 23:19 Michael Niedermayer 2024-05-02 15:05 ` [FFmpeg-devel] [PATCH] avformat/framecrcenc: support calculating checksum of IAMF " James Almer 2024-05-02 15:16 ` Andreas Rheinhardt 2024-05-02 18:33 ` James Almer 2024-05-02 21:23 ` [FFmpeg-devel] [PATCH v3] avformat/framecrcenc: compute the checksum for " Marton Balint 2024-05-02 21:29 ` James Almer 2024-05-04 8:34 ` Marton Balint 2024-05-04 15:16 ` James Almer 2024-05-04 17:17 ` Marton Balint 2024-05-04 20:58 ` Michael Niedermayer 2024-05-04 21:02 ` James Almer [this message] 2024-05-05 1:45 ` Michael Niedermayer 2024-05-05 1:54 ` James Almer 2024-05-06 1:34 ` Michael Niedermayer 2024-05-02 23:27 ` Michael Niedermayer
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=83b46d22-7d4a-4b3b-a9eb-daa99a7599eb@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /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