You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that too, and I always though it was because the system can't keep up. But now I al wondering if it's a rounding / conversion issue. I'll have a look as soon as possible.
There was, in fact, some rounding: it seems something along the encoding path drops the decimal part of the value in the video.field_rate field. I added a round() to the value I pass and made another change which should make the recording loop a bit faster.
The situation should be improved a bit. At least I get more or less consistently the same FPS I choose as target.
e.g. if the target frame rate is 24 FPS, then the output files wind up actually being 23 FPS.
I haven't checked if this is an encoding problem (i.e. it's recording 24 FPS but encoding as 23) or a capturing problem.
The text was updated successfully, but these errors were encountered: