[FFmpeg-devel] How ffplay resolves bad timestamps?

[Martin Storsjö]

On Wed, 22 Dec 2010, Stas Oskin wrote:

> I've got some unfinished code for emitting timestamps from the beginning,
> > if the server sends the start RTP timestamp with a RTP-Info header in
> > response to the PLAY request. Do your servers send RTP-Info headers?
> >
> >
> Yes, for example:
> 
> PLAY rtsp://192.168.253.153/ch0_unicast_firststream/ RTSP/1.0
> Range: npt=0.000-
> CSeq: 4
> Session: 52
> 
> RTSP/1.0 200 OK
> CSeq: 4
> Date: Wed, Dec 22 2010 10:32:24 GMT
> Range: npt=0.000-
> Session: 52
> RTP-Info: url=rtsp://
> 192.168.253.153/ch0_unicast_firststream/track1;seq=56954;rtptime=372642415

Ok, that's good to hear. On the other hand, for streams without RTP-Info, 
I guess one can use the timestamp/sequence number of the first packet of 
each stream to avoid having too many codepaths/special cases.

> if you provide me with the patch, I will be happy to test it.

Sorry, it's from March this year, and probably doesn't apply too well on 
todays SVN. I'll let you know when I get round to polishing it up.

// Martin