From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/3] avformat/matroska: Support JPEG2000 for demuxing
Date: Sun, 25 May 2025 12:53:42 -1000
Message-ID: <20250525125342.0000613a@hawaiiantel.net> (raw)
In-Reply-To: <GV1P250MB0737B6A8825F19A31B24AD548F9AA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
On Sun, 25 May 2025 05:50:54 +0200, Andreas Rheinhardt wrote:
> Patches attached.
>
> - Andreas
looks ok but i wonder if anyone is using the vfw ffv1 mkv in the
archiving universe on purpose. should we include a way to -vfw-codec-id
manual for those systems? maybe is unimportant but it would be good to
ask the ffv1 specification crowd about this change to mkv muxing. and
maybe resend patch separately from jpeg2000 decoding subject. hiding an
ffv1 change under jpeg2000 subj is weird.
said another another way, this change would change the checksums of
files if people tried to recreate their mkv. which is something that
archivists do sometimes.
e.g. old ffv1 mkv vfw codec_id
vs
new ffv1 mkv codec_id
-compn
_______________________________________________
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-05-25 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 3:50 Andreas Rheinhardt
2025-05-25 22:53 ` compn [this message]
2025-05-25 23:50 ` Andreas Rheinhardt
2025-05-27 14:06 ` Dave Rice
2025-05-27 23:09 ` compn
2025-05-28 0:33 ` Andreas Rheinhardt
2025-05-27 11:50 ` Andreas Rheinhardt
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=20250525125342.0000613a@hawaiiantel.net \
--to=ff@hawaiiantel.net \
--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