I'm working on an Application using live555 to obtain images from
different cameras using rtsp. I readed about the FPS or bandwith
maximum on the FAQ and I only readed the question about the packet
loss. My problem not is the packet loss, I'm suffering buffering.
When I have a lot of cameras, f
Ross Finlayson writes:
>
> How were you intending to use the "client data" value?
Since my application has a number of concurrent RTSP sessions, I
need to be able to tie responses back to their context. Without
a user data pointer, I can think of two options. The first is to
keep a global map
Hi developers,
I'm working on an Application using live555 to obtain images from different
cameras using rtsp. I readed about the FPS or bandwith maximum on the FAQ
and I only readed the question about the packet loss. My problem not is the
packet loss, I'm suffering buffering. When I have a lot o
It seems that RTSP over HTTP support was broken in the May 29
release. This patch fixes it:
Thanks. For some strange reason, RTSP-over-HTTP worked OK when I
tested it; however, your patch makes the code more consistent with
the previous code, so I'll include it in the next release of the
so
I tried reworking some of my code today to use the new
asynchronous interface, but ran into a couple problems. First, I
do not see a way to set the URL.
The URL is now passed as a parameter to "RTSPClient::createNew()".
This makes more sense than (the previous behavior of) passing it as a
par
