This is no longer reproducible. The output files are now byte-for-byte the same size, and from_ape.wav has the size the reporter expected (5292078 = 78-byte WAV header + 44100*2*2*30 = 5292000 bytes of PCM). Tested with the exact command line from the ticket, using a freshly encoded file (Monkey's Audio mac 12.97): $ ffmpeg -y -t 60 -f s16le -i /dev/urandom -ar 44100 -acodec pcm_s16le -ac 2 in.wav$ mac in.wav in.ape -c2000$ ffmpeg -y -accurate_seek -ss 5 -t 30 -i in.wav -f wav from_wav.wav$ ffmpeg -y -accurate_seek -ss 5 -t 30 -i in.ape -f wav from_ape.wav$ ls -l from_wav.wav from_ape.wav-rw-rw-r-- 1 user user 5292078 from_ape.wav-rw-rw-r-- 1 user user 5292078 from_wav.wav
Confirmed on two builds: * git master N-124666-gaf86ff142a (libavcodec 62.34.102) * release 7.1.4 (libavcodec 61.19.101) The 4-byte discrepancy is gone in both, so the issue appears to have been fixed at some point since 2017 (most likely as part of the later seek/accurate-seek/discard reworks rather than any APE-specific change). Please close as fixed/outdated.Let me know if you require any additional information from me. Regards from Sweden, Mihaly. _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
