Alexandre Ferrieux <[email protected]> added the comment:
Why ? The evidence is perfectly consistent with the analysis. I even updated the title to better describe the situation. The problem is restricted to wav output on "-", but is not dependent on pipe vs. regular file. Here are further details on the source: there's simply no call to put_flush_packet at the end, because that occurs normally inside wav_write_trailer, but conditionally on (!url_is_streamed). So the fix is to add some kind of flush in the "else" of this condition. (I'm not providing a patch because I don't know the exact "flush" to use when no packet is being put) ---------- status: closed -> open substatus: invalid -> analyzed title: FFmpeg truncates and pads audio -> FFmpeg truncates and pads wav when output is "-" ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue498> ________________________________________________
