> It is ALWAYS immediately follows the error message : > > MultiFramedRTPSource error: Hit limit when reading incoming packet over > TCP. Increase MAX_PACKET_SIZE;
That turned out to be useful information. (It's a pity you didn't mention that before :-) > Could it be that by calling break right after we print that message, that > readSuccess or bPacket has not been updated? No, not quite. However, there *was* a bug in the code that may have caused the problem that you were seeing. I've just installed a new version of the code (2013.04.21) that should fix this. You should also upgrade your *server* (i.e., camera) to use the latest version of the LIVE555 code (if it is using our code, which it likely is). If you do that, this will probably eliminate the "Hit limit when reading incoming packet over TCP" error message that you're seeing in your client. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
