Hi,
Stas Oskin wrote:
> Hi.
>
> Following my periodic :) check of possible solutions, I managed to dig out a
> quite dated solution from the very own FFMPEG developers thread:
> http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2005-October/004638.html
I had a look at it. As I previously said, I never used variable frame rate;
however, I think the email you quote is saying the same things that have been
repeated here in the past.
> The situation described there is very similar to my own, namely a network
> source (camera in his case) which sends frames with rate that varies from 1
> to 10.
>
> The purposed solution (which I hope I understood correctly) was to:
>
> a) Use very small value for timebase, such as 1/2520, or even microseconds
> (1/1000000?).
You have to set your time base so that all the timestamps can be multiple
of the time base. This (as far as I understand) is what Rich is also saying
in the email you quote. So, where are your timestamps coming from? In which
time unit are they expressed? Just set the time base to this time unit, and
you are done...
> b) Use same value both for format and codec timebases.
I am not sure about this.
> c) Timestamp the frames according to source frames.
What Rich says in that email is "you need to set the pts values correctly
for each frame you write". Whis is the same thing that has been told in
this mailing list :)
Assuming that there is no bug in libav* and you ara using a codec/format
which supports variable frame rate, if you use the input timestamps and
the result does not play well, this might mean that your input timestamps
are wrong.
If I remember well, you are using some strange SDK for the input, which
associates questionable timestamps to the frames...
Luca
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
