Re: [Nokia-private-dev] RTP timestamp issue when streamming from vidiator server(Live streaming)
Milko Boic <[email protected]>
| Newsgroups | gmane.comp.multimedia.helix.devel,gmane.spam.detected |
|---|---|
| Message-ID | <[email protected]> |
At 01:22 PM 5/20/2008, [email protected] wrote: >Content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C8BAB7.3D5EE1DA" > >Hi, > >There is a live vidiator server streaming link and upon trying to stream >from this link helix client receives few audio stream RTP packets with >timestamp less than the RTPOffset time initially. It causes helix time >calculation failure. What is the failure? >Here is the RTP PLAY command and PLAY response from vidiator server. > >PLAY dynstream RTSP/1.0 >CSeq: 7 >User-Agent: RealMedia Player HelixDNAClient/10.0.0.6839 (S60 HX >cvs_cays221_20080327:05:00:00utc 27 Mar 2008 21:00) >Session: C03A5301C621C22D >Range: npt=0- >Bandwidth: 1432572 > >RTSP/1.0 200 OK >CSeq: 7 >Date: Tue, 15 Apr 2008 16:34:11 GMT >Session: C03A5301C621C22D >Range: npt=now- >RTP-Info: url=rtsp://10.63.48.228/dynstream/2;seq=1;rtptime=180000, >url=rtsp://10.63.48.228/dynstream/1;seq=1;rtptime=180000 > >Server: Vidiator Server/3.3 > >Sample RTP Audio Packet timestamp sequence > >SEQ: 1, Timestamp: 164000* >SEQ: 2, Timestamp: 166560* >SEQ: 3, Timestamp: 169120* >SEQ: 4, Timestamp: 171680* >SEQ: 5, Timestamp: 174240* >SEQ: 6, Timestamp: 176800* >SEQ: 7, Timestamp: 179360* >SEQ: 8, Timestamp: 181920 >SEQ: 9, Timestamp: 184480 >SEQ: 10, Timestamp: 187040 >SEQ: 11, Timestamp: 189600 >SEQ: 12, Timestamp: 192160 > >Sample RTP Video Packet timestamp sequence >SEQ: 1, Timestamp: 180000 >SEQ: 2, Timestamp: 187200 >SEQ: 3, Timestamp: 194400 >SEQ: 4, Timestamp: 201600 >SEQ: 5, Timestamp: 208800 >SEQ: 6, Timestamp: 216000 >SEQ: 7, Timestamp: 223200 >SEQ: 8, Timestamp: 226800 >SEQ: 9, Timestamp: 234000 >SEQ: 10, Timestamp: 241200 >SEQ: 11, Timestamp: 244800 >SEQ: 12, Timestamp: 252000 > >We could fix this error in couple of ways as given below. > >1) Drop RTP packet(s) with timestamp < RTP offset time >2) If the first RTP packet timestamp is less than the received RTP offset >time correct RTP offset time to first RTP packet time. > >Looking for input/suggestion from community to make a fix to this failure. > >Thanks >Saleem >_______________________________________________ >Nokia-private-dev mailing list >[email protected] >http://lists.helixcommunity.org/mailman/listinfo/nokia-private-dev _______________________________________________ Helix-client-dev mailing list [email protected] http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev