> Recently, we have a powerful camera and we would like to put webrtc into that
> camera.
> But, after searching infos from internet, live555 didn’t release webrtc
> officially.
> So, may we have the webrtc source code and put it into our camera?
Our WebRTC implementation is not yet ready to be
Hi Ross,
Recently, we have a powerful camera and we would like to put webrtc into that
camera.
But, after searching infos from internet, live555 didn’t release webrtc
officially.
So, may we have the webrtc source code and put it into our camera?
Thanks a lot.
This electronic mail transmission is
> But why the older version of live555 compiled in VS2010 I mention in original
> mail working without issues on the same environment?
I don’t know; I can’t explain this. That 3-year-old version of the LIVE555
code should have handled RTP/RTCP-over-TCP *worse* - because many bugs in
RTP/RTCP-o
But why the older version of live555 compiled in VS2010 I mention in original
mail working without issues on the same environment?
Unfortunately there are no sources config files left, only binaries. I can't
check these binaries with new VS2013 solution by obvious reasons, but old
VS2010 soluti
The “EAGAIN"s occur when the sending OS's TCP buffer is full - which occurs if
the stream's bitrate exceeds (at least temporarily) the capacity of the TCP
connection. (When this happens, the only solution is to discard outgoing data.
Our code does so by ensuring that if/when data gets discarde
