Thanks for your response. There are a couple of reasons why we would like to do this. Firstly we will be streaming from a lot sources and for every one we will have to provide a large buffer to Live555 to capture the frame even though most frames will be small. We would like to know in advance how big a buffer we need so that we can minimise memory usage. By getting lots of smaller packets and putting them together afterwards we should be able to do this. Also, we would like to find out which frames are key frames so we will try to get that by passing the packets to ffmpeg which should construct the frame and tell us whether its a key frame.
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: 04 March 2015 16:43 To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] RTP header information I have been trying to work out how I can get Live555 to provide me with the RTP packet header data as well as the payload but have had no luck. I did look at using a SimpleRTPSource but that seems to strip off the RTP header as well. Our code doesn’t just ‘strip off’ the RTP header - it *processes* the RTP header. I.e., the whole purpose of the “LIVE555 Streaming Media” code’s RTP handling is that you - the developer - don’t have to concern yourself with RTP headers (including sequence numbers, RTP timestamps, fragmentation over multiple RTP packets or possibly multiple frames per RTP packets, etc.). Why do you think you want to see the RTP header? If you *really* want to - for whatever reason - see the RTP header, you could use a “BasicUDPSource” rather than a “RTPSource” subclass. You’d be on your own from that point, though. Ross Finlayson Live Networks, Inc. http://www.live555.com/ This company is part of the G4S group of companies. This communication contains information which may be confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. Any personal views expressed in this e-mail are those of the individual sender and the Company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity. This message has been checked for viruses on behalf of the Company. ________________________________ The details of this company are as follows: G4S Technology Limited, Registered Office: Challenge House, International Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338. This communication may contain information which is confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity. This e-mail has been scanned for all viruses by MessageLabs.
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
