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

[Deanna Earley]

Thanks, I was trying to get something concrete by analysing the network stream.
This camera is unusual (compared to others we have) in that it sends an SPS and a PPS before every I frame.
The SPS/PPS share an RTP frame in a STAP with no marker bit, while the I/P frames are in FU-A packets (with the marker set on the last RTP frame).

I’ll post again when I get more information.

Thanks

--
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: 01 May 2015 18:17
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Multiple NALUs concatenated together in one afterGettingFrame

Our software uses liveMedia as an RTSP client to connect to network cameras to receive H.264 frames.
Our sink is being passed data from (presumably) the FramedSource class in response to data arriving from the camera/RTSP/H.264 video source and being depacketised.

OK, it sounds like your network camera might not be implementing the RTP payload format for H.264 video correctly - i.e., it might not be setting the RTP ‘M’ bit correctly, or perhaps it might be packing multiple NAL units into a single RTP packet in an incorrect way.  Because of this, our H.264/RTP reception code (“H264VideoRTPSource”) may be getting confused, and treating a sequence of incoming NAL units as if it were a single NAL unit.

Unfortunately you’re going to have to track this down yourself - e.g., by getting a packet trace of the offending incoming RTP packets from your camera.  Unfortunately, if your camera is buggy (implementing the H.264 RTP payload format incorrectly) then there’s not much we can do; you’d need to get your camera fixed.

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/20150505/55fa9cf3/attachment.html>