[Libav-user] RTSP SDP Parsing Error
mark.kenna at sureviewsystems.com
Wed Mar 4 14:44:59 CET 2015
On 27 February 2015 at 19:38, Andy Shaules <bowljoman at gmail.com> wrote:
> On 2/27/2015 9:09 AM, Mark Kenna wrote:
> On 13 February 2015 at 12:07, Mark Kenna <mark.kenna at sureviewsystems.com>
>> I think there is a problem in the SDP parsing of RTSP.c. I have an SDP
>> which has 2 tracks, one is H264 and the other is MJPEG. It appears that
>> FFMPEG is always opening MJPEG regardless of which codec is specified first
>> in the track list. Here is an example:
>> o=- 130683027881870000 130683027881870000 IN IP4 126.96.36.199
>> c=IN IP4 0.0.0.0
>> t=0 0
>> m=video 1036 RTP/AVP 96 26
>> a=rtpmap:96 H264/90000
>> a=fmtp:96 packetization-mode=1; profile-level-id=420029;
>> a=rtpmap:26 JPEG/90000
> Hi Guys
> Did anyone see this issue? I was wondering if anyone has suffered the
> same problem?
> Libav-user mailing listLibav-user at ffmpeg.orghttp://ffmpeg.org/mailman/listinfo/libav-user
> It appears the SDP is wrong. I believe there should be two m entries.
> m=video 1036 RTP/AVP 96
> a=rtpmap:96 H264/90000
> a=fmtp:96 packetization-mode=1; profile-level-id=420029;
> m=video 1036 RTP/AVP 26
> a=rtpmap:26 JPEG/90000
> Libav-user mailing list
> Libav-user at ffmpeg.org
According to the SDP specification you are allowed to have multiple media
values in the same m line. If you have information to the contrary then
please let me know.
Appreciate the information!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libav-user