[Libav-user] [libav-user] demuxing of incoming rtp stream by means of libavformat and custom IO

Dmitry Volyntsev xeioexception at gmail.com
Fri Feb 24 14:02:44 CET 2012

>Or even "dream on" which API calls do you want?
As far as I understood the problem with rtsp/rtp protocol and customIO
because of there more the one endpoint (or entrypoint).
there are al least 3 connection should be established 1 tcp and 2 udp.
It seems, from API user's point of view, problem could be solved be
providing additional custom callback handler (provides user allocated
socket descriptor,for example)

>Then could you expose how your loop looks like?
1) main polling loop monitor all program's async IO descriptors.
2) Set of data processing chains
When data arrives on any of these descriptor the eventloop feeds data to
it's chain input. So for the any data to be processed its descriptor should
be added to EVLoop

I original idea was to feed some raw rtp data to libavformat inside one of
the processing element

On Fri, Feb 24, 2012 at 4:37 PM, Andrey Utkin <
andrey.krieger.utkin at gmail.com> wrote:

> 2012/2/24 Dmitry Volyntsev <xeioexception at gmail.com>:
> > Oh, my fault. I had to mention that I can't use threads and locking
> > mechanisms for efficiency reasons (highloaded application).
> > I need to make rtsp/rtp stream processing with least possible overhead.
> > Event loop is libevent-based.
> > But thanks you, again, for advices!:)
> > I have no questions anymore
> Then could you expose how your loop looks like?
> Or even "dream on" which API calls do you want?
> There's a WIP on non-blocking protocol functions, BTW.
> grep NONBLOCK libavformat/*.h
> --
> Andrey Utkin
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/libav-user

Be happy,
Best regards,
Dmitry Volyntsev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20120224/e125f2a3/attachment.html>

More information about the Libav-user mailing list