[Ffmpeg-devel] rtsp problem with ffplay

chris.2.dobbs at bt.com chris.2.dobbs
Wed Mar 8 13:35:22 CET 2006

Many thanks for your reply Luca.
I have not heard of libnms/nemesi ...is it part of the ffmpeg src tree?
BTW - I see what is going on with payload type 96 now, I suppose just to
test I could 'hard-code' the sdp_parser to pick up AMR NB codec info for
payload type 96....yuk I know but I am really interested to know if
ffplay can actually deal with AMR NB over rtsp

-----Original Message-----
From: ffmpeg-devel-bounces at mplayerhq.hu
[mailto:ffmpeg-devel-bounces at mplayerhq.hu] On Behalf Of Luca Barbato
Sent: 07 March 2006 19:30
To: FFMpeg development discussions and patches
Subject: Re: [Ffmpeg-devel] rtsp problem with ffplay

chris.2.dobbs at bt.com wrote:
> Slight update to this after some more poking around....
> I notice that in rtp.c the /AVFormatContext/ structure looks to be 
> something that holds all he recognised codec types for audio and video

> ove rtp...I notice there is none for AMR NB. My payload type seems to 
> come thru ok as 96 (which is correct for AMR NB) so am I correct in 
> thinking that I just need to add a line for this payload type to 
> reflect AMR NB codec?

no, payload number is dynamic you have to parse the sdp and set the
context accordingly.

check libnms/nemesi on how to do it.



Luca Barbato

Gentoo/linux Gentoo/PPC

ffmpeg-devel mailing list
ffmpeg-devel at mplayerhq.hu

More information about the ffmpeg-devel mailing list