What I think you're complaining about (although I'm not certain, because your
message is not very coherent) is the fact that if you terminate (-C) a
server, and then try to restart it very shortly thereafter, you will sometimes
find that the port number(s) that the server was using are still una
Rather than trying to detect when the RTSP connection closes (which isn't
reliable, and might not happen for a long time after the server disappears), a
better solution is to arrange for a timer to expire if no data arrives within a
certain period of time (e.g., 1 second). This will also detect
Dear All,
Background:
I am using the camera which is a RTSP server which streams the MPEG4 video.
On the other hand I am using linux based small embedded system which is a RTSP
client.
The LIVE555 streaming media libraries are used to write a small application
which can record the camera video
> I am using the LIVE555 livemedia library for my camera recording development.
>
>
> I have a problem.
>
> 1. I started camera recording – recording in progress
> 2. Camera powered off – the RTSP connection got closed. (monitored
> through net stat)
> 3. Program is not c
Dear All,
I am using the LIVE555 livemedia library for my camera recording development.
I have a problem.
1. I started camera recording - recording in progress
2. Camera powered off - the RTSP connection got closed. (monitored
through net stat)
3. Program is not come out t
> I'm tring to use the testH264VideoToTransportStream test application to
> convert **.264 file to **.ts file, and it turns out to have some problems.
> The conversion cannot be completed. For example, I use the given sample
> "tc10.264" and rename it as "in.264" as conversion input, this file i
I'm tring to use the testH264VideoToTransportStream test application to
convert **.264 file to **.ts file, and it turns out to have some problems.
The conversion cannot be completed. For example, I use the given sample
"tc10.264" and rename it as "in.264" as conversion input, this file is
2.6MB; wh
