Daniel G. Taylor <[email protected]> added the comment: This is still an issue in latest trunk, but I have found a workaround by specifying an explicit output framerate for the yuv4mpegpipe, e.g.:
ffmpeg -i yuv4mpegpipe_incorrect_framerate.wmv -f yuv4mpegpipe -r 25 - | ffmpeg -i - working.avi This means you need to either set a single framerate for all inputs or somehow figure out the framerate of the input yourself before running the command. _____________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue1001> _____________________________________________________
