2018-06-22 21:53 GMT+02:00, Ronak <ronak2121-at-yahoo....@ffmpeg.org>: > > >> On Jun 20, 2018, at 4:48 PM, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: >> >> 2018-06-20 18:37 GMT+02:00, Ronak <ronak2121-at-yahoo....@ffmpeg.org>: >> >>> That command took the following time: >>> >>> real 3m19.316s >>> user 3m14.730s >>> sys 0m1.830s >>> >>> I'm curious about your thoughts on this. With -codec copy, the decoder >>> should not be involved, so it shouldn't be a bottleneck. >> >> Yes. >> >>> I'm wondering if the extra file I/O is the culprit here? >> >> Yes. >> >> You can now specify "-loglevel verbose" to get some useful >> I/O info at the end of the console output.
> [AVIOContext @ 0x23b9140] Statistics: 0 seeks, 15 writeouts > [AVIOContext @ 0x2310e80] Statistics: 0 seeks, 2107 writeouts > [AVIOContext @ 0x22c72c0] Statistics: 541488832 bytes read, 2 seeks This indicates that nothing absurd with regard to seeking happens. Try with different drives for input and output to make sure we know the culprit. Carl Eugen _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
