From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [PATCH] avformat/wavenc: use RF64 when needed
Date: Sat, 3 Jan 2026 00:27:17 +0100
Message-ID: <aVhUVXcHnHJ2kUt1@neo> (raw)
In-Reply-To: <CAGFXeQLiYz6+Jpcy7-L-FTghnRfZ=5=yGK20BO1EiZ8-Rb4V=w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1376 bytes --]
Hi Daniel
On Tue, Dec 30, 2025 at 11:43:17PM -0800, Daniel Verkamp via ffmpeg-devel wrote:
> On Tue, Dec 30, 2025 at 3:17 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
[...]
> That said, I think it's fair to say that switching to `-rf64 auto` by
> default won't cause further compatibility problems due to breaking the
> 44-byte header assumption, because current ffmpeg already doesn't
> generate such files (although it did at some point in the distant
> past). WAV files generated by the ffmpeg CLI now have a "ISFT" chunk
> containing the libavformat version, so the header won't be the magic
> 44-byte size regardless of whether the extra reserved-for-ds64 padding
> is added. In other words, any supposed compatibility improvements we'd
> get by trying to stick with the expected "classic" layout were already
> lost when the encoder metadata was added; I should have peeked in a
> hex editor rather than relying on my recollection. :)
Someone should add a classic44_wav mode.
So we cab generate files for these ancient devices that expect that
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Arguing that you don’t care about the right to privacy because you have
nothing to hide is no different than saying you don’t care about free speech
because you have nothing to say - Edward Snowden
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2026-01-02 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 21:28 [FFmpeg-devel] " Jason A. Donenfeld via ffmpeg-devel
2025-12-21 3:08 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-12-30 4:50 ` Daniel Verkamp via ffmpeg-devel
2025-12-30 11:17 ` Jason A. Donenfeld via ffmpeg-devel
2025-12-31 7:43 ` Daniel Verkamp via ffmpeg-devel
2025-12-31 12:53 ` Jason A. Donenfeld via ffmpeg-devel
2026-01-02 23:27 ` Michael Niedermayer via ffmpeg-devel [this message]
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=aVhUVXcHnHJ2kUt1@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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