[MPlayer-dev-eng] [PATCH] MEncoder: print more precise FPS

Jindrich Makovicka makovick at kmlinux.fjfi.cvut.cz
Thu Nov 17 18:02:14 CET 2005


Guillaume Poirier wrote:
> Hi,
> 
> Jindrich Makovicka wrote:
> 
>>Oded Shimon wrote:
>>[...]
>>
>>
>>>>    } else
>>>>-    mp_msg(MSGT_AVSYNC,MSGL_STATUS,"Pos:%6.1fs %6df (%2d%%) %3dfps
>>>>Trem:%4dmin %3dmb  A-V:%5.3f [%d:%d]\r",
>>>>+    mp_msg(MSGT_AVSYNC,MSGL_STATUS,"Pos:%6.1fs %6df (%2d%%) %5.3ffps
>>>>Trem:%4dmin %3dmb  A-V:%5.3f [%d:%d]\r",
>>>>        mux_v->timer, decoded_frameno, (int)(p*100),
>>>>-        (t>1) ? (int)(decoded_frameno/t+0.5) : 0,
>>>>+        (t>1) ? (float)(decoded_frameno/t+0.5) : 0,
>>>
>>>
>>>
>>>no +0.5, that as only there for integer rounding.
>>
>>
>>there is also progressive NTSC with 23.976 fps, so 6.3 would be more
>>appropriate.
> 
> 
> I'm afraid I don't follow you here. 

Definitely. Sorry for the noise.

> the type of source or output doesn't
> matter here. It's just the encoding speed that's printed.
> 
> Please be more explicit about the problem you see, I don't see any
> problem here, but I may be wrong.

Actually, it can display the real fps when capturing from live sources 
(that's why I once added the +0.5 rounding to make the display less 
confusing), but two decimal places are surely enough.

-- 
Jindrich Makovicka




More information about the MPlayer-dev-eng mailing list