from what I know, this is because of socket restrictions. I may be wrong in
how ffmpeg uses them, but generally, the first multicast creates a socket,
declares it as server side on a particular port, and starts listening. the
problem appears when you declare another multicast on the same port, meaning
in will fail when the program behind will declare the second socket as a
server on the same port on the same pc.

the normal solution would be to add in some way the second multicast to the
socket created by the port and select packets based on the IP from which you
received them...

my workaround for a similar application, for now, was to change the incoming
ports of the streams with an outside program, so I could declare the sockets
in the same time, but on different ports.


On Wed, Mar 10, 2010 at 8:01 PM, Ke Yu <[email protected]> wrote:

> Hi All,
>
> I'm trying to open two udp multicast streams simultaneously in one process.
> The first call to av_open_input_file has been working fine. However, the
> second call to av_open_input_file always failed with return value -5 I/O
> error. Is this by design or just a bug? Is there anyway to work around this
> issue?
>
> There's once more piece of information: if I start more than one FFMpeg
> instances on the same machine to open different udp multicast streams, the
> second one failed with IO error.
>
> Thanks!
> _______________________________________________
> libav-user mailing list
> [email protected]
> https://lists.mplayerhq.hu/mailman/listinfo/libav-user
>



-- 
Bogdan COANDA

AIESEC Iasi
AIESEC in Romania

Mobile: +40-724 013 068
E-mail: [email protected]
Website: www.aieseciasi.ro

_____________________________________________________________________________
AIESEC - The international platform for young people to discover and develop
their potential
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user

Reply via email to