user12052: Is there a way for FFmpeg to output or log time duration since a particular job/process was started?
I know that there are more or less complicated ways to display a progress bar which really seems more like a programmatical problem.
The reasoning is that I want to measure how long time my encoding jobs take (without having to set up a separate timer).

user1871: If you use the -report option, ffmpeg will create a logfile at initialization and the filename will contain the time at which it was created. You can use the last modified time of the log file to get the completion time, and thus the duration. On Windows, you could just check the creation time of the output as well.
Addendum: A rough way to get this information, universally, without altering the command or using a monitoring tool like time, as LN guided, is to note the encoding speed normally reported i.e. speed=5.50x. So, if the duration of the output file is 110 seconds, then time taken to encode is 110 / 5.5 = 20 seconds. 

user27308: Use -benchmark.
You will see something like bench: utime=11.969s stime=0.315s rtime=1.908s, the rtime is what you want.

user1760: In Linux you can use the time command:
$ time ffmpeg -i input.avi output.mp4
  [...]
  real  0m1.927s
  user  0m7.067s
  sys   0m0.243s

This example took 1.927 seconds to complete.

12052: <p>Is there a way for <code>FFmpeg</code> to output or log time duration since a particular job/process was started?</p>

<p>I know that there are more or less complicated ways to display a <a href="https://stackoverflow.com/questions/747982/can-ffmpeg-show-a-progress-bar">progress bar</a> which really seems more like a programmatical problem.</p>

<p>The reasoning is that I want to measure how long time my encoding jobs take (without having to set up a separate timer).</p>
 1871: <p>If you use the <code>-report</code> option, ffmpeg will create a logfile at initialization and the filename will contain the time at which it was created. You can use the last modified time of the log file to get the completion time, and thus the duration. On Windows, you could just check the creation time of the output as well.</p>

<p><strong>Addendum</strong>: A rough way to get this information, universally, without altering the command or using a monitoring tool like <code>time</code>, as LN guided, is to note the encoding speed normally reported i.e. <code>speed=5.50x</code>. So, if the duration of the output file is 110 seconds, then time taken to encode is <strong>110 / 5.5 = 20 seconds</strong>. </p>
 27308: <p>Use <code>-benchmark</code>.
You will see something like <code>bench: utime=11.969s stime=0.315s rtime=1.908s</code>, the <code>rtime</code> is what you want.</p>
 1760: <p>In Linux you can use the <code>time</code> command:</p>

<pre><code>$ time ffmpeg -i input.avi output.mp4
  [...]
  real  0m1.927s
  user  0m7.067s
  sys   0m0.243s
</code></pre>

<p>This example took 1.927 seconds to complete.</p>
