From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/3] avformat/matroska: Support JPEG2000 for demuxing
Date: Tue, 27 May 2025 13:09:37 -1000
Message-ID: <20250527130937.00004dfa@hawaiiantel.net> (raw)
In-Reply-To: <GV1P250MB0737255E8BC47162604C7A248F9AA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
On Mon, 26 May 2025 01:50:42 +0200, Andreas Rheinhardt wrote:
> Why should the FFV1 specification crowd object to us writing FFV1 files
> in the way they have been intended to be written since February 2017
> (since
> https://github.com/ietf-wg-cellar/matroska-specification/commit/51a600106bfa66f58a7f2c8e05fab091ab059ebd)?
> Anyway, I cc'ed Dave Rice, the author of the aforementioned commit.
thanks for cc'ing dave, waiting for dave's response, and thanks to dave
for the quick reply, review and OK.
i know ffv1 users are all about bitexact-ness, and i didnt know when
Dave's timers were ready for this change either.
thanks everyone. and i hope that you dont think i'm trying to slow down
or block any changes to default ffmpeg improvements. i just wanted to be
inclusive of ffv1 users opinions, and now we're set! :)
maybe i'd change commit message from
avformat/matroskaenc: Use native id instead of VfW for FFV1
to
avformat/matroskaenc: Use native id V_FFV1 instead of V_MS/VFW/FOURCC/FFV1
if you think its appropriate anyway.
-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-27 23:09 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
2025-05-25 23:50 ` Andreas Rheinhardt
2025-05-27 14:06 ` Dave Rice
2025-05-27 23:09 ` compn [this message]
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=20250527130937.00004dfa@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