The timestamp is actually embedded in the MPEG-4 header and represents the historic time the frame was captured.
It sounds like I shouldn't get too tricky with the RTSP/RTP/RTCP return/response commands. Thank you, Chris ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ross Finlayson Sent: Monday, November 05, 2007 7:21 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Create and Handle Custom RTSP Response The remaining piece of the puzzle for me deals with a web client that I have written that provides interaction with the live stream. I am trying to get a timestamp back from the media server to the client, and ultimately available to a Javascript function on the page. I can formulate a RTSP request from the client in the form of a URL that triggers an internal method in the media server which provides the current timestamp. How can I get this time stamp back to the client? What exactly is this "timestamp" supposed to be? You realize, I hope, that every RTP packet sent by the server (and received by the client) already has a timestamp, which gets mapped to an accurate "presentation time" that the client software (e.g., VLC) sees. I'm working on trying to "send" back a response w/ the timestamp via the RTSP session If you're trying to do something that's outside the RTSP/RTP/RTCP standard, then this probably isn't a good idea. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel