Ross,
It didn't take me days. I have solved my problem of synchronization
that was caused by wrong "presentation time" decoded by the library.
I have had to modify the library as explained in my email exchange.
> At the RTP receiver end, you get - for each frame of media
> data - a presentatio
age-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ross Finlayson
> Sent: Tuesday, February 05, 2008 1:32 PM
> To: LIVE555 Streaming Media - development & use
> Subject: Re: [Live-devel] Timestamp gap in RTCP Report for
> MPEG1or2VideoStreamFramer
>
>
You need to stop thinking about RTP timestamps. Instead, think about
presentation times.
At the RTP sender end, you provide - for each frame of media data - a
presentation time.
At the RTP receiver end, you get - for each frame of media data - a
presentation time. This presentation time is u
fTimestampBase: 0xae0daf0d, tv: 683382.201906, RTP timestamp: 21097
sending REPORT
fTimestampBase: 0xae0daf0d, tv: 683383.099932, RTP timestamp: 101919
Creating RTCP SR packet, SSRC is 0x6da5, NTP is : tv: 683383.099932,
TimeStamp is: 101919
sending RTCP packet
80c80006 6da5 83b4ebf7 1
fTimestampBase: 0xae0daf0d, tv: 683382.201906, RTP timestamp: 21097
sending REPORT
fTimestampBase: 0xae0daf0d, tv: 683383.099932, RTP timestamp: 101919
Creating RTCP SR packet, SSRC is 0x6da5, NTP is : tv: 683383.099932,
TimeStamp is: 101919
sending RTCP packet
80c80006 6da5 83b4ebf7 199524
I believe I might have ran into a design issue for the TimeStamp creation
when MPEG1or2VideoStreamFramer is used. Here what I have found.
I have checked the RTCP SR packets that are sent when I play a video Mpeg2
ES. I have used the sample application testMPEG1or2VideoStreamer. I have
followed th
