From: "Jason A. Donenfeld via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: Daniel Verkamp <daniel@drv.nu>
Cc: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [FFmpeg-devel] Re: [PATCH] avformat/wavenc: use RF64 when needed
Date: Wed, 31 Dec 2025 13:53:07 +0100
Message-ID: <CAHmME9oLE+DPzqMMOqfA55g2G9uWBJcXMK1PWLVHJCVMWhH8hA@mail.gmail.com> (raw)
In-Reply-To: <CAGFXeQLiYz6+Jpcy7-L-FTghnRfZ=5=yGK20BO1EiZ8-Rb4V=w@mail.gmail.com>
Hi Daniel,
On Wed, Dec 31, 2025 at 8:43 AM Daniel Verkamp <daniel@drv.nu> wrote:
> The compatibility issue I mentioned is not related to the RIFF versus
> RF64 format change (which only triggers for large files, as you
> mentioned); it's that adding the extra reserved space for the
> potentially-needed RF64 header extension, which always happens in
> `-rf64 auto` mode even if the file ends up being a normal WAV and not
> RF64, causes the headers prior to the audio data to not be the exact
> 44-byte size expected by (buggy) software.
Ahh, thank you for the explanation. This also explains what Michael
found in his failed test.
> So in summary, I think switching to `-rf64 auto` by default is fine.
> It just needs a FATE reference update as Michael mentioned; `make
> fate-rsync` to get the samples and then `make fate GEN=1` should take
> care of most of the necessary updates.
Will do. Thanks for laying this out for me. v2 on its way.
Jason
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-12-31 12:54 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 [this message]
2026-01-02 23:27 ` Michael Niedermayer via ffmpeg-devel
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=CAHmME9oLE+DPzqMMOqfA55g2G9uWBJcXMK1PWLVHJCVMWhH8hA@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=Jason@zx2c4.com \
--cc=daniel@drv.nu \
/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