Re: [Live-devel] Problem MJEG stream with proxyserver

2014-10-21 Thread Ross Finlayson
Aha! Yes, you found the problem (which was different from what I had originally thought): Your input JPEG/RTP packets were unusually large (1456 bytes, plus IP, UDP headers). Because of the special way that we proxy JPEG/RTP packets, this turned out to be a problem for us. I’ve now installed

Re: [Live-devel] Problem MJEG stream with proxyserver

2014-10-20 Thread 임차섭
Hi. Thank you for reply. I found that fFrameSize is 1444 in PresentationTimeSubsessionNormalizer::afterGettingFrame (ProxyServerMediaSession.cpp). This value occurred fOutBuf->wouldOverflow because fMax of fOutFuf is 1448( rtp header(12) + 1444 > fMax(1448)). So I changed fMax value by ca

Re: [Live-devel] Problem MJEG stream with proxyserver

2014-10-20 Thread Ross Finlayson
> I tested openrtsp, but result is same. Jpg image is broken. Congratulations! You’ve just discovered why MJPEG streaming - especially with very large frames - is a terrible idea. As I note in the FAQ: "You should be aware, though, that JPEG is a very poor codec for video streaming, because (

Re: [Live-devel] Problem MJEG stream with proxyserver

2014-10-20 Thread 임차섭
Hi. I tested openrtsp, but result is same. Jpg image is broken. Image file is created by ‘-m’ option of openrtsp. Thank you. ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

Re: [Live-devel] Problem MJEG stream with proxyserver

2014-10-20 Thread Ross Finlayson
> When I test h.264 via live555ProxyServer, It's works, but MJEG stream is > broken(https://dl.dropboxusercontent.com/u/4188226/mjpeg_broken.png > ). > > RTSP Client is VLC and back-end RTSP Server is IP-Camera. > > I am using last

[Live-devel] Problem MJEG stream with proxyserver

2014-10-20 Thread 임차섭
      ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel