From: "Tomas Härdin" <git@haerdin.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/8] libavformat/flacdec: Export samples md5 as metadata Date: Wed, 12 Feb 2025 12:27:06 +0100 Message-ID: <8f2c6649b21ba3e412e45aa24277c22a439d7c07.camel@haerdin.se> (raw) In-Reply-To: <AS8P250MB07442743295AC904FAC34F6B8FFC2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> ons 2025-02-12 klockan 12:14 +0100 skrev Andreas Rheinhardt: > Tomas Härdin: > > > > > > _______________________________________________ > > 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". > > This will forward wrong/outdated metadata if only part of a file is > copied. No? lavc/flacenc computes md5 from the actual samples and puts it in the extradata. If you mean incomplete file copy (cp) rather then ffmpeg -acodec copy then this will output what the user is likely interested in: the MD5 of the original data. This allows them to check that the file decodes correctly. This also applies to incomplete remuxing, which also won't recompute the MD5 as it is, AFAICT. But, this patch concerns the demuxer side, not transcoding or remuxing. > Apart from that, is it really necessary to export the md5 as > metadata given that it is very easily obtainable from the extradata? I'm not sure if our users know that. But yes metadata can be dumped and then cut can be used to extract the MD5. But as Michael points out, flac isn't the only codec with MD5 hashes. /Tomas _______________________________________________ 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:[~2025-02-12 11:27 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-05 14:18 [FFmpeg-devel] [PATCH 1/8] avformat/http: Return EIO for prematurely broken connection Tomas Härdin 2025-02-05 14:19 ` [FFmpeg-devel] [PATCH 2/8] libavcodec/wmadec: Return AVERROR_INVALIDDATA on decoding errors Tomas Härdin 2025-02-05 16:28 ` Marth64 2025-02-05 14:20 ` [FFmpeg-devel] [PATCH 3/8] libavformat/flacdec: Export samples md5 as metadata Tomas Härdin 2025-02-06 15:07 ` Michael Niedermayer 2025-02-12 10:56 ` Tomas Härdin 2025-02-12 11:14 ` Andreas Rheinhardt 2025-02-12 11:27 ` Tomas Härdin [this message] 2025-02-12 12:27 ` Andreas Rheinhardt 2025-02-12 13:32 ` Tomas Härdin 2025-02-05 14:20 ` [FFmpeg-devel] [PATCH 4/8] avformat/flacdec: Return correct error-codes on read-failure Tomas Härdin 2025-02-06 15:01 ` Michael Niedermayer 2025-02-05 14:21 ` [FFmpeg-devel] [PATCH 5/8] rtmp: Set correct message stream id when writing as server Tomas Härdin 2025-02-05 14:22 ` [FFmpeg-devel] [PATCH 6/8] GOL-1361: Remove invalid CTTS sample_offset check Tomas Härdin 2025-02-12 11:11 ` Tomas Härdin 2025-02-05 14:23 ` [FFmpeg-devel] [PATCH 7/8] avformat/mp3dec: Subtract known padding from duration Tomas Härdin 2025-02-05 14:24 ` [FFmpeg-devel] [PATCH 8/8] Make mime-type award a bonus probe score Tomas Härdin 2025-02-06 14:58 ` Michael Niedermayer 2025-02-12 11:03 ` Tomas Härdin
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=8f2c6649b21ba3e412e45aa24277c22a439d7c07.camel@haerdin.se \ --to=git@haerdin.se \ --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