[Live-devel] RTP Timestamps

[Eric Flickner]

I am sure that the stream is an MPEG-4 ES via RTP.  The manufacturer usually
had a closed system, where they didn't test with other RTP clients for
problems.  They only checked the marker bit for the end of a frame and
ensured that there were no sequence gaps/errors when reassembling frames.  I
am aware that this stream should be using payload type 96 with increasing
timestamps.  How reliable can I expect this algorithm to be for packet
reassembly? 

Thanks,

Eric Flickner

-----Original Message-----
From: live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Friday, March 28, 2008 5:46 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTP Timestamps

>1.  Is it standards compliant for an RTP stream to contain all of 
>the same timestamp information for each RTP packet?

No, because the timestamp represents the presentation time of each 
enclosed frame.

>2.  All of my packets have a payload type 88.  Is there a specific 
>RFC that specifies the payload for this format?

No.

Are you *sure* that your stream is RTP?
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel