On Fri, Dec 11, 2015 at 04:49:14PM +0100, Moritz Barsnick wrote:
> This adds a computation of the progress speed versus realtime ("Nx")
> to the status line and to the report log. It uses the progress time
> as already calculated for total output time as a base.
> ---
> ffmpeg.c | 15 +
On Wed, Dec 16, 2015 at 15:28:31 +0100, Nicolas George wrote:
> > BTW, these two are used quite often in this function and sort of beg
> > for macros, but I don't go around macro-ifying code just for the fun of
> > it. ;-)
>
> No need for macros, there is the av_bprint() API for that.
*shrug* OT
Le sextidi 26 frimaire, an CCXXIV, Moritz Barsnick a écrit :
> BTW, these two are used quite often in this function and sort of beg
> for macros, but I don't go around macro-ifying code just for the fun of
> it. ;-)
No need for macros, there is the av_bprint() API for that.
Regards,
--
Nicola
On Fri, Dec 11, 2015 at 16:49:14 +0100, Moritz Barsnick wrote:
> This adds a computation of the progress speed versus realtime ("Nx")
> to the status line and to the report log. It uses the progress time
> as already calculated for total output time as a base.
> ---
> ffmpeg.c | 15 ++-
ffmpeg.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
While this is still not a benchmark, the display of a factor "Nx" gives a
much better and easier to parse feeling for the processing speed than
looking at "fps", at the processed file time, or applying the Unix "time"
This adds a computation of the progress speed versus realtime ("Nx")
to the status line and to the report log. It uses the progress time
as already calculated for total output time as a base.
---
ffmpeg.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/ffmpeg.c
