[Live-devel] testRTSPClient / H.264 Network Camera Stream

[Ross Finlayson]

>     Reading further on your site I see that you may need the SDP description
> from my camera stream.
[...]
> v=0
> o=- 1365522147122142 1 IN IP4 192.168.1.2
> s=IP Camera Video
> i=videoMain
> t=0 0
> a=tool:LIVE555 Streaming Media v2013.01.25
> a=type:broadcast
> a=control:*
> a=range:npt=0-
> a=x-qt-text-nam:IP Camera Video
> a=x-qt-text-inf:videoMain
> m=video 0 RTP/AVP 96
> c=IN IP4 0.0.0.0
> b=AS:96
> a=rtpmap:96 H264/90000
> a=control:track1
> m=audio 0 RTP/AVP 0
> c=IN IP4 0.0.0.0
> b=AS:64
> a=control:track2

OK, the bug here is in your server - i.e., the camera; not the client.  The camera (server) isn't including a "sprop-parameter-strings" parameter (in a "a=fmtp:96..." line) in the SDP description.

Fortunately, however, I see that the camera (server) is also implemented using our software, so it should be easy to fix.  Please tell whoever developed your camera to:
	(1) Upgrade to the latest version of the "LIVE555 Streaming Media" software, and
	(2) Either insert "SPS" and "PPS" NAL units at the start of the H.264 Video stream (that it feeds into the "H264VideoRTPSink" object, or else change the way that the "H264VideoRTPSink" object is created - to use one of the forms of the "H264VideoRTPSink::createNew()" function that take "SPS"/"PPS" NAL unit information as a parameter (either as raw binary NAL units, or a "sPropParameterSetsStr" string).

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/20130409/fa67524a/attachment.html>