> > [...] > >> 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... > >> > > > > Actually, these were bugs in my code :). I'm currently using the SDK > > timestamps deltas for live RTP streaming, and this works just fine. > > Why deltas? I think you should use the timestamps directly... > <https://lists.mplayerhq.hu/mailman/listinfo/libav-user> >
I meant that I use the difference between timestamps coming from the SDK, and the first time-stamp (which PTS is 0). For example: 1 frame - 123456789 s, 100 ms 2 frame - 123456789 s, 300 ms 3 frame - 123456789 s, 800 ms This means that: 1 new frame pts = 0 2 new frame pts = 200 3 new frame pts = 700 And so on. I think that using SDK timestamps directly would do same thing, but it won't start from zero, thus will lead to some issues (I remember I had some really weird effects with this one in RTP, but not sure). What do you think? P.S.: I will upload a movie soon. _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
