> I am using genuine proxy server, without modifications yet and still see the
> problem. The error is EAGAIN, and proxy uses nothing more than 2% of CPU and
> little of memory.
> The VERY intereting part is that if i use "openRTSP -v -t -d 60
> rtsp://proxyaddress > /dump.h264 INSIDE camera - i
Hello Ross,
The problem with "why" i have to use proxy - it's because i dont have
source code for original software inside - then i have to "glue"
something else in camera to do the job.
I am using genuine proxy server, without modifications yet and still see
the problem. The error is EAGAIN, a
First, if you have access to the IP camera - and are able to completely control
what runs on it - then why are you using a proxy server at all? Why not modify
the H.264 stream (to add SEI NAL units) as it comes from the camera’s H.264
*encoder*, and just run a single RTSP server (not a proxy se
Hello Ross,
I have an IP Camera that i need to insert SEI messages into datastream.
I used Live555ProxyServer with some modification to do this. But after
that i faced a huge problem.
Camera has already build in RTSP Server so i recompiled to ARM, ran this
inside camera:
localRTSP => liveProxy
> I came across the question on the mailing list "Query Related to GroupSock
> Library",as i am newbie to this live 555 media .In
> "testMPEG2TransportStreamer.cpp" there is support to create in built rtsp
> server, when the proxy server request the "testMPEG2TransportStreamer.cpp"
> with "-t"
Hello Ross
* I came across the question on the mailing list "*Query Related to
GroupSock Library",as i am newbie to this live 555 media .In "testMPEG2Trans
portStreamer.cpp" there is support to create in built rtsp server, when the
proxy server request the "testMPEG2TransportStreamer.cpp" with "-t
