Hi,
(sorry for the delay... I'm currently quite busy)
Stas Oskin wrote:
>> Mind checking my formula? :)
>>
>> PTS_delta = av_rescale_q(timestamps_delta, AV_TIME_BASE_Q, time_base);
If your timestamps are in milliseconds, I guess AV_TIME_BASE_Q is wrong
(try something like {1, 1000}).
>> Just one question here - the used timebase value is from stream
>> structure. The den member is always equal to 90,000, no mater what FPS
>> I set for the codec time base den memeber. Does it mean it's unrelated
>> to codec timebase, hence the approach work safely on every possible
>> frame rate? Or I misunderstand it's purpose.
If we are talking about the RTP TS (the PTS value that must be set in
AVPacket before calling av_write_frame()), then 1/90000 is the correct
time base for almost all the video payloads (for audio, the time base is
1/90000 in case of mp2/mp3, or 1/<frame rate> in case of other audio codecs).
> Well, I tried this approach, and have now huge pixel trails for every
> movement on screen, which gets cleared every so often (probably by
> intra-frame). What is the reason behind these trails?
Maybe some frames are lost/corrupt because of the wrong PTS values
computed above?
Luca
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
