Commit 241fb0c4 authored by Luca Barbato's avatar Luca Barbato

RTP clarifications

Originally committed as revision 9722 to svn://svn.ffmpeg.org/ffmpeg/trunk
parent 0509d453
...@@ -406,10 +406,8 @@ The standard MSys bash (2.04) is broken. You need to install 2.05 or later. ...@@ -406,10 +406,8 @@ The standard MSys bash (2.04) is broken. You need to install 2.05 or later.
@section I tried to pass RTP packets into a decoder, but it doesn't work. @section I tried to pass RTP packets into a decoder, but it doesn't work.
Of course not, you MUST strip ALL RTP headers and assemble valid packets RTP is a container format like any other, you must first depacketize the
first, an MP3 decoder decodes MP3 packets not bastardized MP3 packets codec frames/samples stored in RTP and then feed to the decoder.
encapsulated in RTP. The same applies to all decoders, this is not specific
to ffmpeg or libavcodec.
@section Where can I find libav* headers for Pascal/Delphi? @section Where can I find libav* headers for Pascal/Delphi?
...@@ -419,12 +417,10 @@ see @url{http://www.iversenit.dk/dev/ffmpeg-headers/} ...@@ -419,12 +417,10 @@ see @url{http://www.iversenit.dk/dev/ffmpeg-headers/}
see @url{http://svn.mplayerhq.hu/michael/trunk/docs/} see @url{http://svn.mplayerhq.hu/michael/trunk/docs/}
@section how do I feed H.263-RTP (and likely other RTP bastardizations of codecs) to libavcodec? @section how do I feed H.263-RTP (and other codecs in rtp) to libavcodec?
Remove _ALL_ RTP trash and either feed the fragments through an AVParser and Even if peculiar since it is network oriented, RTP is a container like any
then into the decoder or merge the fragments yourself into proper frames and other. You have to DEMUX RTP before feeding the payload to libavcodec.
feed them into the decoder. Note: The payload of H.263-RTP is not valid In this specific case please look at rfc 4629 to see how it should be done.
H.263 you at least have to merge the first and last bytes discarding RTP trash
from them, possibly more. Also look at rfc 4629.
@bye @bye
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment