[Live-devel] Multiple NALUs concatenated together in one afterGettingFrame

[Deanna Earley]

Thank you for confirming those.
I’ll do a follow-up as soon as we have packet capture.

Kind regards

--
Deanna Earley | Lead developer | icatchercctv

w: www.icode.co.uk/icatcher<http://www.icode.co.uk/icatcher> | t: 01329 835335 | f: 01329 835338
Registered Office : 71 The Hundred, Romsey, SO51 8BZ. Company Number : 03428325

From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: 08 May 2015 08:48
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Multiple NALUs concatenated together in one afterGettingFrame

Is there a way we, as the RTSPClient caller, can determine when RTP frames have been lost

Yes, look at “RTPReceptionStats”.  Note (in “testProgs/playCommon.cpp”) how the “openRTSP” client implements the “-Q” (report QOS stats) option:
          http://live555.com/openRTSP/#other-options



As our original problem was multiple frames concatenated together in one “frame”, do you agree that a dropped RTP frame *couldn’t* cause that issue too (given the packet structure I described earlier)?

Yes (though I’d say “shouldn’t” rather than “couldn’t”).  I’m not ruling out the possibility of a bug in our code that might be causing this (though I’d need to see a packet trace to be sure).

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20150508/9bd3574f/attachment.html>