On 3/3/08, Luca Abeni <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Mahmoud M'HIRI wrote:
> [...]
>
> >>> I have to listen to UDP packets, extract RTP packets, and
> >>> retrieve the payload.
> >> Why do you want to parse RTP packets by yourself if libavformat can
> >> already do it?
> >
> >
> > well, it's not my may to spend my free time but because didn't knew
> about
> > that!
> >
> > I spent the weekend in printing and reading all the code related to
> inputs
> > and networking in ffmpeg (udp.c, rtp.c, rtp.h, avio.c, avio.h,....),
> here
> > what I figured out: ffmpeg implements methods of reading streams from
> file,
> > http, rtp, udp, ...
>
> [...]
>
> From your description, it's still not clear why you do not want to use
> av_open_input_file(), av_read_frame(), and the usual libav* API, anyway...
>
> [...]
>
> > int main ( int argc, char *argv[] )
> > {
> > // Initialization
> > av_register_all();
> >
> > URLContext *h;
> > const char *filename = "udp://0.0.0.0:8060/";
>
>
> This will hardly work. What you probably want is
> "udp://0.0.0.0?localport=8060".
Oh it worked! thanks a lot!! never guessed it was a matter of url's syntax!!
Well, would it would fantastic to deal with my streams using
av_open_input_file() and cie, but when I tested the example of creating
image files from a video with substituting the disk file with
"udp://0.0.0.0?localport=8060" or a sdp file, it didn't worked... that's why
I'm digging deeper..
>
Luca
> _______________________________________________
> libav-user mailing list
> [email protected]
> https://lists.mplayerhq.hu/mailman/listinfo/libav-user
--
Mahmoud M'HIRI
[EMAIL PROTECTED]
Phone: Under request
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
