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 <[email protected]> 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
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
