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 server) to stream the
modified stream?
If instead you are running - inside your IP camera - “encoder” + “built-in RTSP
server” + “your modified proxy server (which manipulates (presumably with lots
of data copying) the H.264 NAL unit stream)”, then perhaps you are becoming CPU
bound?
> sendRTPorRTCPPacketOverTCP: failed! (errno 11)
What is errno 11 on your system? (Run “man errno”?)
In any case, when streaming-over-TCP fails (as it did for you), it means that
the data rate of the stream exceeds the capacity of your TCP connection. In
this case, that might be because your IP camera’s CPU (and/or memory subsystem)
is becoming overloaded (from all of the extra stuff you’re running on it, with
all of the extra data copying), causing its effective TCP data rate to drop.
In any case, why are you streaming over TCP? If you haven’t already done so,
please read:
http://lists.live555.com/pipermail/live-devel/2018-September/021053.html
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
