[Libav-user] SDP Parsing
Mark Kenna
mark.kenna at sureviewsystems.com
Thu Oct 18 17:43:18 CEST 2012
Could someone tell me if this SDP looks correct? I was under the impression
that you couldn't have more than one a=rtpmap within a m= media tag?
Note that I've taken the capture through WireShark and omitted the top parts
Session Description Protocol
......
......
Media Description, name and address (m): video 0 RTP/AVP 26 96
Media Attribute (a): rtpmap:26 JPEG/90000
Media Title (i): video stream 1 in camera 1
Media Attribute (a): control:rtsp://74.112.34.42:554/media/1/video/1
Media Attribute (a): x-bufferdelay:0.050000
Media Attribute (a): mimetype:string;"video/JPEG"
Media Attribute (a): rtpmap:96 H264/90000
Media Attribute (a): fmtp:96 packetization-mode=1;
profile-level-id=420029;
config=0000000167420029e2900800c3602dc0404069078911500000000168ce3c80;
sprop-parameter-sets=Z0IAKeKQCADDYC3AQEBpB4kRUA==,aM48gA==;
Media Title (i): video stream 1 in camera 1
Media Attribute (a): control:rtsp://74.112.34.42:554/media/1/video/1
Media Attribute (a): x-bufferdelay:0.050000
Media Attribute (a): mimetype:string;"video/H264"
It looks as if this SDK is trying to say that the media track could be
MJPEG or h264. FFmpeg is reading the codec as MJPEG and then failing when
the media data delivered is actually h264. I just need to know if this is a
valid SDP and whether there could be a bug in FFMpeg.
Thanks,
Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20121018/b5b9244c/attachment.html>
More information about the Libav-user
mailing list