<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 10pt; font-family: '맑은 고딕';" class=""><span lang="EN-US" class="">I tested openrtsp, but result is same. Jpg image is broken.</span></div></div></div></blockquote><br class=""></div><div>Congratulations! You’ve just discovered why MJPEG streaming - especially with very large frames - is a terrible idea. As I note in the FAQ:</div><div><br class=""></div><div>"You should be aware, though, that JPEG is a very poor codec for video streaming, because
(unlike MPEG, H.264 or H.265 video)
there is no inter-frame compression.
<em class="">Every</em> video frame is a 'key' frame, and is sent in its entirety.
Also, each frame is typically large
(and so takes up many network packets).
If <em class="">any</em> of these network packets gets lost, then the whole frame must be discarded.
JPEG video streaming is strongly discouraged,
and should be considered (if at all) only for high-bitrate local-area networks with very low packet loss.”</div><div><br class=""></div><div>What you’re seeing is packet loss. Because you have doubled the number of network interfaces in your system (in addition to the transmitter’s and the receiver’s interface, you now have the input and output interfaces of the proxy) you have at least doubled the packet loss rate, which *vastly* decreases the likelihood that a complete JPEG frame will be passed end-to-end.</div><div><br class=""></div><div>Your only real solution is to stop trying to stream MJPEG. Instead, transcode to H.264, and stream that.</div><br class=""><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Ross Finlayson<br class="">Live Networks, Inc.<br class=""><a href="http://www.live555.com/" class="">http://www.live555.com/</a></span></span>
</div>
<br class=""></body></html>