Recently there has been a lot of interest - by several people - in being able
to develop a RTSP server that takes, as input, a UDP Transport Stream (that
arrives via IP multicast, or via unicast). Achraf Gazdar demonstrated how the
LIVE555 libraries can easily be used to do this.
I wasn't orig
Hi Ross
>
> Knowing this is not an issue totally due to live555 , if you could, I
> would like to ask you for some clues or advices about an networking issue
> related with my streaming client application
>
> Using live555, our app; now it can send and receive unicast streams to a
> server , in th
> What is the preferred way of stopping and closing a client after it received
> a stream? Currently, I am calling Shutdown() and it works fine for the first
> time around. When starting another stream after the first one completes, the
> client crashes in the following function:
>
> void Ge
Hi,
What is the preferred way of stopping and closing a client after it
received a stream? Currently, I am calling Shutdown() and it works fine
for the first time around. When starting another stream after the first
one completes, the client crashes in the following function:
void GetSDPDescr
Hi Ross,
Clearly you right, memory is surely allocated, and it will not end with a
segmentation violation.
I will put an exception in valgrind rules, but using unitilalized memory is
probably not a good practice.
In fact what's annoy me is to keep align a valgrind exception (or
