[Live-devel] H264 SDP

soumya patra soumya.patra at lge.com
Thu Jul 10 22:17:20 PDT 2008


Hi,

 

I have implemented the H264VideoStreamer subclass and am able to
successfully unicast stream to a single VLC client. For this I had modified
the live sdp generation code to exclude the fmtp:... line from the returned
describe response for H264. In this case I am able to play the streamed
content using MPlayer or VLC client.

 

If I pass the profile level id "profile_level_id" and 

"sprop_parameter_sets_str" parameters to 

"H264VideoRTPSink::createNew()" as suggested and ensure that the sdp
returned contains the correct 

fmtp: line -"a=fmtp:97
packetization-mode=1;profile-level-id=000042;sprop-parameter-sets=Z0Ligqwewo
3FkkBaHsuG,aMOOOOKCrA=="

 

then my vlc client is not able to play the stream.(I am also unable to play
using MPlayer)

 

I have extracted the profile level id and sps and pps and using h264analyzer
tool.

Also I have base64 encoded the sps and pps as stated in the rfc-3984.

 

I suspect that the vlc client is able to play the h264 stream when it
extracts the decoder parameters from the rtp stream itself (in band; we are
transmitting NAL units 7 and 8 (sps and pps) also over RTP). But if we try
to provide the profile id and sprop_parameters over sdp (while also
streaming the NAL packets 7 and 8 over rtp as before) then even a single
requesting client is unable to play the stream. Maybe the presence of the
fmtp: line stops the client from looking for this information within the
stream. But the fmtp: line provided by us is not intelligible enough to the
client to successfully play the stream.

 

As our actual requirement is to unicast stream to multiple clients
(reuseFirstSource is set to True) and also stream multicast we need to
communicate using the sdp, the in band mechanism is not sufficient and also
not reliable.

 

I have attached our sdp and NAL frame (contains NAL units 7 and 8) alongwith
the mail. We may be missing some needed information in sdp or we might be
communicating it in the wrong format or I might be totally mistaken:-).
Could you tell us the correct sdp fmtp line to generate or any pointers to
missing or incorrect information in our sdp?

      I have attached ethereal extracted sdp description and NAL packet
extracted from h264 analyzer.Please check the attached text file.

Regards

Soumya

LGSI

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20080711/d6a2269d/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sdph264.txt
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20080711/d6a2269d/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: NAL packet.txt
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20080711/d6a2269d/attachment-0001.txt>


More information about the live-devel mailing list