[Libav-user] FPS incorrect (regression) with new codecpar api

[Gonzalo]

El 24/06/16 a las 12:29, Gonzalo escribió:
>
> Compiled from HEAD.  muxing example (only one that has been updated to 
> new api) compiles and runs fine, but ffprobe returns the following for 
> the resulting movie:
>
> Duration: 00:00:10.03, start: 0.000000, bitrate: 289 kb/s
>     Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 
> 352x288, 220 kb/s, 25.10 fps, 25 tbr, 12800 tbn, 50 tbc (default)
>
> Notice it says 25.10 fps instead of just 25 fps as set in the code.
>
> I am seeing the same behavior on my code, with fps that are 25.1603 
> for example.
>
Ping.  Anybody seeing this behavior on the docs/examples/muxing.c sample?

-- 
Gonzalo Garramuño
ggarra13 at gmail.com