Thanks Ross, I'll take a look into that.
Diego Barboza
2013/10/1 Ross Finlayson
> Hi everyone, I'm doing a research about live streaming the video output
> from a game to a client. By doing so, I need to generate the streaming data
> at runtime instead of reading it from a file (like most LIVE
> I'm developing an application which supports RTP Multicast video streaming.
> The video stream would be H.264 encoded video stream.
> The application should join the appropriate family address of the streamed
> video and behave as a video client.
Because you are transmitting H.264 video via RTP
> I've changed the code to read only one .jpg image and start to stream that
> continuously. But after the stream starts the entire network is brokes until
> I stop the stream.
Of course - because you're streaming data continuously, without any gaps
between the frames!
You commented out the im
Hi,
I'm developing an application which supports RTP Multicast video streaming.
The video stream would be H.264 encoded video stream.
The application should join the appropriate family address of the streamed
video and behave as a video client.
I looked for samples and the closest thing I
Hi all,
I will respond to myself to because i forgot to mention. The camera
produces good and working H264 stream.
Proof: http://www.speed666.info/testok.h264
I can record it via openRTSP command from different host without
problems so it looks like compiler or linux limitation - but where to
Hello,
I wanted to ask You because i have no idea where the problem may sit.
I have compiled openRTSP which i use to dump H264 streams from RTSP
server over localhost
This approach works fine in many IP Cameras that i use for my purpose.
Suddenly i found a device that producest wierd files.
In
Hy!
I founded this example -> http://www.live555.com/Elphel/.
I've changed the code to read only one .jpg image and start to stream that
continuously. But after the stream starts the entire network is brokes until I
stop the stream. I tried to watch the stream with VLC but it not showing the
co
> We think maybe the changes introduced in 2013.09.27 version that close some
> TCP sockets are causing some instabilities.
The (unneeded) sockets that are closed starting in version 2013.09.27 are UDP
sockets, not TCP sockets. I've released a new version (2013.10.02) of the code
now that make
Hello Ross,
We are having critical problems with versions 30.09.2013 and 01.10.2013
over TCP. We use the live555ProxyServer example to connect to a camera
stream using the following command
live555ProxyServer -V -t rtsp://
root:camera86@192.168.0.86/axis-media/media.amp
Once the backend connec
